USBDM - Version 4.10.4 (RS08/HCS08/HCS12/CFV1/Kinetis BDM)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

USBDM - Version 4.10.4 (RS08/HCS08/HCS12/CFV1/Kinetis BDM)

16,889 Views
pgo
Senior Contributor V

Dear All,

USBDM has been updated to V4.10.4

Please post any queries on this version in a separate thread - I really can't cope with this newfangled setup!

Documentation available at: SourceForge

Applications available at: SourceForge

Source code is available at: GitHub eventually.

bye

Note

  • Please note that these design are different from the Freescale OSBDM-JM60 design which was proceeding independently while I was doing the above designs.


USBDM V4.10

=========================

V4.10.4 (January 2013) -

   - Added support for Codewarrior 10.3 Release (This version does not work with the BETA)

   - Added customisable security options to programmers

   - Improved HCS08/HCS12 programming speeds (15~30%)

   - Added Codesourcery and USBDM API examples to installation

   - Updated/added Codesourcery instructions to help files

   - Numerous bug fixes to GDB Server

   - Improvements to handling secured devices

   - Added Examples to installation

   - Added OpenSDA firmware (This allows use of FRDM-KL25 board as general purpose Kinetis BDM)

  

V4.10.3 (November 2012) -

   - Updated device driver installation (V1.0.1) (removed unnecessary driver).

   - ELF Files now supported for MC56F80xx devices.

   - Changed to shared DLLs build for wxWidgets.

   - Bug fixes:

     - DSC Access to ONCE registers when target running

     - Fixed BDM doing reset when setting target even if already powered.

       This was interfering with doing a 'gentle' connection to a running target.

     - ARM interface now reports access errors on failing memory access rather than following access.

     - Corrected corruption in large reads for ARM GDI Interface.


0 Kudos
46 Replies

267 Views
pgo
Senior Contributor V

Hi Zhilun,

Sorry that's a pretty bad bug in the GUI.  I updated the programmer GUI because of the interaction between the Target and Advanced tabs but missed that problem.  The settings should only be reset on device change but they are happening on all updates and this is done before programming.

I will upload a fix in a couple of days.

I'm sorry for the delay.

bye

Message was edited by: Peter O Donoghue

A fix has been uploaded to sourceforge.

0 Kudos

267 Views
raining
Contributor I

dear peter

   I use the "RS08 Programmer", its trim freqyency to and can not be checked, must be changed to "device selection", or download the error message appears, any suggestions?

   thank you for the quick update.

0 Kudos

267 Views
pgo
Senior Contributor V

Dear Zhilun,

I'm sorry I'm unclear what the problem is that you are describing.

I tested V4.10.4a with a MC9RS08LE4 and it appeared to trim and program correctly.

It is necessary to select the device using 'device selection" and then the trim settings before programming otherwise the trim settings will be reset on device change.  This is intentional as trying to trim with illegal values would be ill advised,

Could you post the error message you are seeing?

bye

0 Kudos

267 Views
raining
Contributor I

dear peter

   when I open the program, the check box is unavailable, see attachment.

Thanks.

0 Kudos

267 Views
pgo
Senior Contributor V

Dear Zhilun,

The reason its isn't enabled is that it is showing the clock module as external so there is no trimming possible.  It should be updated to show the correct clock for the device selected.

It's a bug but it only occurs if the device selected is KA1 when the programmer is closed and then re-opened.  It's because it is the first device in the list.  This is why I hadn't seen it.  I think it was introduced when I fixed the last bug your reported.

I'll have a look at it.

For the moment you will have to select another device and then re-select the KA1 to update the clock information correctly.

Sorry!

bye

0 Kudos