On Tue, Aug 24, 2010 at 11:00 PM, David Brownell <davi...@pacbell.net> wrote: > jtag_examine_chain_display() >> 74376: JTAG >> tap: mico_2.cpu tap/device found: 0x01273043 (mfg: 0x021, >> part: >> 0x1273, ver: 0x0) >> Info : 218 293 core.c:949 jtag_examine_chain_display() >> 74032: JTAG >> tap: mico_3.cpu tap/device found: 0x01273043 (mfg: 0x021, >> part: >> 0x1273, ver: 0x0) >> Info : 219 293 core.c:949 jtag_examine_chain_display() >> 74032: JTAG >> tap: mico_4.cpu tap/device found: 0x01273043 (mfg: 0x021, >> part: >> 0x1273, ver: 0x0) >> Info : 220 293 core.c:1072 jtag_examine_chain() 74080: TAP >> pera10_0.cpu does not have IDCODE >> Warn : 221 293 core.c:949 jtag_examine_chain_display() >> 73432: JTAG >> tap: pera10_0.cpu >> UNEXPECTED: 0x00000000 (mfg: 0x000, part: > > > All these zeroes suggest either a TAP which > legitimately has no IDCODE instruction support > (and thus looks like IDCODE == 0) ... > > ... OR else hardware problems somewhere in the > JTAG chain, possibly in some other TAP. >
Hello David, I am not so sure about this. Still smells like reset problem to me. It should be noted that when I let small bootloader execute from the SPI flash and do the reset (and some other config), I can attach with OpenOCD, i.e. chain is well scanned. I was able after attachment to set-up SDRAM and launch eCos application (which would further configure SoC). Now I erased the flash and tried without bootloader. I do not exactly know what bootloader is doing (have not insight in the code yet), but obviously nothing expect reset is needed for a proper chain scanning. It should be also noted that Lauterbach jtag attaches without any problems. I do not think that it does anything special for this step. All what is needed after is few lines of SDRAM set-up and application can be uploaded and run. But that comes after attachment (as for OpenOCD). All this confirms that hardware is working properly. I am almost convinced that bug is either on OpenOCD side (I tried with both ftd libs) or I should configure reset in some special way... Would anybody have some hints after these additional explanations ? Best regards, Drasko _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
