Hi Øyvind et al - I had a question about the AM3517 work:
http://lists.berlios.de/pipermail/openocd-development/2010-June/015867.html In your early posts you found this ID: 0x0b86802f Info : JTAG tap: am3517.jrc tap/device found: 0x0b86802f (mfg: 0x017, part: 0xb868, ver: 0x0) and eventually you said: > I'll be merging an board config file for Ti AM3517 EVM that > is good enough for alpha testing. But the tcl/board/am3517evm.cfg file I see in git has: set CHIPTYPE "am35x" source [find target/amdm37x.cfg] and: tcl/target/amdm37x.cfg: set _JRC_TAPID "-expected-id 0x0b7ae02f" and I see no reference to your original "0x0b86802f" ID in git. I have a similar board, and the first ID found is 0x0b86802f.... I'm confused, how did you get from finding 0x0b86802f on the jtag chain, to checking in a config file that looks for 0x0b7ae02f? It seems that these are IDs for 2 different flavors of OMAP chips? Looking at u-boot source, +#define HAWKEYE_OMAP34XX 0xb7ae +#define HAWKEYE_AM35XX 0xb868 I'm wondering if you can offer any pointers to get things started.... I'm confused, sorry. :) Thanks, -Eric _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
