USBDM Software builds

It is suggested to build Linux versions from scratch rather than download the DEB here.
See instructions on this page GitHub

History

USBDM V4_12_1_262 (July 2018)

• Changed how programmer locates RAM region to use
• Fixed startup code in Kinetis firware version so USB interruption recovery is better
• USBDM project stationery (extensive changes)

USBDM V4_12_1_240 (Oct 2018)

• Updated documentation and minor changes
• USBDM project stationery
• Fixes for USBDM libraries

USBDM V4_12_1_230 (June 2018)

• Updated documentation and minor changes
• Updated examples
• Fixed vector table generation for user defined handlers
• USBDM project stationery (a-i)
• Minor corrections
• Refactor for improved visibility
• Added CRC, CMT and EWM

USBDM V4_12_1_220 (June 2018)

• Added S32 family
• Various minor fixes
• Added S32EVM board flash-images
• Updated MCUExpresso installer
• USBDM Eclipse plug-in
• Compiler language standard now passed to C indexer
• Changed default RAM region in project linker file to be largest RAM region
• Set default RAM range to largest added RAM memory region
• Added parameters, improved S32, some peripherals
• Minor changes for consistency
• Added S32K144 and some related improvements
• Added raw binary image files to programmer
• USBDM project stationery
• Fixes for USBDM libraries
• Added synchronization classes and functions
• Work on SVDs — added parameters, improved derivedFrom function
• Added SVDs for S32 family
• Improved SVD for some devices
• Improved SVD processing
• Improved handling of Interrupt entries.
• Added categories for S32 etc.
• Added MKL02-MKL05 stationery (basic)
• Added QUADRATURE mode divider selection
• Fixed missing ‘-‘ for some -ve numbers in write()
• Improved Security descriptions
• Added checks for ISR handler installation
• Updated to be comptible with latest GCC (constexpr changes)

USBDM V4_12_1_210 (November 2017)

• Installer updates
• Added MKW41z
• Fixes for Linux build
• GDB Server
• More control on reset actions, better VLLx reset handling
• Fix for when connecting to secured device
• USBDM project stationery
• Added console write() and writeln()(available for general UART use)
• Snippets updated and other examples added
• Added -Og option to compiler
• Improved C++ example mainline
• Improved speed for SPI driver in USBDM project
• Improved low-power options
• SPI configuration more flexible for shared use
• Added SetIn(), SetOut() and asserts for bit numbers to GPIOxField,
• Added asserts for pin number in SPI
• Added asserts for pin number in TSI

USBDM V4_12_1_200 (July 2017)

• Stationery changes (IRQ handling etc.)

USBDM V4_12_1_190 (July 2017)

• Added MK27, MK28
• Updated Kinetis USBDM firmware
• Added floating-point options for printf() to new project wizard
• Bug Fix in BME operations header file
• Stationery — Added BME operations to GPIO/PCR on MKL devices
• Stationery — Added attribute((always_inline)) to various functions
• Stationery — PCR field names made more consistent
• Stationery — Bug Fix to SPI — startTransaction()
• Stationery — Added eraseAll() to FTFx module
• Stationery — Basic DMA device for some Kinetis MK
• Stationery — Added DMA support to various peripherals
• Stationery — Added DMA examples
• Stationery — Corrected period calculations for PIT, FTM etc (1-off corrections)
• Stationery — Added PDB and ADC support

USBDM V4_12_1_180 (June 2017)

