On Mon, Oct 06, 2008 at 06:39:24PM -0400, Duane Ellis wrote: > somebody> I'm not convinced that your JTAG chain is configured correctly > somebody> or that your JTAG interface is able to communicate with the > device. > somebody> ARM11 is finicky > > I believe this is exactly the ARM 1176 chip.
Thanks, this is a big help. It seems either the manual or the datasheet is wrong... The setting for what should be the XDBGSEL=1 is giving me the ARM11 instead of the boundary scan... FYI: Info: JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: 0x2) Info: JTAG device found: 0x07b76f0f (Manufacturer: 0x787, Part: 0x7b76, Version: 0x0) Info: found ARM1176 > Here is why. > > > Info: JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: > 0xb900, Version: 0x2) > > Rev: 2 > Mfg: 787 is ARM. > Part: B90 > > I believe is the on-chip ETM module. > > Arm DIA0099C - section 2.2.3 defines bits [27], and [26:24] > > B = 1011 => ARM Embedded Trace buffer(2). > > I do not know what the '90' means. > > > Info: JTAG device found: 0x07b76f0f (Manufacturer: 0x787, Part: 0x7b76, > > Version: 0x0) > > This is clearly the ARM1176. > > See ARM DDI0333G - Section 14.6.2 - page 14-10. > > MFG: 787 - is ARM. > Part: B76 = (B = 11 hex, thus 1176) > It is revision 0. > > This other number is present when the "xdbg" pin is set - placing the > chip in "boundary scan mode" > > > Info: JTAG device found: 0x00eb509d (Manufacturer: 0x04e, Part: > 0x0eb5, Version: 0x0) > > I'll bet - MFG 4e = samsung. > > -Duane. > > > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development -- -- Ben Q: What's a light-year? A: One-third less calories than a regular year. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
