I think the missing piece of information is that the nuttx file contains the debug symbols.
Thanks for your time and help. Regards, Mark _____________________________ Blog: blog.thepcsite.co.uk Twitter: @nevynuk > On 10 Jun 2023, at 22:10, Alan C. Assis <acas...@gmail.com> wrote: > > Hi Mark, > > Could you please try these magical steps: > > $ make distclean > > $ ./tools/configure.sh stm32f777zit6-meadow:nsh > > $ make menuconfig > > Build Setup ---> > Debug Options ---> > [*] Generate Debug Symbols > > $ make -j > > Flash nuttx.bin > > Connect to the board using OpenOCD + STLink-V2: > > $ sudo openocd -f interface/stlink-v2.cfg -f target/stm32f7x.cfg > > In another terminal: > > $ gdb nuttx > (gdb) target remote localhost:3333 > (gdb) monitor reset > (gdb) load nuttx > (gdb) b nx_start > (gdb) c > > BR, > > Alan > > On 6/10/23, Mark Stevens <m...@thepcsite.co.uk> wrote: >> So I’m admitting defeat on this problem and I need some help please. >> >> I’m trying to work out the magic incantations I need to weave to create a >> NuttX ELF file that I can use with GDB. To be clear this is the OS ELF file >> that I can use on the host computer. >> >> I am currently targeting the Pico boards but I have also had this problem >> with the STM32F767 Discovery board as well. I have opened connect to the >> boards in both cases and I am now trying to debug the OS on the board. >> >> Can anyone point me in the right direction - I’m sure it is going to be >> simple, I just need pointing in the right direction. >> >> Thanks in advance, >> Mark >> _____________________________ >> Blog: blog.thepcsite.co.uk >> Twitter: @nevynuk >> >> >> >> >> >>
