Has anyone encountered a standalone gdb server? That is gdb server that runs on a bare metal.
I've been looking for sources to build one. Doesn't need to be ARM, but that might help.
Maybe someone has come across a document explaining how gdb server really works?
(It might help in reading the 'standard' gdb server code.)
I understand that 'stub' means "gdb server" linked into the executable, but I'd like to have a server with which I could upload programs onto the board for debugging through the network or serial IF.
My main concern is attaching to the program to be debugged, when there is no OS (and no processes).
Stub in boot loader is OK, stub in program to be debugged is not.
About the compatibility: it's the other HW that I'm more concerned, not the core.
RPi 2 B has 4 cores, and that must make some effect on the interrupt controller etc.
Since RPi HW is not "abundantly documented" it'll take some time to figure out stuff.
The good thing about the ARM Connected Community, is that "nothing is final". You can edit everything you've posted earlier - even delete posts.
Try having a look at this excellent post, in particular: "3. How can I change a discussion to a question?".
Since the Raspberry Pi 2 is fairly new, the Linux sources for it might be one of the best sources on how the hardware works.
Reading "driver source code" is unfortunately not the ideal way of finding out how to accomplish a goal, but sometimes it might be the quickest way.
I do not know where to obtain the source, though. Most of the information you need, is related directly to the processors, so if you can get the processor's User's Manual and datasheet, it would probably be all the documentation you'd need.
Unfortunately, not all companies are willing to give the datasheets to developers, some require NDAs, others think that some companies are too small.
I have not tried too but normally it's using U-Boot .
Many Git exists depending on the platform . But we must have a track here
http://www.denx.de/wiki/U-Boot/Custodians
Thanks for the compliment but I had made an omission and that otherwise "excellent" document: the OP can only mark or unmark the discussion as a question within 15 minutes of its creation... However, cause I thought it's what you wanted, I have made the change for you... and I have updated the document!
I wonder why there's a 15 minute limit. It will take most people more than 15 minutes, before someone will notice and suggest a change.
-If you ask me, there should be no limit at all.
-But the document is great nevertheless; packed with information on the topic.
Good find!
As far as I understand, U-Boot allows you to load the program via Ethernet and remote-debug it; but does it need an operating system in order to work, or does it act fully as a bootloader and remote debugger ?
you'll have to load it an image kernel. a small rootfs with some binary but not necessarly the full os.
I don't try it like that, but small kernel image can be found who are using lowest memory.