Hello everyone,
I'm new to embedded systems and would really appreciate any help or suggestions regarding a boot loop issue I'm experiencing with the MCF5253
System Details:
MCF5253
SDRAM : MT48LC4M16A2
FLASH : M25P32
To troubleshoot the boot loop, I purchased a USBDM-JMXX-CF interface to connect to the MCF5253 via BDM. My goal is to identify where the system is stalling during startup.
Tools & Versions:
- USBDM-JMXX-CF(software version 4.12)
- USBDM_4_12_1_340_Win.msi
- CodeWarrior 10.7
BDM connection pins:
-BKPT
-DSCLK
-DSI
-DSO
-RSTIO ->to rst pin of MCF5253
-PST0-4
-GND
-VDD_BDM
When I try to connect with CodeWarrior 10.7, the connection fails with the following error:
: Error launching MCF5253_Console_RAM_USBDM
ColdFire GDI Protocol Adapter : Can't connect. Unknown or not supported device.
I also tested communication using the standalone USBDM application. Here’s the output from a memory dump attempt:
USBDM MEMORY DUMP :
Creating Empty flash image...
Interface options: CFVx, , speed = 250
Using Memory space =
Reading memory-block[0x20000000, 0x20000010, 1]...
Done
I'd appreciate any insights or suggestions, especially on the following points:
1. Has anyone successfully connected to an MCF5253 using a USBDM-JMXX-CF?
2. Is CodeWarrior 10.7 compatible with this setup, or are there known issues?
3. Are there specific configuration steps required to enable BDM communication?
4. Any general advice for debugging boot loops on ColdFire processors?
Thank you in advance for your help and support!
Hello,
Sorry for the later reply.
CodeWarrior for MCUs (Eclipse IDE) supports OSBDM debugger tool.
There are two documents about OSBDM, please refer below links for details:
AN4331: Enabling OSBDM DLLs
You also could find OSBDM basic info from P&E website:
https://www.pemicro.com/osbdm/osbdm_description.cfm
While, P&E has discontinued support for OSBDM.
We recommend to use P&E Multilink debug probes.
Thanks for the attention.
Best regards,
Mike
Thank you so much !
Best regards