Kevin > Error: JTAG tap: lpc2478.cpu got: 0x4f1f0f0f (mfg: 0x787, part: 0xf1f0, ver: 0x4)
freddie> put that value (0x4f1f0f0f) in your config file at the top: freddie> set CPUTAPID 0x4f1f0f0f freddie> 0xFFFFFFFF is the default value used to cause the error, so that you can get the right value. Close - the idea here is there should be a "nxp-lpc2478.cfg" file. And - in this case, since we did not know the TAPID of *THAT* specific chip... we use 0xFFFFFFFF to flag the warning, with the hope that the user(victim) will post the details about the chip to the mailing list. It worked exactly as planned :-) Now if somebody can create a 'nxp-lpc2478.cfg' file and post it as a patch - we'll commit it. ==== Some background/history... Some chips have a single tap - ie: arm7tdmi type micro controllers. Others - have multiple taps, in a chain. Others have a "test/configuration" jumper, in one mode, the debug works, in the other "boundary scan work" - example: see the at91rm9200.cfg file. This causes a bit of end-user(victim) confusion. By inserting this "tapid" check - has actually helped quite a bit. It is sort of the "blinky-green-light" *THIS*IS*WRONG*, the "blinky-red-light" *THIS*IS*CORRECT*. In this case, exactly as planned: The blinky-yellow-light: *WARNING*WE*ARE*NOT*SURE*HERE* -Duane _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
