Hi All, sorry for the n00b question, but I'm stuck...
My ultimate goal is kernel debugging on a AM3703. I hope to do this via Sourcery's sprite tool chain through a serial line via J-Link ARM Pro to the board. As you may guess, I'm not there yet
I can run JLinkExe (on a linux system) and can reset the board, so I think the serial connection to the board is working. However, when I try to run the sprite executable, I get a J-Link error: Parity error (Data = 0xFFFFFFFF, ReceivedParity = 1). I'm not sure what this is telling me, given that I can connect via the JLinkExe tool itself.
Any suggested probing I can do via jlink tools to find more information? For example, I could write a jlink script to be executed via the default.ini file when invoked via sprite. But what should that script do? What should it look at to find out what's going on?
Thanks,
Steve
My ultimate goal is kernel debugging on a AM3703. I hope to do this via Sourcery's sprite tool chain through a serial line via J-Link ARM Pro to the board. As you may guess, I'm not there yet
I can run JLinkExe (on a linux system) and can reset the board, so I think the serial connection to the board is working. However, when I try to run the sprite executable, I get a J-Link error: Parity error (Data = 0xFFFFFFFF, ReceivedParity = 1). I'm not sure what this is telling me, given that I can connect via the JLinkExe tool itself.
Any suggested probing I can do via jlink tools to find more information? For example, I could write a jlink script to be executed via the default.ini file when invoked via sprite. But what should that script do? What should it look at to find out what's going on?
Thanks,
Steve