Adding BLE kills my console!

RE: Adding BLE kills my console!

Vidar Berg — Mon, 08 Jan 2024 09:00:44 GMT

Hello Doug,

Please verify if the 'uart' group is still present in the generated zephyr.dts file located at build/zephyr/. It should have been removed by the '/delete-node/ uart;' line in your overlay. As you can see from the 7002 DK board file here link, P1.0 and P1.1 should only be assigned to the network core if the 'uart' group has not been deleted.

By the way, since my first reply, we have created a webinar on how to create a custom board in the SDK, see https://www.youtube.com/watch?v=V_dVKgWKILM. This is an alternative to creating board overlays for our 7002 DK.

Best regards,

Vidar

RE: Adding BLE kills my console!

DBT — Fri, 05 Jan 2024 20:10:31 GMT

Vidar,

For option 3 above, what besides "uart" can you use /delete-node/ with?

When I check my MCUSEL bits in the PIN_CNF[n] registers, I notice that P1.0 and P1.1 are also assigned to the NetworkMCU, which isn't what I want either. I want both assigned to the ApplicationMCU

Is there some documentation somewhere that answers this question?

Doug

RE: Adding BLE kills my console!

Vidar Berg — Thu, 20 Jul 2023 12:20:54 GMT

Hello,

The pins defined in the 'gpio_fwd' node (binding) will automatically be assigned to the network core when the network core is enabled by the SoC init code here. But these pins are only used for UART logging from the net core. You can safely remove these pin assignments if you don't need UART logging from the net core.

Ways you can disable the GPIO forwarding

1. Set the 'gpio_fwd' status to "disabled" in your board dts

2. Create a board overlay where you disable the gpio forwarding mechanism:

&gpio_fwd {
    status = "disabled";
};

3. Create a board overlay where you remove the pin assignments for UART but keep the forwarding mechanism enabled (useful if you want to define other pins you want to assign the network core:

&gpio_fwd {
    /delete-node/ uart;
};

Best regards,

Vidar