Forum : ARM
Post Information | Post |
---|---|
September 20, 2009 - 4:46am
|
Hi all, I'm getting 'Unable to read IdCode' errors when I try and enter debug mode on a LPC2387. It's a new install of Ride/Rkit, everything works great on a STM32F board and I've tried multiple RLINK devices. However, when I go to RLink configuration -> advanced options, I can 'Check connection to target' (it gives IdCode = 0x4F1F0F0F), erase device and (frequently) write target flash. Occasionally trying to write the target flash also gives 'Unable to read IdCode' errors. Trying to enter debug mode always gives debug errors. All I can think is that there is a problem either with the JTAG layout on the 2387 board, or an error in the RLink driver. The 2387 board is a custom design, I can provide schematics if necessary. The JTAG connections are as follows: I've tried with and without the pull up/down resistors mentioned above, and neither configuration helps. Those resistors are chosen based on keil schematics, and looking at what the LPC23XX user manual says about internal JTAG pull up/down resistors. Thanks for your help, |
Also note that while 'Write target FLASH now!' and 'Dump target FLASH to hex file generally appear to complete successfully, the contents of that dump file are always only
:00000001FF
Hi Ben
I have just made a trial again and it is working here.
So lets try to check your board.
You can send to your board schematic.
You can check connectors from here http://raisonance-forum.xsalto.com/viewtopic.php?id=2449
All I see from what you gave is that DBGACK is not connected.
Regards,
Matloub
Hi Matloub,
Correct- I haven't connected DBGRQ or DBGACK pins from the JTAG connector. I couldn't find any pin in the 2387 documentation that seemed appropriate to connect to these. Am I missing something? Should I be doing something with RSTOUT?
I'll send you the schematic- at the moment it's in FreePCB format- is that ok or would gerbers/png images of the copper layers be better?
Thanks,
Ben