| 01:19.15 | *** join/#openjtag purl (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 01:19.15 | *** topic/#openjtag is this is the place to discuss bootloaders and JTAG |
| 05:58.21 | *** join/#openjtag pleemans (n=toi@212-123-1-140.iFiber.telenet-ops.be) |
| 14:03.42 | *** join/#openjtag prpplague (n=dave@mail.americanmicrosystems.com) |
| 15:14.49 | *** join/#openjtag ali_as_ (n=ali_as@ambix.plus.com) |
| 19:05.10 | *** join/#openjtag ChanServ (ChanServ@services.) |
| 19:05.10 | *** join/#openjtag prpplague (n=dave@mail.americanmicrosystems.com) |
| 19:05.10 | *** join/#openjtag bjdooks (n=ben@trinity.fluff.org) [NETSPLIT VICTIM] |
| 19:05.10 | *** mode/#openjtag [+o ChanServ] by irc.freenode.net |
| 19:14.40 | *** join/#openjtag drath (n=vmaster@p5B07D06B.dip.t-dialin.net) |
| 21:05.25 | bjdooks | has anyone tried an ARM11 recently? I've got a Samsung S3C6410 which seems to be giving an error when validating the jtag chain |
| 21:05.32 | bjdooks | Info: JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: 0x2) |
| 21:05.37 | bjdooks | Info: JTAG device found: 0x07b76f0f (Manufacturer: 0x787, Part: 0x7b76, Version: 0x0) |
| 21:05.39 | bjdooks | Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x0e11 |
| 21:05.42 | bjdooks | Error: Could not validate JTAG chain, continuing anyway... |
| 21:06.02 | bjdooks | iirc, it is an ARM1176 |
| 21:10.55 | bjdooks | posts the question to the list |
| 21:11.04 | *** join/#openjtag ali_as (n=ali_as@ambix.plus.com) |
| 21:20.58 | prpplague | bjdooks: there have been a number of posts recently about improper detection of arm11 chains |
| 21:21.50 | *** join/#openjtag ali_as_ (n=ali_as@ambix.plus.com) |
| 21:32.27 | *** join/#openjtag ali_as (n=ali_as@ambix.plus.com) |
| 21:45.39 | *** join/#openjtag ali_as_ (n=ali_as@ambix.plus.com) |
| 21:55.07 | bjdooks | prpplague: ok, thanks |
| 21:56.57 | prpplague | bjdooks: so far it looks like we are going to bail on samsung for our next gen handhelds and go with an omap |
| 21:57.25 | bjdooks | good luck, the whole omap kernel dev looks a complete mess |
| 21:57.38 | prpplague | bjdooks: indeed, i've been arguing against it |
| 21:57.48 | prpplague | bjdooks: but samsung isn't making it easy |
| 21:59.31 | bjdooks | if you hadn't guessed, we're evalutating s3c6410s |
| 21:59.44 | prpplague | bjdooks: you sure that the 6410 doesn't have a ice debugging device in the chain? |
| 21:59.52 | prpplague | bjdooks: yea |
| 21:59.52 | bjdooks | no idea |
| 22:00.11 | prpplague | bjdooks: the post you did looks as though there is a second device in the chain |
| 22:00.49 | bjdooks | i've solved my problem so far |
| 22:01.15 | prpplague | bjdooks: oh ok, what was it? |
| 22:01.40 | bjdooks | UART's phys-addr not aligned to 1MiB, head code generats L1s only during boot |
| 22:02.09 | bjdooks | when switched to virtual address, the uart's virtual address needed to be shifted up by the offset |
| 22:02.32 | prpplague | bjdooks: uh, are we talking about the problem you posted on the openocd list? |
| 22:02.42 | bjdooks | oh, no, the problem i was trying to debuig |
| 22:09.49 | prpplague | ahh ok |
| 22:10.41 | prpplague | bjdooks: yea, that looks like there is something else in the chain |