Closed plex1 closed 5 years ago
Hi,
I have a pi3 and have to give a try one it :)
Anyway, it look like the PI doesn't handle unaligned memory access properly. so fixing the compilation error could also fix the runtime errors.
Do you feel ready to fix it :D ?
Hi,
Thanks for the reply. Yes changing all the unaligned memory accesses to aligned ones could also solve the runtime issue.
But on the other hand I don't understand why it worked with version a3421baa677c4ac1a1d4c0cb118e7187aeca6537. After disabling the compilation errors (remove -Werror in Makefile) I used that commit a year ago. And programming and debugging of the VexRiscv worked just fine.
Hi,
I think the issue is fixed now in the riscv_spinal branch. the memory missalignement should not be there anymore and the memory issue detected by valgrind are gone too.
Could you give a try ? Let's me know how it go :)
Great. There was one more unaligned memory access which I had to fix. Please check my pull request if it is correct.
Merged, thanks :D
Ok cool. I checked the newest version. And both issues I raised (compile and runtime error) are fixed now. Thanks for your help.
I am trying to run openocd on the Raspberry Pi 3B. Unfortunately I get a compilation error (see below). This problem can be overcome by removing the -Werror flag in the Makefile. Now, compilation and installation is successful. However when running the openocd executable I get a runtine error (see below at the end).
With a previous commit (a3421baa677c4ac1a1d4c0cb118e7187aeca6537) I do have the compilation problem but not the runtime error. So some changes between that commit and the current one (94655121c75ddc846e84fd86c580c324c5f55a22) must break the execution on my target.
Compilation Error:
Runtime Error