Page 1 of 1

Buildroot settings for remote debug

Posted: 2024-10-27 9:27
by robit
Hi,

Could you please guide me which settings have to be enabled in the .config file of the Buildroot for making the remote debug with gdbserver available?

# BR2_
...

Re: Buildroot settings for remote debug

Posted: 2024-10-28 1:45
by Alenwowo
robit wrote: 2024-10-27 9:27 Hi,

Could you please guide me which settings have to be enabled in the .config file of the Buildroot for making the remote debug with gdbserver available?

# BR2_
...
Hello, we open the gdbserver tool by default (my current SDK version is 1.4), you can use it directly, I tested it without problems.

Re: Buildroot settings for remote debug

Posted: 2024-10-28 19:46
by robit
Thanks for the response.

Where can I download that 1.4 SDK from?
I used the git from https://gitee.com/LuckfoxTECH/luckfox-pico.git, compiled it and burnt the images to a pico miniB.

There is no gdbserver available in this initial system.
I wish to compile the image with my own buildroot menuconfig settings with gdbserver enabled for VSCode IDE
Which BR2_ flags has to be enabled for the gdbserver?

Thanks!

Re: Buildroot settings for remote debug

Posted: 2024-10-29 1:10
by Alenwowo
robit wrote: 2024-10-28 19:46 Thanks for the response.

Where can I download that 1.4 SDK from?
I used the git from https://gitee.com/LuckfoxTECH/luckfox-pico.git, compiled it and burnt the images to a pico miniB.

There is no gdbserver available in this initial system.
I wish to compile the image with my own buildroot menuconfig settings with gdbserver enabled for VSCode IDE
Which BR2_ flags has to be enabled for the gdbserver?

Thanks!
You can download our latest SDK, which opens the gdbserver tool by default, from here: https://github.com/LuckfoxTECH/luckfox-pico

Re: Buildroot settings for remote debug

Posted: 2024-10-29 17:58
by robit
I've got the point now, github instead of gitee.
It works.
Thanks

Re: Buildroot settings for remote debug

Posted: 2024-10-30 1:09
by Alenwowo
robit wrote: 2024-10-29 17:58 I've got the point now, github instead of gitee.
It works.
Thanks
Yes, the first thing we synchronise our updates with is github