Hi Tim,
You can enable to Stack Monitor to help you.
BR,
Alan
On 1/7/22, Tim wrote:
>>Any thoughts, anyone?
>
> Stack again. Not enough for the main thread. Guess I need to go back to
> school to learn about stacks :(
>
>
>
>Any thoughts, anyone?
Stack again. Not enough for the main thread. Guess I need to go back to school
to learn about stacks :(
Update on my issues.
msconn crashing was, as suggested, inadequate stack size. Default was 768, and
changing to 2048 and it no longer crashes. This was my first experience of
stack issues with NuttX.
I have now merged the 10.2 release and building and running OK.
Msconn now allows my board to
Yes, I now think so. I know I looked at stack settings but (without benefit of
access to my Linux work machine from home) if I recall they are spread around
the place and I suspect - from other advise here - that it is the app stack
size that is inadequate.
Hopefully a break from it all will ma
Could it simply be a stack overflow?
Alan Carvalho de Assis kirjoitti keskiviikko 22. joulukuuta 2021:
> Exactly, something is changing the memory layout and forcing the error
> to happen.
>
> I can try duplicate it later, but I think it could be specific for
> your board configuration. What boar
Hello,
just an idea:
When adding more nested function calls causes a crash, I check stack
overflows.
Sometimes the default stack size specified when defining apps (2048) is
too small, specially you have buffers on this stack, and printf consumes
a lot of stack itself when calling nested for
It is better you create your own blog, some people could like your style to
write the posts!
On Wednesday, December 22, 2021, Tim Hardisty
wrote:
> On 22/12/2021, 20:15, "Alan Carvalho de Assis" wrote:
>
> >On 12/22/21, TimH wrote:
> >> On 22/12/2021 15:55, Alan Carvalho de Assis wrote
On 22/12/2021, 20:15, "Alan Carvalho de Assis" wrote:
>On 12/22/21, TimH wrote:
>> On 22/12/2021 15:55, Alan Carvalho de Assis wrote
>> If I want to share what I'm doing with the details of the project etc,
>> where might you suggest I do this?
>If you want share your progres
On 12/22/21, TimH wrote:
> On 22/12/2021 15:55, Alan Carvalho de Assis wrote
>> This is why I always suggest to people getting started to NuttX to
>> create some blogs post to document their progress and discoveries, it
>> will pave the new to all new users.
>>
> If I want to share what I'm doing
Hi Tim,
Yes, get a solid settings before moving forward is the best approach.
Thank you very much, have a great Xmas and a Happy New Year!
BR,
Alan
On 12/22/21, TimH wrote:
> This is a custom board (SAMA5D27-D5M). I suspect what has happened is
> that multiple "messing around" with configs ha
On 22/12/2021 15:55, Alan Carvalho de Assis wrote
This is why I always suggest to people getting started to NuttX to
create some blogs post to document their progress and discoveries, it
will pave the new to all new users.
If I want to share what I'm doing with the details of the project etc,
w
This is a custom board (SAMA5D27-D5M). I suspect what has happened is
that multiple "messing around" with configs has broken something basic.
To add insult to injury I have messed it all up so badly that the apps
directory won't compile in properly either now.
I will take your advice and retu
Exactly, something is changing the memory layout and forcing the error
to happen.
I can try duplicate it later, but I think it could be specific for
your board configuration. What board/MCU are you using?
BR,
Alan
On 12/22/21, Tim wrote:
> Usb_msc_main.c
>
> If I add a "return OK" as the first
Usb_msc_main.c
If I add a "return OK" as the first line of main, msconn runs and returns.
If I put a printf statement before it, I get a crash.
If I do the same in an example app I've written, it is fine.
If I put a breakpoint at the printf statement and step over it, into there it
gets to "vo
Hi Tim,
On 12/22/21, Tim wrote:
>>Tried running msconn with /dev/ram0 but it still crashes.
>>
>>It *seems* to be printf statements in the msconn system app itself!!??
>>
> Comment all the printf statements out of msconn and it runs...but it now
> crashes during nxtask_exithook().
>
> This SCREAM
>Tried running msconn with /dev/ram0 but it still crashes.
>
>It *seems* to be printf statements in the msconn system app itself!!??
>
Comment all the printf statements out of msconn and it runs...but it now
crashes during nxtask_exithook().
This SCREAMS of a basic nuttx RTOS/THREAD/SOMETHING con
>
>Try to spot the exact place where it is happening, also enabling the DEBUG FS
>could help to spot issues.
Well, here's an odd thing.
I already had FS debug on of course, but not the informational output. Turn
that on, and I can now actually create a FAT volume on /dev/ram0.
Cannot explain t
Hi Tim,
On 12/22/21, Tim wrote:
>>Here the issue is your ramdisk size. You need at least 64 sectors to be
>> able to
>>format as FAT, try it:
>>https://acassis.wordpress.com/2020/08/23/how-to-use-ramdisk-as-filesystem-
>>on-nuttx/
>
> That is the guide I followed Alan:
>
> nsh>mkrd 64
> nsh>ls /d
>Here the issue is your ramdisk size. You need at least 64 sectors to be able to
>format as FAT, try it:
>https://acassis.wordpress.com/2020/08/23/how-to-use-ramdisk-as-filesystem-
>on-nuttx/
That is the guide I followed Alan:
nsh>mkrd 64
nsh>ls /dev
/dev:
console
null
ram0
ttyFC0
ttyFC1
tt
Hi Tim,
On 12/22/21, Tim wrote:
> Hi Alan,
>
> I am - right this minute - using GDB (well...VS Studio Code with Segger
> J-Link) and it falls over during the (second) call to file_dup2 in
> fs_files.c, on its second call (I believe related to usb_scsi_main), but
> not
> got further than that yet.
mental stuff that, to me, just "should work"
quite often doesn't :(
Thanks,
Tim.
>-Original Message-
>From: Alan Carvalho de Assis
>Sent: 22 December 2021 12:22
>To: dev@nuttx.apache.org
>Subject: Re: USB MSD problem
>
>Hi Tim,
>
>I don't
Hi Tim,
I don't know the root cause of the issue you are facing, but it could
be some memory misalignment. Try to use GDB to investigate where the
crash is happening.
Also test using other File Systems, if you use USB MSD with FAT then
your host OS will show the content of the SPI Flash.
BR,
Al
Hi,
Having some grief getting USB MSD device to work, following some notes from
Alan C. Assis from around 5 years ago.
It is an MT25Q 32Mbyte spi nor flash device, registered as /dev/mtdblock0
and also mounted and initialised as an nxfss file system at /mnt/flash. I
can read/write to it from nsh.
23 matches
Mail list logo
