Skip to content

31 thoughts on “Oh the joys of Open Source.

  1. Matthias Welwarsky

    Oh it works just fine if you debug only Linux. But there are bugs in the TTB handling when TTBCR.N != 0 that make VA/PA translations fail, plus some bogus special cases based on MIDR "partnum" bitfield that I don't understand. I pushed patches into the gerrit, lets see what this resolves to.

  2. Matthias Welwarsky

    Nishanth Menon​ well I actually have access to a trace32, but I can hardly justify buying Cortex M support for my little pet project. Speaking of which, I am now struggling with the IcePick-D on the AM3359, I need to setup the chain so that both the A8 and the M3 are accessible simultaneously. Any help would be greatly appreciated ☺

  3. Matthias Welwarsky

    Nishanth Menon I've looked there. Lots of good information, but surprisingly little questions (let alone answers) about accessing the wakeup-m3 via JTAG. Oh well, maybe I should ask there...

  4. Felipe Balbi

    I don't think icepick docs are publicly available. But yeah, openocd is cool but not a real product; I found out you can't rely on it working. Then again there aren't that many contributors on openocd. And getting anything done for these devices is usually a PITA because the documentation is scattered all over and not all of it is available to the public. A sorry state 🙁

  5. Matthias Welwarsky

    Felipe Balbi There's a public document about ICEPick-C, which is quite detailed. But there seems to be nothing google-able for Icepick-D. The differences seem to be subtly more than just "D supports more TAPs".

  6. Felipe Balbi

    Yeah. There are some other differences just not sure how much I can say :-p it would be great to have that publicly available. In any case, I did a few cleanups on icepick support on openocd. I just never had the time to fiddle with the m3s 🙁

  7. Matthias Welwarsky

    I'm trying to enable both the Cortex-A8 and the Wakeup-M3 taps in the jtag chain so that I can debug both in one session. But while the chain configuration seems to be OK (i.e. no jtag errors reported when scanning), whenever I want to inspect the a8 it fails, while talking to the m3 works fine. So I'm now trying to verify if my assumption about the enabled TAPs and their location is correct.

  8. Felipe Balbi

    Care to send your tcl? If I have some time I'll try here myself. I have some memory of Paul F saying openocd couldn't debug different targets like that, but not 100% my memory's correct

  9. Matthias Welwarsky

    Felipe Balbi​ all set. Turns out the IcePick-D was not the problem, the configuration file just listed the taps in the wrong order. Works if you have only one tap and all others bypassed, but not with 'all in' ☺

  10. Matthias Welwarsky

    Felipe Balbi halt only works if the M3 is not in reset. Apart from that - "targets am335x.m3; halt"

    Also, did you "set DEFAULT_TAPS am335x.dap am335x.m3_dap" ?

  11. Felipe Balbi

    I did use the DEFAULT_TAPS trick, yes. Let me try checking if M3 is in reset or not. I guess targets am335x.m3; run; halt should work ?


Leave a Reply

Your email address will not be published. Required fields are marked *