Freedom Boards and OpenSDA Problem

[tr9]

Recently acquired 3 Freedom boards; FRDM-KE06Z, FRDM-K22F, and FRDM-K64F.

We tried to load Segger's OpenSDA board specific firmwares into each

(available here; www.segger.com/downloads/jlink#JlinkOpenSDABoardSpecificFirmwares )

The K64F worked fine.

The K22F got  bricked, we were able to recover the board by reflashing the K20 debug chip, but cannot load our intended OpenSDA firmware.

The KE06Z does not seem to even accept the OpenSDA firmware we push onto it when in boot mode (appearing as an external drive). The KE06Z remains in boot mode, even after a power-cycle / reset.

This is the first time we have encountered such problems. Other posts have suggested Windows and/or Windows drivers may be a factor.

1. What specific OpenSDA drivers should we be using?

2. Are there specific .srec files we should load into the debug chips of these boards.

3. Something else?

Thanks

[kerryzhou]

Hi tr9,

1. What specific OpenSDA drivers should we be using?

   FRDM-KE06Z, FRDM-K22F, and FRDM-K64F have different opensda version.

  FRDM-KE06 is using the opensda v1.x, this on board K20 can't be mass erased. Then you can't change the on board K20 code.

   FRDM-K22F, and FRDM-K64F is the opensda v2.0/2.1.  These version have problems in win10.

  More details, please check this link:

OpenSDA Serial and Debug Adapter | NXP 

Freedom OpenSDA Firmware Issues Reported on Windows 10 

So, you need to update the K20 code to DAPLink rev0244 OpenSDA v2.2 Bootloader

About the opensda, you need to use DEBUG_OpenSDA_for_MBED_Bootloader_by_Pemicro_v108.bin

2. Are there specific .srec files we should load into the debug chips of these boards.

    FRDM-KE06Z just can change the debugger firmware, can't change the K20 opensda version.

   FRDM-K22F, and FRDM-K64F  can change the K20 code.

   More details and the firmware, go to this link:

OpenSDA Serial and Debug Adapter | NXP 

Wish it helps you!

If you still have question about it, please kindly let me know.
Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[tr9]

All 3 Freedom boards are now loaded with Open SDA firmware from Segger, causing them to function as an equivalent to the Segger J-Link debugger. All are functioning normally. They are being used with a Windows 10 PC running IAR's EWARM tool. This firmware is available from Segger's website.

FRDMK64F - no problem was encountered when loading the Segger Open SDA firmware onto this device. 

FRDMK22F - after following your instructions above we were able to load this board with Segger's Open SDA firmware.

FRDMKE06Z - we used a Windows 7 PC to load Segger's Open SDA firmware. After doing so we had no problems performing development and debug on a Windows 10 PC, running IAR.

Thanks much for the help.

[kerryzhou]

Hi tr9,

   You are welcome.

   It's very good to hear you solved the problem.

   If you have the new question in the future, please create the new question post, we will help you in your new case.

Wish it helps you!

If you still have question about it, please kindly let me know.
Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------