NRF522832 FreeRTOS can't start.

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Tue, 28 Feb 2023 02:38:24 GMT

OK, thanks I think this problem has been solved.

RE: NRF522832 FreeRTOS can't start.

Edvin — Mon, 27 Feb 2023 11:30:35 GMT

The issue was only the RAM start. Interrupts are forwarded by the MBR, but if you don't set the RAM start address correctly, it will not receive it's interrupts correctly.

BR,
Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Mon, 27 Feb 2023 08:11:13 GMT

Ok, it's worked too, but why?

RE: NRF522832 FreeRTOS can't start.

Edvin — Mon, 27 Feb 2023 08:02:22 GMT

Actually, I spoke to a colleague of mine who wrote the FreeRTOS port for nRF52. Don't comment out the lines from my previous reply. Just change the RAM start.

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Mon, 27 Feb 2023 02:14:39 GMT

it's worked, so the reason is start process interrupted by kernel?

RE: NRF522832 FreeRTOS can't start.

Edvin — Fri, 24 Feb 2023 14:03:39 GMT

EDIT:

DON'T change the port.c file. Only change the RAM start and RAM size:

BR,

Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Fri, 24 Feb 2023 09:31:14 GMT

ok, try this

devzone.nordicsemi.com/.../nRF5_5F00_SDK_5F00_17.1.0.zip

RE: NRF522832 FreeRTOS can't start.

Edvin — Fri, 24 Feb 2023 09:00:51 GMT

Please zip a project that I can unzip that will compile where I can recreate the issue.

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Fri, 24 Feb 2023 07:48:49 GMT

you can see the application in examples/peripheral/blinky_freertos/pca10040/blank/arm5_no_packs.

I removed a lot of things that were not related to UART. So, maybe it looks like a bit of a mess.

devzone.nordicsemi.com/.../1768.nRF5_5F00_SDK_5F00_17.1.0_5F00_ddde560.rar

BR,

Lurn

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Thu, 23 Feb 2023 11:16:20 GMT

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411603"]

Ok, can you please send me a strip down version, or at least an application that replicates the issue that you are seeing? You can use one of the examples in the SDK as a starting point.

[/quote]

Ok, but it might take some time. I can share a part of my code now, but application will take some time.

It looks like a bit of a mess, because I delete some another tasks things.

devzone.nordicsemi.com/.../8823735.sdk_5F00_config.h devzone.nordicsemi.com/.../1321.main.c devzone.nordicsemi.com/.../1212.thread.c devzone.nordicsemi.com/.../1616.uart.c

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411603"]earch your application's sdk_config.h for "LF_SRC". [/quote]

yes, they all set to 1, after set it to 0, threads aren't started too.

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411603"]..RC_CTIV should be set to 16
...RC_TEMP_CTIV should be set to 2
...CLOCK_LF_ACCURACY should be set to 1[/quote]

Sorry, I didn't have the occurrences like you said...

BR,

Lurn

RE: NRF522832 FreeRTOS can't start.

Edvin — Thu, 23 Feb 2023 10:13:05 GMT

[quote user="Lurn_Z"]I can't send you my all application, but I can try to reduce something.[/quote]

Ok, can you please send me a strip down version, or at least an application that replicates the issue that you are seeing? You can use one of the examples in the SDK as a starting point.

Also, search your application's sdk_config.h for "LF_SRC". Are they all set to 1? If so, they should be set to 0. And also, all occurences of:

...RC_CTIV should be set to 16
...RC_TEMP_CTIV should be set to 2
...CLOCK_LF_ACCURACY should be set to 1

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Thu, 23 Feb 2023 07:18:42 GMT

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411365"]It may be a bit too late, but do you really need FreeRTOS? [/quote]

yes, I need FreeRTOS to scheduler my different processes.

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411365"]And you did program the MBR, right?[/quote]

yes, I program the MBR, and the problem arose after that, when I only use FreeRTOS (address start from 0x00), my device looks fine.

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411365"]Can you please send the application?[/quote]

I can't send you my all application, but I can try to reduce something.

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411365"]Oh, did you change your clock configurations in your application to use the internal RC Oscillator instead of the external LFXTAL? Because your custom board didn't have an external LFXTAL, right?[/quote]

before vTaskStartScheduler(); I used this.

{
    nrf_drv_clock_init();
    
    NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
    NRF_CLOCK->TASKS_HFCLKSTART = 1;
    
    while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
}

BR,

Lurn

RE: NRF522832 FreeRTOS can't start.

Edvin — Wed, 22 Feb 2023 13:03:38 GMT

[quote user="Lurn_Z"]can't receive anything, even if I keep sending data.[/quote]

So that is because your threads aren't started, right?

It may be a bit too late, but do you really need FreeRTOS?

I don't know why it doesn't work from your screenshot. Can you please send the application?

