-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JTAG exploration and OpenOCD support #24
Comments
Hi, By using the correct JTAG pins with nuc910 as target with openocd seem work and correctly reset the CPU :
But i got an error with bootscript.elf :
Do you have an idea what is going wrong ? |
Hey, nice to see that the NUC910 config seems to work!
|
Yes, thanks. That work fine now with monitor.elf. That little bit tricky with openocd. So the only i found is :
I don't known if is link to the fact i use an RPI as JTAG programmer and non welded cables. I don't known, if you can confirm the same behavior on your side ? I cross check JTAG connections that my conclusion :
./gdb.sh output :
UART output :
You can find my config environment on https://github.com/OpeniDrac/wpcm450-openocd |
I'll investigate this when I get around to it (hopefully this weekend, no guarantee though, sorry!). I have a few Dell boards with JTAG headers. |
I've managed to connect to the JTAG port, but I'm still exploring how to do resets with my adapter (Glasgow + OpenOCD) |
I got it to work somewhat well today, but then it stopped working, probably for electrical reasons (I'll re-check my connections when I get around to it). I had to use
I had petty bad performance, it took several seconds for a single step ( |
@StidOfficial unfortunately, I haven't had much success with OpenOCD + GDB either. I get lots of weird errors, UART output doesn't seem to work, etc. |
Ok, for me that work fine but i still need always to restart openocd after halting the CPU. I try to run the latest Linux, but i have some issue with the DTB.
When i launch from u-boot, i got this error :
When i run the kernel
Did you known what i'am doing wrong or this variant is not declared in Linux code ? |
You can't do that, because it's not a DTB:
See for example To build the final bootable image, I use this command: cat arch/arm/boot/zImage arch/arm/boot/dts/nuvoton-wpcm450-supermicro-x9sci-ln4f.dtb > zImage-dtb
The kernel didn't find a DTB, so it requires a machine ID that it recognizes. Machine IDs are the legacy way of telling ARM Linux what kind of board it's running on.
That looks a bit like an ARM instruction that got mistaken for a processor type somehow… Not sure what went wrong here. I've never seen this error (but I've also never tried to load a kernel with openocd). |
Thanks for your quick reply and clear explanation, i try and understand this morning how is work. So i basically do what you told me :
Now i can boot with I don't known why but
You can load the kernel with |
Yes, that's a good start, but what's in
Not sure you need the ATAGS options. I think they should be uncessary if you supply a good devicetree.
I have a few ideas:
|
I get the error
Yes, he use the wrong baudrate. But your supermicro dts use the good baudrate too.
That work too
If you see in output logs, he fail to get the clock, i don't known if that as an impact : EDIT :
|
Ah, you don't seem to have provided any root file system. |
The text was updated successfully, but these errors were encountered: