Hello Tim, What I do here to implement a NuttX application is to use an Ubuntu Server VM (in my case, VMWare).
In this VM, I map my Jlink (which is a nucleo board with changed firmware). I use Segger tools to load the firmware. To code, I use VSCode in Windows with SSH access to the VM (I set a host-only network). For the toolchain, I use x-pack arm-gcc. The toolchain provided by ubuntu does not provide gdb. You can use the VSCode extension with GDB and JLink to run. Hope it helps. Best regards, Flavio Em ter., 11 de mai. de 2021 às 13:50, Disruptive Solutions <disruptivesolution...@gmail.com> escreveu: > > Tim. Maybe I can try to help you concerning this matter. How can we > connect? Do you have telegram? > > Op di 11 mei 2021 6:42 p.m. schreef Tim <t...@jti.uk.com.invalid>: > > > Pulling my hair out here!! So apologies for the lengthy brain dump and plea > > for help! > > > > > > > > All this starts from the CAN init code crashing (SAMA5D27) when it makes > > any > > call to print debug messages. Printf itself is fine. > > > > > > > > I need to debug it. I will need to get to that point regardless. > > > > > > > > The only way I can actually get Nuttx to build is using WSL - compiles no > > problem at all. I have a MAC - it won't compile without errors and there's > > not enough info (for me) to see what the error is - some complaint about > > ./builtin_list.c > > > > > > > > Mac is the machine I know least. I have no "full" Linux machine. No > > experience of Cygwin and its ilk - just a minefield to me. > > > > > > > > I know Windows best, and have successfully used eclipse under Windows for > > Arm development for many years (sometimes compiling within eclipse, > > sometimes from a command prompt). But although I can download and run code > > via my jlink, eclipse will not correctly index the source code so I cannot > > debug or set breakpoints. > > > > > > > > So I went back to trying to get it to compile under the Mac but no joy so > > not even got as far as seeing if eclipse - or any other debugger- will run > > and do its job. Eclipse is pointing at the source code properly and even if > > I stop the program and manually point the eclipse debugger to the source > > code - where I have inserted a while(1); - it completely refuses to pick up > > the source code. I am suspected a "\" vs "/" issue or something dumb. This > > is true either for a project pointing to a clone in the WSL location or in > > a > > more native windows location > > > > > > > > I have not succeeded in getting Nuttx to build via eclipse (in Windows) > > either - although my "Bare Metal" SAMA5 code compiles just fine with the > > eclipse GNU cross compilers and debugs nicely. > > > > > > > > I thought maybe I could run an X-windows emulator on my Win 10 machine and > > run eclipse on WSL...but it doesn't get very far and just throws errors. > > > > > > > > Thought I'd try Visual GDB - no SAMA5D2 support it seems. Tried to run > > OpenOCD (which purported to be "Windows ready") but it doesn't run. > > > > > > > > Has anyone got NuttX to successfully compile, and allow debug, under either > > MAC or Windows. At all? Ever? > > > > > > > > If someone has any pointers I will be extremely grateful, as this is doing > > my head in. I really don't want to waste yet more days finding a machine to > > build up exclusively for Linux unless I REALLY have to!!! > > > > -- Flavio de Castro Alves Filho flavio.al...@gmail.com Twitter: http://twitter.com/#!/fraviofii LinkedIn profile: www.linkedin.com/in/flaviocastroalves
