Although we will not used full fledged IDE here, the package provides ST-Link GDB Server which will be used for uploading RTEMS binaries to the board memory.
I am really exploring what is different between Arm32 microcontrollers and Arm64. What works on STM32.You seem to want to do things intended for application processors (libgpiod, fltk, u-boot).
gdb is the debugger. Some (many?) developers like to be able to view the running code, set break points, analyze state, registers and so on.For development you need GDB?
community.st.com
MEMORY
{
FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K
DTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128K
RAM_D1 (xrw) : ORIGIN = 0x24000000, LENGTH = 512K
RAM_D2 (xrw) : ORIGIN = 0x30000000, LENGTH = 288K
RAM_D3 (xrw) : ORIGIN = 0x38000000, LENGTH = 64K
ITCMRAM (xrw) : ORIGIN = 0x00000000, LENGTH = 64K
FreeBSD (Unix) is my IDENoob question: is there an IDE for code development on ‘nix platforms.
The best approach is to blend the GUI and the command line, using each where it shines. At least, that's how I'm happy to work.I have zero desire to return to that.
yes, it should follow the rules. Yes, polluting base stuff is bad.Shouldn't the devel/openocd port message have /usr/local/etc/devd as the path for user devd rules? Is that just a nicety?
I thought polluting base stuff bad. In case of upgrades it could be cleaned at that location.
It's the exact tool set I'm using and I'm happy with it.For me, Geany with plugins + make + git + compiler/linker + loader strikes the right balance between "not too old" and "not too modern," while remaining efficient for embedded.
If you add the Code Navigation, GeanyCtags, Git Change Bar, and Project Organizer plugins to Geany, you can navigate the code easily and get a source file tree view; pressing Ctrl-T opens the definition, even if it is in another file that isn't currently open, then you can come back.On Geany, Ctrl-Click only works on open files (Geany doesn't have a project database)
pkg install geany-plugins