Run Command during Pre-Initialization (early chance to disable UART1)

RE: Run Command during Pre-Initialization (early chance to disable UART1)

ovrebekk — Wed, 22 Mar 2023 09:51:21 GMT

Hi Douglas

It is odd that P1.00 wouldn't work, this pin should be available.

Could you try P1.01 as well and see if it's the same issue?

How do you configure and use the pin?

Best regards
Torbjørn

RE: Run Command during Pre-Initialization (early chance to disable UART1)

douglas.malnati — Tue, 21 Mar 2023 14:18:25 GMT

Oh also I have CONFIG_LOG_BACKEND_UART=y and CONFIG_LOG_BACKEND_SWO=n

RE: Run Command during Pre-Initialization (early chance to disable UART1)

douglas.malnati — Tue, 21 Mar 2023 14:17:23 GMT

Ah thanks, I'm looking into that.

Ran into another question while doing so, maybe you can help.

I'm trying to toggle a pin at certain points to know when my code is executing.

Unfortunately, I see no signal, just a constant HIGH logic level, I think QSPI. I'm using the pin that QSPI (P1.00/TRACEDATA0) would be on if in use, but I didn't think it was.

Can you tell me what to look for? I looked and I see CONFIG_NRFX_QSPI defaults to n in my configuration. I tried setting

CONFIG_FLASH_SHELL=n

CONFIG_FLASH=n

But that didn't do it.

Thanks!

RE: Run Command during Pre-Initialization (early chance to disable UART1)

ovrebekk — Tue, 21 Mar 2023 11:17:59 GMT

Hi Douglas

It seems odd that it would take as much as a second for the system to boot, but anyway this should not happen too often in most applications.

In order to run code during the boot sequence you can use the SYS_INIT(..) macro, described here.

With this macro you can define the level at which the function should be run, which determines where in the boot sequence your code gets executed.

If you set the level to PRE_KERNEL_1 it should be called very early in the process.

Best regards
Torbjørn