Hello,

thanks for giving GDB monitor a try!

it fails to compile (gdb_monitor_interactive)

...

cp: cannot stat `bin/uart_drv': No such file or directory

There exists indeed no UART driver for OMAP4. So the test will not run as is. However, you might opt to use the TCP terminal instead of the UART driver to connect GDB to the debugging target. Both the UART driver and the TCP terminal provide the same "Terminal" interface. So they are interchangeable. You can find the TCP terminal accompanied with a small README file at 'gems/src/server/tcp_terminal'. To integrate it, you will need a "Nic" service, which is provided by the 'usb_drv' on the Pandaboard.

Btw, there is an UART driver for OMAP4 in the works (it is available at the Ksys-labs fork, not yet merged into the mainline tree):

https://github.com/Ksys-labs/genode/commits/pullrequest

and other script(noux_gdb ) it doesn't work on panda board

I have just tried out the run script and cannot reproduce your problem. After starting up, GDB greets me with a prompt at the HDMI screen and accepts commands. Are you using the current master branch of the genodelabs/genode repository?

For reference, I have uploaded an image of my current build here:

https://github.com/downloads/nfeske/genode/noux_gdb_panda.img.gz

Can you give this a try? Just uncompress it (via 'gzip -d') and dump it onto your SD card (via 'dd').

Btw, while playing around with 'run/gdb_noux', I recognized that some stale files in the '<build-dir>/bin' were causing me problems. The run script archives the source code and binary of the debugging target at 'bin/test-gdb_monitor-src' and 'bin/test-gdb_monitor'. Please make sure that your '<build-dir>/bin' directory is free from such artifacts before executing the run script.

Cheers Norman