I'm having difficulty programming this device with a Multilink, and since this is the first time attempting to program this device I'm unsure where the problem lays.
ProgCFZ is able to detect the device as generic "Generic 52xx", but is unable to communicate. The board combines all PST lines into a single connection, which I have connected to all four PST pins in the adapter cable (this board does not utilize the default connector).
I am able to program another ColdFire V2 device, MCF5282, with a Multilink Universal via ProgCFZ and the older ColdFire software.
I think the adapter cable was made correctly, but I'd also appreciate a sanity check on whether this setup should be working in the first place, and to know if there are certain requirements I may not be meeting.
Ian A,
JTAG_EN has to be low (=0) to enable Background debug mode. Our tools do not support JTAG mode.
Can you uncheck the box "Use PST signals to determine device state" in the connection manager/assistant screen of PROGCFZ? Then it should not matter how your PST lines are connected.
Please try a reset delay of 300 ms or higher.
Do you have any external watchdogs that need to be turned off?
Please refer to the recommended ColdFire BDM pinout in the technical summary of the Multilink Universal.
https://www.pemicro.com/downloads/download_file.cfm?download_id=376
What other differences do you have from our pinout?
If you open a support ticket and show us a schematic of your board, that might be useful in tracking down the issue.
Regards,
Johnny
PEmicro
Hi Johnny,
I confirmed that JTAG_EN is set low, that the reset line is only being controlled by the programmer, and tried the PST and delay settings you suggested, all to no avail. I would like to create a ticket and send you the schematic, but I need to have PE sign an NDA before doing so. Can you provide an email for our team to contact for this process?
Thank you.
Hi Ian,
Are you allowed to send us just the small portion of the clock and debug circuitry without needing an NDA (which will take time to go through the process)?
Regards,
Unfortunately, I cannot. This is customer IP so we must be strict with its handling.
You can create a support ticket through Support -> Submit a Support ticket to attach the NDA docs.
While we wait for that process, you should analyze the debug signals on an oscilloscope.
Port D – Coldfire V2/V3/V4
a. BKPT (Pin-2), DSI (Pin-8), and DSCLK (Pin-4) signals are driven low.
b. RESET (Pin-7) is driven low for 20+ milliseconds and released.
c. After RESET is released and if the processor has correctly entered background mode, the PST0 (Pin-15), PST1 (Pin14), PST2 (Pin-13) and PST3 (Pin-12) lines should all be driven high by the processor.
d. Activity (changing signals) is seen on the DSI, DSO, and DSCLK signals. The activity on the DSCLK and DSI lines is generated by the PC and the activity on the DSO line is generated by the processor.
How are your XTAL, EXTAL, and BOOTMOD[1:0] signals connected?
a. BKPT (Pin-2), DSI (Pin-8), and DSCLK (Pin-4) signals are driven low.
BKPT starts at 3.3V then starts oscillating
DSI starts at 3.3V then starts oscillating
DSCLK starts at 0V then starts oscillating
b. RESET (Pin-7) is driven low for 20+ milliseconds and released.
RESET starts at 3.3V then goes low for 20 milliseconds
c. After RESET is released and if the processor has correctly entered background mode, the PST0 (Pin-15), PST1 (Pin14), PST2 (Pin-13) and PST3 (Pin-12) lines should all be driven high by the processor.
PST0-3 are combined into one signal, ALLPST. With COLDFIRE interface disconnected, ALLPST remains low. When the COLDFIRE interface is connected, ALLPST is high and remains high.
d. Activity (changing signals) is seen on the DSI, DSO, and DSCLK signals. The activity on the DSCLK and DSI lines is generated by the PC and the activity on the DSO line is generated by the processor.
Activity is seen on the DSCLK and DSI lines, no activity seen on the DSO line.
I have a couple snippets from the schematic showing the XTAL, EXTAL, and BOOTMOD[1:0] connections. How would I be able to send them?
Rob,
You can send them to technical-info@pemicro.com. Reference this forum post in the email message.
Regards,
Johnny