• Added MCUExpresso to installer
• Changed device XML files to use XInclude
• Changed peripheral XML files to use XInclude
• Added MAX30102 examples
• Extended device descriptions (erase methods, programming checksum for LPC devices)
• Updated plugins — Fixes for USBDM launch (MCUExpresso)
• Updated plugins — Added Run/Debug USBDM C++ to project right-click menus and debug/run menus
• Automatically creates launch configurations when missing on launch (see previous)
• Extended erase method and reset method handling (needed for LPC)
• Provided configurable device security settings for projects
• Added some NXP LPC ARM cortex devices:
• Added LPC11U12,LPC11U13,LPC11U14,LPC11U22,LPC11U23,LPC11U24,LPC11U34,LPC11U35,LPC11U36,LPC11U37
• Added LPC1311,LPC1313,LPC1342,LPC1343
• Rebuilt using C++14
• Review of TCL scripts to take advantage of additional features
• Updated I2C examples
• Update LCD examples
• Bug fix — CMSIS build failure on MKL devices (cortex-M0)
• Bug fix — Changed Trim parameters in Launch configurations to string to avoid eclipse parsing errors
• Bug fix — SVD file/device selection fixed for external files
• Bug fix — SVD parsing extended
• Bug fix — Corrected handling of device aliases in GDB server
• Bug Fix — SWD BDM Firmware — Fix for occasional hang in SWD Tx/Rx routines (I hope)
• Bug Fix — Corrected SDIDs for some MKVx devices

USBDM V4_12_1_170 (April 2017)

• Updated FTFL (flash) code stationery
• Improved format of generated Doxygen comments
• Spelling!
• Added mutex lock(), trylock(), unlock()to CMSIS stationery
• Updated Kinetis target flash code, added MKE18M16 family
• Added .abs as valid extension for loading ELF files
• Bug fixes
  • Fix for USB enumeration for non-USBDM devices (JS16_Bootloader and JB16_Bootloader)
  • Fixed MKE02 flash script error (NMI now ignored as expected)
  • Fix for RAM writes for targets without generic Flash program code
  • Changed back to using loading ELF files by Program Headers

USBDM V4_12_1_160 (March 2017)

• Updated GCC to 5.3.0
• Updated wxWidgets to 3.1.1
• GDB programming of secured devices improved
• Restored disabling NMI for MKE device programming
• Added CMSIS CPP wrapper stationery and examples
• Updated various other stationery (CMP, USB)
• Fixed for console for MKE devices
• Minor bug fixes for GDB debug dialogues
• Added MKV4xF16 devices (contribution by LN)

REQUIREMENTS

• BDM firmware must be updated
• Current drivers must be used

See USBDM V4_11_1_70 release for older history

USB Driver Installation

To support the 64-bit version of Windows it has been necessary to update to using libusb1.0 drivers. For consistency this is also done on Linux and the other windows platforms. As part of this process the Vendor-ID/Product-ID (VID/PID) for the hardware (BDM) has been changed. This will allow the co-existence of Freescale’s OSBDM-JM60 hardware while using a new driver for USBDM. Formerly both these BDMs used the same VID/PID and changes to the driver would not be possible without rendering the OSBDM-JM60 inoperable.

Note: On Windows, libusb1.0 is a thin wrapper around the Microsoft winUSB low-level USB drivers. Because of this you may see references to winusb in the following.

Note for upgrading from version 3.x to 4.x USBDM firmware

This change is complicated by the existence of a Bootloader in the BDM firmware. If not replaced this loader will continue to use the original VID/PID. Because of this, it is desirable to completely replace the BDM firmware.

For JS16 based BDMs this is a simple process since the Freescale JS12 Bootloader software may be used to replace all the firmware. See Construction and Installation.

For JMxx based BDMs it is necessary to use a HCS08 programmer to re-program the entire device so that the Bootloader is updated when the rest of firmware is changed. If a programmer is not available then it is still possible to update the BDM firmware using the Bootloader but the Bootloader will remain unchanged. To do this it will be necessary to install the drivers twice — once for the old VID/PID used by the Bootloader and again for the new VID/PID used by the main firmware. Doing so will render any OSBDM drivers inoperable on that USB port.

Installation of USBDM USB drivers for Linux

There isn’t any. The installation script provided will modify the /etc/udev/rules.d file to allow access to the USBDM device. The required driver for USBDM BDM interface (LibusbV1) is included in the standard Linux (at least Ubuntu current version). The CDC (serial port) is a standard device and should also be installed without any extra steps.

