> of
> > the ST-Link. So it appears that the older revision of ST-Link works,
> where
> > as the newer revision does not?
> >
> > On Fri, Dec 6, 2024 at 11:20 AM Russell Burgett <
> rburg...@squarerobots.com
> > >
> > wrote:
> >
> > >
work say 1940 on the BACK of
> the
> > ST-Link, where as the ones I can connect with say IQE 1915 on the FRONT
> of
> > the ST-Link. So it appears that the older revision of ST-Link works,
> where
> > as the newer revision does not?
> >
> > On Fri, Dec
The nuttx example ran with no issues
On Mon, Dec 9, 2024 at 7:26 AM Russell Burgett
wrote:
> thanks Alan,
> I inherited the project from another developer and have been using his
> settings - will start turning things off
> right after I posted I built the Nuttx example for this b
ced you are
> enabling cu terminal, but you have only a UART enabled, so it is using
> /dev/ttyS0 that is also the /dev/console.
>
> I suppose you are not running it yet, but when you run it it could
> interfere in your nsh> in a similar way you described.
>
> BR,
>
>
I am using NuttX on a STM32F446RET.
I have the console enabled (serial) and am able to receive data from my
target, however NSH is not responding to commands sent over serial.
I can execute commands from my nsh_romfsimg.h file, although cd fails with
code 2 and ls fails with the message "out of m
