**** BEGIN LOGGING AT Wed Oct 01 02:59:59 2008 Oct 01 21:06:36 has anyone tried an ARM11 recently? I've got a Samsung S3C6410 which seems to be giving an error when validating the jtag chain Oct 01 21:06:45 Info: JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: 0x2) Oct 01 21:06:49 Info: JTAG device found: 0x07b76f0f (Manufacturer: 0x787, Part: 0x7b76, Version: 0x0) Oct 01 21:06:52 Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x0e11 Oct 01 21:06:54 Error: Could not validate JTAG chain, continuing anyway... Oct 01 21:07:14 iirc, it is an ARM1176 Oct 01 21:12:08 * bjdooks posts the question to the list Oct 01 21:22:11 bjdooks: there have been a number of posts recently about improper detection of arm11 chains Oct 01 21:56:20 prpplague: ok, thanks Oct 01 21:58:10 bjdooks: so far it looks like we are going to bail on samsung for our next gen handhelds and go with an omap Oct 01 21:58:38 good luck, the whole omap kernel dev looks a complete mess Oct 01 21:58:51 bjdooks: indeed, i've been arguing against it Oct 01 21:59:00 bjdooks: but samsung isn't making it easy Oct 01 22:00:44 if you hadn't guessed, we're evalutating s3c6410s Oct 01 22:00:57 bjdooks: you sure that the 6410 doesn't have a ice debugging device in the chain? Oct 01 22:01:05 bjdooks: yea Oct 01 22:01:05 no idea Oct 01 22:01:24 bjdooks: the post you did looks as though there is a second device in the chain Oct 01 22:02:02 i've solved my problem so far Oct 01 22:02:28 bjdooks: oh ok, what was it? Oct 01 22:02:53 UART's phys-addr not aligned to 1MiB, head code generats L1s only during boot Oct 01 22:03:22 when switched to virtual address, the uart's virtual address needed to be shifted up by the offset Oct 01 22:03:45 bjdooks: uh, are we talking about the problem you posted on the openocd list? Oct 01 22:03:55 oh, no, the problem i was trying to debuig Oct 01 22:11:02 ahh ok Oct 01 22:11:54 bjdooks: yea, that looks like there is something else in the chain **** ENDING LOGGING AT Thu Oct 02 02:59:57 2008