The board had an internal "library" to configure pins in an Arduinoeish
fasion. This is no longer used, so can be removed.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
- Specify in DT the pin to enable I2C pull-up connection
- Always build board.c, so that the I2C bus is always pulled-up
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Most sensors are enabled by enabling the VDD_ENV output. Define a
regulator on DT for that and enable the regulators if sensors are
enabled.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
The board has a user LED attached to P1.09. This information was
hardcoded in board C files and enabled by default. This is something
applications need to do if needed (note that an always ON LED can incur
a considerable power consumption).
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
It's not clear why the board configures debug/tracing functionality
using HAL low level code, remove it.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Enabling PWMs without selecting any channel is pointless, so remove
entries from DT. Also remove custom code in sensor_init, PWM API needs
to be used instead.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Drop the BOARD_ARDUINO_NANO_33_BLE_EN_USB_CONSOLE Kconfig option. If
applications need a USB console, they need to adjust `prj.conf` (or
overlays) enabling relevant settings.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
The peripheral is already disabled by default, so the entry was
pointless. Also removed commented code in init_sensors.c related to rtc.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This commit makes the transition from the pinmux driver to the pinctrl
driver. It also modifies UART, SPI and I2C drivers used in FE310-based
boards to use the new pinctrl API.
Signed-off-by: Filip Kokosinski <fkokosinski@antmicro.com>
Fix the BL5340 DVK pin assignment using the nrf5340 DK pin.
Regression from: e4260ac03f.
This also aligns the BL5340 DVK to use the GPIO forward module.
Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
Fix missing include path for TF-M installed headers.
When TF-M was enabled resulted in the following error:
"fatal error: tfm_ioctl_api.h: No such file or directory"
Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
This PR updates the `thingy52_nrf52832` dts to add two additional
aliases for leds 1 & 2.
Why:
In a university course, alot of students use this board with Zephyr
and have wondered why many boards provide dts aliases for
additional leds (ex [1][2]), yet, this only has an alias
for the single led. The PR adds required led
aliases to make working with the leds on this board a
little bit quicker/easier.
Testing:
* `./scripts/twister -p thingy52_nrf52832`
* Hardware verification using the gpio_api to toggle all leds.
Edit: Fixup commit msg line length
[1] boards/arm/particle_boron/dts/mesh_feather.dtsi
[2] boards/arm/arduino_nano_33_ble/arduino_nano_33_ble.dts
Signed-off-by: Wilfred Mallawa <thulith.mallawa@uqconnect.edu.au>
Use the ENTROPY_BT_HCI entropy device on the application core, which has
no access to the hardware RNG peripheral (network core only).
Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
This adds an overlay defining a dummy arduino_header with three pins
required by the adafruit 2.8 TFT display to work on arduino_nano_33_ble.
While the nano form factor doesn't really have a proper Rev3 header, this
allows to connect the display to the nano pins and make the display work.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@huawei.com>
Certain overlays reference I2C and SPI by the semi standardized
arduino_i2c/arduino_spi labels. Add them to the DT for arduino_nano_33_ble
for the I2C and SPI interfaces exposed on the headers.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@huawei.com>
Skeleton board support for the aspeed ast1030 evaluation board from
Aspeed Technology.
Signed-off-by: Dylan Hung <dylan_hung@aspeedtech.com>
Change-Id: I16af50dd63cb355071e32f89264d8aeae47184ac
The LDO line (1V8) used by MAX30101 can be enabled using a regulator
device instead of custom code in the board pinmux.c. The same applies
for the 3V3 line used by multiple sensors.
NOTE: also enabled gpioa, required by LDO_EN. Spotted thanks to
build-time issue (current code did not work...).
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
The battery sensing circuit can be enabled using a regulator device
instead of custom code in the board pinmux.c.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
If such table pointer is present with EFI system table, this will speed
up ACPI initialization later on.
Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Remove pinmux file where possible, and remove all pinmux driver usage
where file cannot be removed. All kinetis boards no longer use pinmux
driver.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Remove pinmux usage for acmp peripheral on kinetis boards, as mcux_acmp
driver supports pinctrl
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
LPSPI peripheral driver supports pinctrl. Move twr_ke18f pinmux to use
pinmux for lpspi, and apply dynamic pinctrl states in order to select
correct chip select pin.
Also add pinmux settings to LPSPI for RT1060, so that LPSPI peripheral
driver will continue to work.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Add dts binding and pinctrl definition for flexio in twr_ke18f. This
allows ke18f pinmux code to apply pinctrl selections for flexio.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
Set CONFIG_PINCTRL=y for all kinetis boards, so they can use the
relevant drivers that enable pinctrl
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
all pinctrl nodes for RT1060 need to be defined, as some drivers used by
kinetis also are used on RT series boards.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
- Move the SX oscillator control pins to a regulator node
- Create a board level compatible for the RF switch
- Use gpio_dt_spec to simplify board pins.c (now rf.c)
- Cleanup include list
For reference:
https://downloads.rakwireless.com/
LoRa/RAK811/Hardware_Specification/RAK811_HF_Schematics.pdf
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
If more information is required on anything, one should look at
documentation, no point to add a specific comment about it.
Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>