Stjepan Gotic

> Hi @MainframeReboot please enable Debug Scheduler Info and Debug FileSystem Info, it will report more info showing why it is failing. Look at sched/init/nx_bringup.c line 379, probably it is...

Hi All, Thank you for your replies and the direction, I've definitely learned a lot. I have gone down the road of exporting NuttX, importing it into the `../apps` folder,...

Thanks for your reply @acassis. I can definitely look into a blog post of my findings once I get this to work! I took a look, and I am not...

> > EPC says that the NSH Shell is trying to execute the code at Address 0 and failing? This is very odd. > > Is zero a valid address...

> Hi @MainframeReboot: The RISC-V Exception looks interesting: > > ```yaml > EXCEPTION: Instruction page fault. > MCAUSE: 0x0C > EPC: 0x00 > MTVAL: 0x00 > Segmentation fault in PID...

Thank you all so much for your help. The recent suggestions pointed me down the right path and I can confirm that init now loads:  To get this to...

> > I have seen places where the ctor/dtor code is executed in binfmt > > Constructors and destructors should run in crti and crtN, respectively, for general Unix compatibility....

> > However, that alone did not solve the issue. I had to remove the calls `exec_ctores()` and `atexit(exec_dtors)` from `crt0.c` in order to not crash on ELF load. >...

@patacongo I sat down and RTFM to fully understand the differences between crt0, crt1, crti, crtbegin, crtn and crtend. This has helped me immensely and I have managed to get...

> > I sat down and RTFM to fully understand the differences between crt0, crt1, crti, crtbegin, crtn and crtend > > I recall that crtbegin and crtend come from...