Board Fails to Compile Due to sx1276, SPI not connected

[ineskhou]

This was initially observed with the v5d board. When FPrime Zephyr is complied with the board definitions and no LORA radio, on the version v5d, the board no longer boots

This means that

• the serial connection doesnt work on Tabby
• The GDS doesn't run
• none of the hardware, like the LED blinker works

Solution

The solution is to comment out the board definitions of two files.

lora0: sx1276@0 {
		compatible = "semtech,sx1276";
		reg = <0>;
		spi-max-frequency = <125000>;
		dio-gpios =  <&gpio0 13 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>,<&gpio0 12 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>;
		reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
		power-amplifier-output = "pa-boost";
		label = "HOPE_RF";
	};

in

boards/bronco_space/proves_flight_control_board_v5/proves_flight_control_board_v5.dtsi 

[ineskhou]

This could be an SPI issue

zephyrproject-rtos/zephyr#34581
zephyrproject-rtos/zephyr#94282
https://devzone.nordicsemi.com/f/nordic-q-a/74370/unable-to-send-receive-lora-data

If the SPI transaction never completes the SPI driver may get stuck?

It seems under the hood spi_context_wait_for_completion may be the issue? in

https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/spi/spi_context.h#L186

[Mikefly123]

V5d Pinout

[Mikefly123]

V5b Pinout

[Mikefly123]

Radio Pinout | Same For All

[Mikefly123]

After review of the schematics we now believe that the non-boot error was due to a collision between the V5b and V5c/d pinouts. GPIO8 was MISO on b but is PSRAM_CS on c/d. This causes the flash to become confused and cause a crash on boot!

[Mikefly123]

LoRa Radio DIO Mappings