-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Description
Following introduction of "default board configuration guidelines" (#6858), one part of the work is to move boards already ported to zephyr to conform with guidelines available here:
http://docs.zephyrproject.org/porting/board_porting.html#default-board-configuration
In order to migrate all boards to the new standards, work is split into several tickets. See below.
As part of the work to do on each board:
- pins should be configured to fit valuable HW components available on board
- pins should be configured to fit connector if featured on the board (dts file should provide connector configuration and board should select matching connector flags, cf Enable use of shields #6837)
- propose a default network interface (when possible)
- If ever a pin conflict prevents configuration of one of the components, board documentation should be updated with conflict and arbitration.
- update board metadata yaml file vs new board configuration (cf documentation)
Work is split into following issues:
- Get 96Boards boards (4) compliant with default configuration guidelines (Get 96Boards boards compliant with default configuration guidelines #9233)
- Get ARC boards (4) compliant with default configuration guidelines (Get ARC boards compliant with default configuration guidelines #9234)
- Get XTENSA boards (2) compliant with default configuration guidelines (Get XTENSA boards compliant with default configuration guidelines #9235)
- Get X86 boards (8) compliant with default configuration guidelines (Get X86 boards compliant with default configuration guidelines #9236)
- Get RISCV boards (5) compliant with default configuration guidelines (Get RISCV boards compliant with default configuration guidelines #9237)
- Get POSIX board compliant with default configuration guidelines (Get POSIX board compliant with default configuration guidelines #9238)
- Get NIOS boards (2) compliant with default configuration guidelines (Get NIOS boards compliant with default configuration guidelines #9239)
- Get ARM boards (2) compliant with default configuration guidelines (Get ARM boards compliant with default configuration guidelines #9240)
- Get ATMEL SoC based boards (6) compliant with default configuration guidelines (Get ATMEL SoC based boards compliant with default configuration guidelines #9241)
- Get NORDIC SoC based boards (15) compliant with default configuration guidelines (Get NORDIC SoC based boards compliant with default configuration guidelines #9242)
- Get NXP SoC based boards (8) compliant with default configuration guidelines (Get NXP SoC based boards compliant with default configuration guidelines #9243)
- Get SILABS board compliant with default configuration guidelines (Get SILABS board compliant with default configuration guidelines #9244)
- Get TI SoC based boards (4) compliant with default configuration guidelines (Get TI SoC based boards compliant with default configuration guidelines #9245)
- Get ST Nucleo boards (14) compliant with default configuration guidelines (Get ST Nucleo boards compliant with default configuration guidelines #9246)
- Get ST Disco and Eval boards (14) compliant with default configuration guidelines (Get ST Disco and Eval boards compliant with default configuration guidelines #9247)
- Get Olimex boards (4) compliant with default configuration guidelines (Get Olimex boards compliant with default configuration guidelines #9248)
- Get ST Based boards (3) compliant with default configuration guidelines (Get non ST, STM32 Based boards compliant with default configuration guidelines #9249)
In order to allow provision of dts connector aliases, dtc > v1.4.1 should be used. Hence all these tickets (at least when a connector is available on board) have a dependency on zephyr SDK v0.9.3:
https://github.com/zephyrproject-rtos/meta-zephyr-sdk/releases/tag/0.9.3-rc2
PR #7176 could be used as reference for this update.
EDIT: Following creation of #19116 that aims at instantiating a systematic test to check compliance, I'm closing the above issues.