And you did program the MBR, right?

Oh, did you change your clock configurations in your application to use the internal RC Oscillator instead of the external LFXTAL? Because your custom board didn't have an external LFXTAL, right?

BR,

Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Wed, 22 Feb 2023 08:57:50 GMT

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411274"]Do any of your tasks actually start?[/quote]

Nope, the tasks not stat, and the vTaskStartScheduler() doesn't return.the debug session is running and not arrived the breakpoint.

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/411274"]What data? How do you send it? UART? BLE? ESB?[/quote]

I use UART to send it, data is like abc...or something, just for test.

RE: NRF522832 FreeRTOS can't start.

Edvin — Wed, 22 Feb 2023 08:45:01 GMT

[quote user="Lurn_Z"]can't receive anything, even if I keep sending data.[/quote]

What data? How do you send it? UART? BLE? ESB?

Does vTaskStartScheduler() return?

Do any of your tasks actually start? Have you tried debugging? Does it hardfault (stop around 0xA60 in the callstack), or does it keep running, just with no log output?

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Wed, 22 Feb 2023 03:14:10 GMT

OK, when I delete this code nrf_drv_clock_lfclk_request(NULL); My device started working normally.

And when set the RX pin pullup, I no longer get gibberish data.

So,I think it works fine weather enable the UART or not.

but when I program MBR and application, the FreeRTOS didn't start scheduler.

1. I only program application (address start 0x00), everthing looks ok, I can receive the data I send and rtt will show logs.

2. I program MBR and application (address start 0x1000), logs looks ok before the code running to vTaskStartScheduler(), and then there was nothing, I can't receive anything, even if I keep sending data.

BR,

Lurn

RE: NRF522832 FreeRTOS can't start.

Edvin — Tue, 21 Feb 2023 12:24:55 GMT

If you have a floating UART RX or CTS pin that is not connected to anything, and especially without pullup, then the application may crash before the log module is initialized. See if it reaches the main-loop in your project. If not, does it stop the same place every time, or does it vary? And if you disable the UART, does it still stop?

BR,
Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Tue, 21 Feb 2023 01:56:01 GMT

yes, I can see it, and the breakpoint can be reached.

Thank you very much.

RE: NRF522832 FreeRTOS can't start.

Edvin — Mon, 20 Feb 2023 14:03:59 GMT

Ok. Were you able to see the RTT log, then? You did in your other ticket, at least. If not, can you please set a breakpoint in main() in main.c and see if this is reached?

BR,

Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Mon, 20 Feb 2023 01:15:09 GMT

yes, it's me

I connect the UART pins, should I set the nrf_gpio_cfg_input(p_config->pselrxd, NRF_GPIO_PIN_NOPULL) to rf_gpio_cfg_input(p_config->pselrxd, NRF_GPIO_PIN_PULLUP) ?

BR,

Lurn

RE: NRF522832 FreeRTOS can't start.

Edvin — Fri, 17 Feb 2023 11:18:28 GMT

I just realized you are the same person that I just answered to in the other ticket 🙂

[quote user=""]I found it can not start, but when I use the RTT to connect my device, It worked[/quote]

Could it be that when you connect the RTT, you also connect the UART pins? A floating UART pin (RX in particular), can cause the application to fail. Looking at the ble_app_uart example for reference, in the uart event handler in main.c, you can see that it has the event APP_UART_COMMUNICATION_ERROR, which will trigger an APP_ERROR_CHECK(err), which will reset the application.

For debugging purposes, see if you have something similar in your application, or try to disable the UART to see if the issue still occurs.

Best regards,

Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Fri, 17 Feb 2023 10:26:41 GMT

Sorry, I also have a 32.768khz clk.

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Fri, 17 Feb 2023 09:38:16 GMT

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/410569"]Is your application (either log or application itself) using UART?[/quote]

yes, I used UART.

[quote userid="26071" url="~/f/nordic-q-a/96752/nrf522832-freertos-can-t-start/410569"]

Can you try it on a DK? Does the same happen there?

Does your custom board have an external LFXTAL?

[/quote]

I only have my custom board with a 32MHz Crystal.

Lurn

RE: NRF522832 FreeRTOS can't start.

Edvin — Fri, 17 Feb 2023 09:35:04 GMT

Is your application (either log or application itself) using UART?

Can you try it on a DK? Does the same happen there?

Does your custom board have an external LFXTAL?

Best regards,

Edvin

RE: NRF522832 FreeRTOS can't start.

Lurn_Z — Fri, 17 Feb 2023 08:54:34 GMT

In my esb program I used this

static void clock_start(void)
{
    NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
    NRF_CLOCK->TASKS_HFCLKSTART = 1;
    while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
}

maybe this is the location of conflict.

But why can I use RTT connect to startup?

Lurn