8defb843aa
## Summary A lot of linker scripts were listed twice, once for unix, once for windows. This PR cleans up the logic so they're only listed once. ## Impact Any opportunity to use a single source of truth and reduce lines of code is a win! ## Testing CI will test all build |
||
---|---|---|
.. | ||
configs | ||
include | ||
scripts | ||
src | ||
Kconfig | ||
README.txt |
README ====== README for NuttX port to Adafruit NRF52 Feather boards. Contents ======== - Status - Feather nRF52 board - Configurations Status ====== This is the current status of the NRF52 port: - The basic OS test configuration and the basic NSH configurations are present and fully verified. This includes: SYSTICK system time, pin and GPIO configuration, and serial console support. Feather nRF52 board =================== https://www.adafruit.com/product/3406 Console ------- The Feather nRF52 default console is the UART0. The Feather nRF52 have USB serial bridge chip on board and UART0 is connected to micro USB connector through the bridge chip. LEDs ---- The Feather has 2 user-controllable LEDs LED MCU LED1 PIN0-17 LED2 PIN0-19 A high output illuminates the LED. Pushbuttons ----------- The Feather nRF52 does not have user-controllable buttons. The reset button on the board is connected to nRF52832 reset pin directly. Memory Map ========== Block Start Length Name Address --------------------- ---------- ------ FLASH 0x00000000 512K RAM 0x20000000 64K Configurations ============== Each configuration is maintained in a sub-directory and can be selected as follow: tools/configure.sh nrf52-feather:<subdir> Where <subdir> is one of the following: <board>-nsh: ----------- This configuration is the NuttShell (NSH) example at examples/nsh/. NOTES: 1. This configuration uses the mconf-based configuration tool. To change this configurations using that tool, you should: a. Build and install the kconfig-mconf tool. See nuttx/README.txt see additional README.txt files in the NuttX tools repository. b. Execute 'make menuconfig' in nuttx/ in order to start the reconfiguration process. CONFIG_ARCH_LEDS ---------------- If CONFIG_ARCH_LEDS is defined, the LED will be controlled as follows for NuttX debug functionality (where NC means "No Change"). TBD! If CONFIG_ARCH_LEDS is not defined, then the LEDs are completely under control of the application. The following interfaces are then available for application control of the LEDs: uint32_t board_userled_initialize(void); void board_userled(int led, bool ledon); void board_userled_all(uint32_t ledset);