If more installation is required on your version you will have to investigate this yourself. I’m not a Linux expert and I don’t have access to other versions for testing. If you find other steps are necessary then please advise and I will try to update the installation accordingly.

Installation of USBDM USB drivers for Windows

This driver allows the USBDM software to communicate with the USBDM cable. You would usually only need to install these driver files once. If you subsequently plug the USBDM cable into another USB port of the same computer the driver will be installed for that port automatically.

The required drivers are copied to the installation location as part of the installation process. The driver folder may be opened from the window’s Start Menu.

Setting up the drivers differs somewhat between the different versions of windows. In versions before Windows 7 you will be automatically prompted to install the drivers using a Found New Hardware Wizard when you first plug in the USBDM. For Windows 7 the installation will quietly fail and it is necessary to manually trigger the wizard.

Prior to Windows 7 the following sequence should occur:

• 1. Plug in the USBDM.
• 2. The Found New Hardware Wizard should appear. Select the Install from a list or a specific location option.
  Select Next to continue.

The above sequence may be necessary a second time if you are installing a USBDM supporting a serial port connection. The serial port appears as a second device.

With Windows 7 the following sequence should occur:

• 1. Plug in the USBDM.
• 2. A small pop-up alert indicates windows is searching for the drivers.

Alternative Driver Installation Method for Windows

Alternatively, zadig may be used to install the libusbV1 drivers for the BDM interface (not the Serial port). http://www.libusb.org/wiki/libwdi/zadig

• Download the current version of the required driver installation program from Windows Backend — libusb or using the direct link (at this time) zadig.exe.
• Plug in the programmed BDM.
• Cancel any dialogues prompting to install the device drivers.
• Under Windows 7 the automatic driver installation will proceed and fail.

This following process will install the correct libusb 1.0 driver.

1. Run the zadig_XXX.exe program.

• 2. Select the BDM from the list of devices. Under Windows Vista and Windows 7 the device description will be USBDM BDM Interface. Under Windows XP it may simply appear as USB Device.
  • Check carefully that the Vendor ID and Product ID are 16D0 and 0567 respectively. There may also be a third number if the USBDM has a serial interface. This should be zero(0) if present.
  • If the description is anonymous click on the Edit Desc. checkbox and change it to something more meaningful.
  • Check that the WinUSB driver is the Target.

    

3. Click the Install Driver button. This will install the driver files. You may see a number of dialogues.

Select Yes to replace any existing driver This may take a while! Note if successful and then Close Select Yes to refresh the list of devices.

4. If you now plug in an updated BDM to another USB port the Found New Hardware wizard should automatically appear. If prompted accept the recommended options to install the driver. Under Windows-7 there may be a prompt to accept an unsigned driver.

5. The Found New Hardware wizard should now complete. Just click Finish to close the dialogue.

Installation of USBDM USB drivers for old VID/PID

This process should only be done if you need to use the USBDM Bootloader to update an old JMxx based BDM when you do not have access to a HCS08 programmer.

• Plug in the old BDM before proceeding.
• Do not move the BDM to another port before updating the firmware as the driver installation will apply only to that port.
• If the BDM has already been updated once, then it may be necessary to use the setboot.exe utility to place the BDM in ICP mode before installing the driver.
1. Run the zadig_XXX.exe program.









Linux Drivers

The shell scripts supplied with the linux version should install the required information for the libusb drivers to work on a linux machine.

You will also need to make sure you have installed some libraries: (Some information posted by joncas on Freescale Forums — thanks)

Читайте также:  Linux создать образ диска img
Оцените статью
Вам также может понравиться

Windows или Linux: Что лучше выбрать?
Есть много причин выбирать между Windows и Linux, но

Файл владелец изменить linux
Команда Chown в Linux Chown Command in Linux (File

Установка шлюза по умолчанию linux
Настройка сети вручную Содержание Краткое описание

Чем разбить диск для linux
ИТ База знаний Курс по Asterisk Полезно — Узнать IP —
• Правообладателям
• Политика конфиденциальности
• Контакты