Hello again,
I've got kind of a followup question. I've got some things working (I can hold the board, read and write to memory and resume operations), what's still missing is real debug capability, which most likely comes from me not knowing which file gdb should load. I assumed it would be the image.elf, but that is stripped and therefore seems not to include any debug info.
Another somewhat related question is, if I can make sure that writes via "write<registername>(0x1234)" really happen. If my OCD works, the value doesn't seem to change (or the driver fails before that even gets executed. Is there a way to sensibly use debug-printf like statements (does "Genode::warning()" work inside a device driver?
Thank you and kind regards, Hinnerk
On Wed, May 09, 2018 at 10:32:46PM +0200, Hinnerk van Bruinehsen wrote:
Hello,
I'm writing/porting a bunch of device drivers for an ARM board (am335x based) for Genode/seL4. I have an on chip debugger (flyswatter2) and can halt or resume the board's operation via the OCD (so generally it seems to work). Since you have successfully ported/written drivers for other boards (imx6 for example), I've asked myself if you have some hints, that may help me to get gdbi (ideally with OpenOCD) working. Right now my problem is that I don't know what binary file I should open gdb with, since using the resulting uimage file doesn't work for me.
If someone has some hints for me it would be greatly appreciated!
Have a nice holiday and presumably long weekend!
WKR Hinnerk
Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users