On the libm: some time ago I tried to install the RISCV toolchain on Ubuntu with apt and the installed toolchain was built without libm :)
In other words, running compiler + arch flags with "--print-file-name=libm.a" option gave me an empty output (also "find gcc_folder -name libm.a" gave me an empty result). I think the best way is to install GCC from the ARM website and not using OS package manager. For the romfs error, maybe you can try to track romfs generation path and try running it manually from console instead of running it from make. I think it would be easier to narrow down an issue by executing steps manually from the console. Best regards, Petro чт, 9 бер. 2023 р. о 12:01 Simon Filgis <si...@ingenieurbuero-filgis.de> пише: > Hi all, > > thanks for answering. > > I'm still in build-phase. No runtime hard-fault. I'm using my fork on > github https://github.com/SimonFilgis/incubator-nuttx > > Mr. Xiao nailed it. It choose to use the NuttX internal libm for the > moment. > > But still something seems to miss, please have a look at the attached log. > > LD: nuttx >> arm-none-eabi-ld --entry=__start -nostdlib --gc-sections --cref >> -Map=/home/simon/projects/autococo2/temp/autococo2fw/nuttx/nuttx.map -g >> -T/home/simon/projects/autococo2/temp/autococo2fw/nuttx/../autococo2-board/scripts/flash.ld >> -L /home/simon/projects/autococo2/temp/autococo2fw/nuttx/staging -L >> /home/simon/projects/autococo2/temp/autococo2fw/nuttx/arch/arm/src/board \ >> -o /home/simon/projects/autococo2/temp/autococo2fw/nuttx/nuttx \ >> --start-group -lsched -ldrivers -lboards -lc -lmm -larch -lapps >> -lnet -lfs -lbinfmt -lboard >> /usr/lib/gcc/arm-none-eabi/12.2.0/thumb/v7e-m+dp/hard/libgcc.a --end-group >> arm-none-eabi-ld: warning: >> /home/simon/projects/autococo2/temp/autococo2fw/nuttx/nuttx has a LOAD >> segment with RWX permissions >> arm-none-eabi-ld: >> /home/simon/projects/autococo2/temp/autococo2fw/nuttx/staging/libapps.a(nsh_romfsetc.c.home.simon.projects.autococo2.temp.autococo2fw.apps.nshlib.o): >> in function `nsh_romfsetc': >> /home/simon/projects/autococo2/temp/autococo2fw/apps/nshlib/nsh_romfsetc.c:97: >> undefined reference to `romfs_img_len' >> arm-none-eabi-ld: >> /home/simon/projects/autococo2/temp/autococo2fw/apps/nshlib/nsh_romfsetc.c:97: >> undefined reference to `romfs_img' >> make[1]: *** [Makefile:159: nuttx] Error 1 >> make[1]: Leaving directory >> '/home/simon/projects/autococo2/temp/autococo2fw/nuttx/arch/arm/src' >> make: *** [tools/Unix.mk:509: nuttx] Error 2 >> > > Again romfs_img, I had this with the bitbucket pipeline a few days ago, > xxd was missing. I cannot identify root cause with make V=1 (attached). > > Has anybody an idea? > > Simon > > -- > Hard- and Softwaredevelopment Consultant > Ingenieurbüro-Filgis > USt-IdNr.: DE305343278 > > > On Wed, Mar 8, 2023 at 7:43 PM Gregory Nutt <spudan...@gmail.com> wrote: > >> >> > Hi, >> > >> > I think that some key information is missing like what is the NuttX >> version >> > used. Is it mainline or some release or custom. >> > >> > Best regards, >> > Petro >> >> It would be helpful to understand where and why the crash occurs too. >> You can get that information by analyzing the stack. See >> >> https://cwiki.apache.org/confluence/display/NUTTX/Analyzing+Cortex-M+Hardfaults >> for an example. >> >> Without know why the hard fault occurs that is nothing anyone can really >> do or say to be helpful (unless the problem can be replicated). >> >>
