I think the issue is that you need to halt execution right before all registers
are touched in the handler.
The problem I always found is that at this point it doesn't mean execution
arrived there due to a hardfault
as this is also used for context switches (so placing a breakpoint there is o
;Is there any setup guideline for Nuttx debuggig with VSCode (normal
> > use) and Eclipse (Hard faults)?
> >
> > Best Regards,
> > Marlar
> > ____________________
> > From: Disruptive Solutions
> > Sent: Wednesday, December 9, 2020 6
regs in the eclipse
GUI, and IIRC a ton of typing in VS code or read only. Has that improved?
David
-Original Message-
From: Brennan Ashton [mailto:bash...@brennanashton.com]
Sent: Wednesday, December 09, 2020 5:59 PM
To: dev@nuttx.apache.org
Subject: Re: about IDEs and dev boards
Marlar
gards,
> Marlar
>
> From: Disruptive Solutions
> Sent: Wednesday, December 9, 2020 6:16 PM
> To: dev@nuttx.apache.org
> Subject: Re: about IDEs and dev boards
>
> VSCode (normal use) and Eclipse (Hard faults).
>
> STM32 stack (nucleos
A mixture my c_cpp_properties.json looks like this:
{
"configurations": [
{
"name": "Linux",
"defines": [],
"includePath": ["${workspaceRoot}/**"],
"compilerPath":
"/home/bashton/toolchains/gcc-arm-none-eabi-8-2019-q3-update/bin/arm-none-eabi-gcc",
"compileCommands": "${workspaceRoot}/nuttx/compile
> > From: Disruptive Solutions
> > Sent: Wednesday, December 9, 2020 6:16 PM
> > To: dev@nuttx.apache.org
> > Subject: Re: about IDEs and dev boards
> >
> > VSCode (normal use) and Eclipse (Hard faults).
> >
> >
t;
> Best Regards,
> Marlar
>
> From: Disruptive Solutions
> Sent: Wednesday, December 9, 2020 6:16 PM
> To: dev@nuttx.apache.org
> Subject: Re: about IDEs and dev boards
>
> VSCode (normal use) and Eclipse (Hard faults).
>
> STM32 stack (nucleos, blackboards, etc) an
Dear Ben,
Is there any setup guideline for Nuttx debuggig with VSCode (normal use) and
Eclipse (Hard faults)?
Best Regards,
Marlar
From: Disruptive Solutions
Sent: Wednesday, December 9, 2020 6:16 PM
To: dev@nuttx.apache.org
Subject: Re: about IDEs and dev
VSCode (normal use) and Eclipse (Hard faults).
STM32 stack (nucleos, blackboards, etc) and own reference board(s).
Hardware as extra tools (logic analyzer, scope, seggers, st link, etc)
And just having fun to use NuttX and the results one can achieve. Still
mind blowing!!!
Ben
Op wo 9 dec.
Am 04.12.2020 um 02:54 schrieb Matias N.:
Hi,
I was wondering what IDEs do you use with NuttX and what is your preferred dev
board (can be more than one).
I'm curious since I have used QtCreator for long time now and generally works
well, but it has some quirks.
Jetbrains CLion is the IDE i us
On Thu, Dec 3, 2020 at 5:54 PM Matias N. wrote:
>
> Hi,
> I was wondering what IDEs do you use with NuttX and what is your preferred
> dev board (can be more than one).
> I'm curious since I have used QtCreator for long time now and generally works
> well, but it has some quirks.
These days it
Thanks for the responses.
Any others?
On Fri, Dec 4, 2020, at 08:36, David Sidrane wrote:
> Hi Matais,
>
> I use GNU ARM Eclipse http://gnuarmeclipse.github.io/ but it is now
> https://eclipse-embed-cdt.github.io/
>
> I value it for the Segger debugger integration and SVD support.
>
> I use mak
Hi Matais,
I use GNU ARM Eclipse http://gnuarmeclipse.github.io/ but it is now
https://eclipse-embed-cdt.github.io/
I value it for the Segger debugger integration and SVD support.
I use make file builds imported from git.
I use a lot of the PX4 boards the FMUv2 2.4.6 (Pixhawk2), FMUv4 (Pixracer
> The "mux (almost) any peripheral to any pin" is great (any other chip does
> that?).
The ESP32 does that. Although, for better performance, there is a
selected group of pins for every peripheral.
Regarding the boards, right now I mostly use the ESP WROVER Kit.[1]
This board is populated with
14 matches
Mail list logo
