On Mon, May 24, 2021 at 1:04 PM Tim Hardisty
wrote:
> With thanks to Flavio's suggestion (and .json file to point me in the
> right direction) I now have VS Code running under Ubuntu as a full IDE -
> edit/build/debug with Segger jlink all from within VS Code
>
> Had to create custom scripts in t
s not come with GDB. So I use x-pack toolchain to build and debug.
It works well.
Best regards,
Flavio
Em sex., 21 de mai. de 2021 às 13:28, Tim escreveu:
Eventually got a Linux dev environment up and running (first PC purchased
failed after a few hours...grrr...now have an Intel i5 NUC for this
Hello Tim,
I use VSCode with GDB and Segger.
But Ubuntu does not come with GDB. So I use x-pack toolchain to build and debug.
It works well.
Best regards,
Flavio
Em sex., 21 de mai. de 2021 às 13:28, Tim escreveu:
>
> Eventually got a Linux dev environment up and running (fi
Hi Tim,
Great move! Kudos!
I'm also not a GUI guy, I already used the Insight and DDD interfaces with GDB.
You can find other options here:
http://sourceware.org/gdb/wiki/GDB%20Front%20Ends
BR,
Alan
On 5/21/21, Tim wrote:
> Eventually got a Linux dev environment up and running (
Eventually got a Linux dev environment up and running (first PC purchased
failed after a few hours...grrr...now have an Intel i5 NUC for this). Amazed
how darn fast compilation is compared to WSL (even on my 3.3GHz Zeon-based
workstation with the -j6 make option) so that in itself means it was
>On 5/12/21, Tim Hardisty wrote:
>>>From: Alan Carvalho de Assis
>>>
>>>Did you enable CONFIG_DEBUG_CAN_INFO in your menuconfig?
>>>
>>> │ -> Build Setup
>>> │
>>> │ -> Debug Options
>>> │
>>> │ -> Enable Debug Features (DEBUG_FEATURES [=y])
>>>
Hi Tim,
On 5/12/21, Tim Hardisty wrote:
>>From: Alan Carvalho de Assis
>>
>>Did you enable CONFIG_DEBUG_CAN_INFO in your menuconfig?
>>
>> │ -> Build Setup
>> │
>> │ -> Debug Options
>> │
>> │ -> Enable Debug Features (DEBUG_FEATURES [=y])
>>
>From: Alan Carvalho de Assis
>
>Did you enable CONFIG_DEBUG_CAN_INFO in your menuconfig?
>
> │ -> Build Setup
> │
> │ -> Debug Options
> │
> │ -> Enable Debug Features (DEBUG_FEATURES [=y])
> │
> │ -> CAN Debug Features (DE
Did you enable CONFIG_DEBUG_CAN_INFO in your menuconfig?
│ -> Build Setup
│
│ -> Debug Options
│
│ -> Enable Debug Features (DEBUG_FEATURES [=y])
│
│ -> CAN Debug Features (DEBUG_CAN [=y])
BR,
Alan
On 5/12/21, Tim
> Disruptive Solutions Tue, 11 May 2021 09:50:53 -0700 wrote
>Maybe I can try to help you concerning this matter. How can we
>connect? Do you have telegram?
WhatsApp, Signal, email, FB Messenger...but not Telegram :) Email me if you
like and we can go from there - guess you will need to remove t
>Brennan Ashton Tue, 11 May 2021 13:12:50 -0700 wrote
>So back to your root issue, you said you were having issue setting
>breakpoint and getting that to line up with the code, did you enable the
>debug symbols in menu config?
Yes:
- Enable Debug Features checked
- Enable Error Output checked
- E
>From: Gregory Nutt
>Sent: 11 May 2021 18:33
>
>> All this starts from the CAN init code crashing (SAMA5D27) when it
>> makes any call to print debug messages. Printf itself is fine.
>These kinds of crashes are often due to stack overrun. It might be worth
>increasing the stack size of the task t
You can also use Virtualbox. I use this for my NuttX CI/CD. Works nice!
Ben
>
>
I see from https://www.mail-archive.com/dev@nuttx.apache.org/ that others have
replied. These have not got through to me so apologies for not yet taking up
the offers of assistance.
I will try and sort whatever the email issue is and then reply!
For what it's worth, there are a bunch of people here that use macOS
(including our CI testing) and I have used both Cygwin and WSL. So if there
is a problem with any of these it is very important that we work with you
to resolve it rather than drive you to another OS where you may run into
the exa
Hmm...do need Windows for my schematic capture and 3D design applications, but
Mac little used as yet...I'm thinking dual boot Mac/Ubuntu is probably the way
to go!
On 11/05/2021, 20:30, "Alan Carvalho de Assis" wrote:
Also, if you are not dependent on Windows, just install Linux on your
Also, if you are not dependent on Windows, just install Linux on your
computer, it will avoid all those tricks to get the work done ;-)
On 5/11/21, Tim Hardisty wrote:
> Thanks Alan. Compiling is no problem it is debugging that is my issue. I see
> from your process that you copied the elf from t
Hello Tim,
I use ubuntu 20.04 server to save space :-) ... If you use
authorized_keys in ssh ... it is even better.
For me here, the USB in the VM is more stable than in my Windows host
:-\ ... for the J-Link and also for the FTDI to see syslog.
In VS-Code, I use these extensions:
* marus25.cor
I have the board booting from AT91bootstrap and Uboot, from QSPI no problem.
Downloading code using JLink from Windows/eclipse is fine, but the debugging is
broken/mis-configured. I will probably have another go at a Windows-hosted
development environment and have the arm cross compilers install
Thanks Flavio - I hadn't thought about using a VM; that would avoid yet another
lump of PC hardware cluttering up the place if I can't get the WSL or MAC
approach to work.
I am really hating Window at the moment (1 machine can connect to my Mac, the
other can't...many hours wasted NOT fixing it
It seems that it is possible to run JLink from Windows in WSL.
I used J-Link under Windows to bring up the SAMA5Dx. The only tricky
thing was booting from an SD card with U-boot.
All this starts from the CAN init code crashing (SAMA5D27) when it makes any
call to print debug messages. Printf itself is fine.
These kinds of crashes are often due to stack overrun. It might be
worth increasing the stack size of the task that calls CAN init.
Has anyone got NuttX to succes
It seems that it is possible to run JLink from Windows in WSL.
Em ter., 11 de mai. de 2021 às 14:23, Tim Hardisty
escreveu:
>
> Thanks Alan. Compiling is no problem it is debugging that is my issue. I see
> from your process that you copied the elf from the WSL environment to the
> Windows /mnt
Am 11.05.2021 um 18:41 schrieb Tim:
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.
The best way would be a virtual machine using Virtualbox
(https://www.virtualbox.org) (free) or VMWare Player
(https://www.vmware.c
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
Thanks Alan. Compiling is no problem it is debugging that is my issue. I see
from your process that you copied the elf from the WSL environment to the
Windows /mnt/c ...I haven't tried that but I am not sure it will help eclipse
find the source code...unless I also replicate the source tree on t
Hi Tim,
I don't use Windows or MacOS, but some time ago just tested NuttX on
WSL to help other to get started to NuttX on Windows, I documented the
process here:
https://acassis.wordpress.com/2018/01/10/how-to-build-nuttx-on-windows-10/
I hope it helps you!
BR,
Alan
On 5/11/21, Tim wrote:
>
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 :
> 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)
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 on
29 matches
Mail list logo
