- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good afternoon,
due to problems with the on board debug probe on the FRDM-K66 board and problems of this board with Segger J-Link Plus, I want to use Segger's Ozone and generate the elf file with MCUXPresso.
After Debug->Start Debug Session -> Download and Reset Program the program should start executing the function main(). The corresponding map file shows that main() starts at 0x428 in the program memory.
extract from frdmk66f_lwip_tcpecho_bm.map
.text.main 0x00000428 0x240 ./source/lwip_tcpecho_bm.o
0x00000428 main
In Ozone at the disassembly window everything looks alright but the code line in the file scope window does not match to the reset conditions. If I understand elf files correctly, the C-code and the corresponding executabble code are linked together. Here, the executable code starts at the right position but is not linked to the corresponding c-code which would be the first non comment or signal declaration line in main().
Thanks in advance for your help
Christof Abt
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all,
I have just found out a working designflow with the FRDM-K66F evaluation board. The on board debugger often dies when the board is connected to a Windows 10 computer. I think it is a problem with the software on the additional microcontroller on the board.
I connected a SEEGER J-link and the connection was established but afterwards the whole system stalled. Yesterday I updated the MCUXpresso IDE to version 24.12.148 and this combination of an external debugger, the FRDM-K66F and the MCUXpresso seems to work.
My problem is solved!
Thanks for your support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I have forgotten to add the screenshot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all,
I have just found out a working designflow with the FRDM-K66F evaluation board. The on board debugger often dies when the board is connected to a Windows 10 computer. I think it is a problem with the software on the additional microcontroller on the board.
I connected a SEEGER J-link and the connection was established but afterwards the whole system stalled. Yesterday I updated the MCUXpresso IDE to version 24.12.148 and this combination of an external debugger, the FRDM-K66F and the MCUXpresso seems to work.
My problem is solved!
Thanks for your support

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am glad to hear that. Any new issues, welcome to create a new post.
BRs,
Celeste

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @ChristofAbt ,
Thanks for your post. We don't have Ozone on our side, so I'm unable to replicate your issue in the exactly same way. I used the on-board debugger to debug the axf file generated by MCUXPresso and didn't encounter any problems.
In the .map file:
.text.main 0x000005fc 0x188 ./source/lwip_tcpecho_bm.o
0x000005fc main
Through the disassembly in the following way.
You can see from the following picture that there is no problem.
You mentioned that your ELF file was generated by MCUXpresso. Could you please tell me how exactly you generated it?
BRs,
Celeste
