nuttx

History

cuiziwei 4ec7af779d nuttx/boards:init_array.* needs to be executed in order When I try to set priorities in certain programs, such as init_priority(HIGH_PRIORITY), I've noticed that during linking, there's no guarantee that the programs will be compiled in the sequence I've specified based on priority. This has led to some runtime errors in my program. I realized that in the ld file, when initializing dynamic arrays, there's no assurance of initializing init_array.* before init_array. This has resulted in runtime errors in the program. Consequently, I've rearranged the init_array.* in the ld file of NuttX to be placed before init_array and added a SORT operation to init_array.* to ensure accurate initialization based on priorities during linking.		2023-08-29 22:54:37 +08:00
..
configs/nsh
include
scripts	nuttx/boards:init_array.* needs to be executed in order	2023-08-29 22:54:37 +08:00
src
Kconfig
README-qemu.txt
README.txt

README.txt

1. Download and install toolchain

  $ curl https://static.dev.sifive.com/dev-tools/riscv64-unknown-elf-gcc-8.3.0-2019.08.0-x86_64-linux-ubuntu14.tar.gz

2. Download and install J-Link Software Documentation Pack

  https://www.segger.com/downloads/jlink/

  $ sudo apt install JLink_Linux_V656b_x86_64.deb

3. Configure and build NuttX

  $ mkdir ./nuttx; cd ./nuttx
  $ git clone https://github.com/apache/nuttx.git nuttx
  $ git clone https://github.com/apache/nuttx-apps.git apps
  $ cd nuttx
  $ make distclean
  $ ./tools/configure.sh hifive1-revb:nsh
  $ make V=1

4. Flash the nuttx with J-Link and run

  $ picocom -b 115200 /dev/ttyACM0

  $ /opt/SEGGER/JLink_V656b/JLinkGDBServer -device FE310

  $ riscv64-unknown-elf-gdb ./nuttx
  (gdb) target extended-remote:2331
  (gdb) load nuttx
  (gdb) c

5. TODO

  Support GPIO/SPI/I2C/RTC/WDT/PWM
  Support RISC-V User mode