Migrating nRF52840 to nRF52833

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Mon, 31 Jan 2022 11:07:41 GMT

Hi Joel,

Thank you for the update. I'm happy to hear it is working now.

Best regards,

Vidar

RE: Migrating nRF52840 to nRF52833

Joel V — Fri, 28 Jan 2022 19:54:28 GMT

Hi Vidar,

I have managed to resolve the rest of my issues.

First, I had a PIN mapping problem causing my SPI to wait for response.

Second, I took the ESB library from the nRF_15.0.0 and it resolved my communication issue.

I would like to thanks you very much for your help, it is much appreciated !

Best regards,

Joel V.

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Fri, 28 Jan 2022 15:30:40 GMT

Hi,

So you no longer have the problem where the program hangs in the Default_Handler? The nrfx_power_clock.c implementation we had in sdk 15 is removed in more recent SDKs. Now we have the nrfx_power_clock.h header to connect the shared CLOCK_POWER IRQ handler to the handler in nrfx_power.c or nrfx_clock.c: https://github.com/NordicSemiconductor/nrfx/blob/1aa7824f45d46b5f81250801868bef050ba72440/drivers/include/nrfx_power_clock.h#L74

[quote user="Joel V"]goes in an infinite loop in nrfx_spim.c while trying to send or receive data to my antenna, is there something to change in terms of pinout for the antenna in the software ?[/quote]

Could you point me to where it hangs? Also, what is the role of the SPIM in your app? We don't have anything that's controlled through SPI on the 52833 DK.

If possible, maybe you could share your project along with the the files you have modified? I think it would be helpful if I could debug the code here on a DK.

Best regards,

Vidar

RE: Migrating nRF52840 to nRF52833

Joel V — Thu, 27 Jan 2022 19:08:12 GMT

First, I realized that I was using almost exclusively the nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac_min

I tried using nRF5_SDK_16.0.0 instead and it solved some problems (i think), then I had the errors I told you about. Then I found the nrfx_power.c in the 16.0.0 and i didnt have the error anymore, but I cannot find the nrfx_power_clock.c so I commented it and debbugged my nrf52833 and it goes in an infinite loop in nrfx_spim.c while trying to send or receive data to my antenna, is there something to change in terms of pinout for the antenna in the software ?

I think it my solve the problem.

Thanks,

Joel V.

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Thu, 27 Jan 2022 17:58:13 GMT

Hi Joel,

I realize now that there must be more files needing to be patched to get 52833 support in SDK 15.0.0, so it might be easier to just update the entire nrfx directory.

Have you tried to see if your project compiles against the latest nrfx 1.x release? I don't believe there should be any breaking changes as long as you stay on the 1.x branch.

[quote user="Joel V"]NRFX_POWER_CONFIG_DEFAULT_DCDCEN and NRFX_POWER_CONFIG_DEFAULT_DCDCENHV[/quote]

I need to look more into this later. Unlike the 52840, the 52833 does not have a high voltage DCDC regulator, so it kind of makes sense that the last symbol is undefined here.

Best regards,

Vidar

RE: Migrating nRF52840 to nRF52833

Joel V — Thu, 27 Jan 2022 17:34:18 GMT

Hi Vidar,

The nrfx_irqs_nrf52833.h path is included and the following line is written

https://github.com/NordicSemiconductor/nrfx/blob/1aa7824f45d46b5f81250801868bef050ba72440/soc/nrfx_irqs.h#L47

I have tried multiple configurations and there is still those 2 variables that are undefined in my system:

NRFX_POWER_CONFIG_DEFAULT_DCDCEN and NRFX_POWER_CONFIG_DEFAULT_DCDCENHV

Thanks,

Joel V.

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Thu, 27 Jan 2022 16:42:22 GMT

Hi Joel,

Actually, the problem is probably that 'POWER_CLOCK_IRQHandler' is *not* being redefined. Assuming you use the SDK drivers, you need the nrfx_irqs_nrf52833.h (this line) to connect POWER_CLOCK_IRQHandler to the nrfx_power_clock_irq_handler() in nrfx_power_clock.c.

Please make sure the your nrfx_irqs.h file includes the following line: https://github.com/NordicSemiconductor/nrfx/blob/1aa7824f45d46b5f81250801868bef050ba72440/soc/nrfx_irqs.h#L47 and that nrfx_irqs_nrf52833.h is in your include path.

Best regards,

Vidar

RE: Migrating nRF52840 to nRF52833

Joel V — Wed, 26 Jan 2022 17:27:39 GMT

Hi Vidar,

I am not redefining any IRQ handler in my application. Could it be a library I use that have this redefinement ? There is one script I couldn't compile because of an error with nrf_power.h and I decided to let it down because I don't need the usb in my application and the script was about USB. This is the error :

devzone.nordicsemi.com/.../1447.error.txt

Hope it helps,

Joel V.

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Wed, 26 Jan 2022 16:46:24 GMT

Hi Joel,

Do you have a power/clock interrupt handler in your application defined under a different name? I.e. something else than 'POWER_CLOCK_IRQHandler'

In our examples, it is redefined to nrfx_power_clock_irq_handler:

I guess you must have some redefine too that is not included now when you build with -DNRF52833_XXAA.

RE: Migrating nRF52840 to nRF52833

Joel V — Wed, 26 Jan 2022 16:35:17 GMT

Hi Vidar,

I couldn't reply to your last message so I replied here, I read the regs and got this:

Seems like the faulty IRQ is the 0 which is POWER_CLOCK. Any hint on what could cause that ?

Thanks,

Joel V.

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Wed, 26 Jan 2022 16:12:09 GMT

Hi Joel,

No problem!

[quote userid="104385" url="~/f/nordic-q-a/84055/migrating-nrf52840-to-nrf52833/349812#349812"]

I debugged it and it hangs in the gcc_startup_nrf52833.S on line:

.type Default_Handler, %function

[/quote]

This is helpful. It indicates you have an enabled IRQ source without a corresponding IRQ handler. Were you debugging with GDB? In that case, please run "info registers" to get the xPSR register while you are inside the exception handler. You can use "nrfjprog --readregs" for the same if you are not using GDB. The last byte of this register will hold the current ISR number, and that will tell us which one of the IRQs caused the program to enter Default_Handler.

Here is an example where xPSR shows that the program running inside the UARTE0_UART0_IRQHandler:

Note that you have to subtract ISR number by 16 to get the IRQ number as listed in the nrf52833.h header. This is because cortex specific interrupts are starting at -15 instead of 0.

Best regards,

Vidar

RE: Migrating nRF52840 to nRF52833

Joel V — Wed, 26 Jan 2022 15:20:57 GMT

Hi Vidar,

First, thanks for the quick answer !

[quote userid="4240" url="~/f/nordic-q-a/84055/migrating-nrf52840-to-nrf52833/349804#349804"]

The relevant startup files are:

$(SDK_ROOT)/modules/nrfx/mdk/gcc_startup_nrf52833.S

$(SDK_ROOT)/modules/nrfx/mdk/system_nrf52833.c

Also remember to replace the preprocessor flag "NRF52840_XXAA" with NRF52833_XXAA in your makefile.

[/quote]

Those are the exact changes I did, and I changed the board from PCA10059 to PCA100100

[quote userid="4240" url="~/f/nordic-q-a/84055/migrating-nrf52840-to-nrf52833/349804#349804"]Did you update the MDK files in /nRF5_SDK_15.0.0_a53641a/modules/nrfx/mdk/ with files with one of the more recent MDK releases here: https://www.nordicsemi.com/Products/Development-tools/nRF-MDK?[/quote]

I took the MDK in a more recent SDK (17 I think), but now I did the test by using the latest MDK in https://www.nordicsemi.com/Products/Development-tools/nRF-MDK and I still have the same problem.

[quote userid="4240" url="~/f/nordic-q-a/84055/migrating-nrf52840-to-nrf52833/349804#349804"]Are you able to debug the application to see if the program hangs or crashes? [/quote]

I debugged it and it hangs in the gcc_startup_nrf52833.S on line:

.type Default_Handler, %function

in the IRQ handler.

I changed the linker script to have the memory:

MEMORY
{
FLASH (rx) : ORIGIN = 0x00000000, LENGTH = 0x80000
RAM (rwx) : ORIGIN = 0x20000000, LENGTH = 0x20000
}

Thanks,

Joel V.

RE: Migrating nRF52840 to nRF52833

Vidar Berg — Wed, 26 Jan 2022 14:46:01 GMT

Hello,

Are you able to debug the application to see if the program hangs or crashes? It should generally be fairly straight forward port FW from the 52840 to 52833. The most important step is probably to remember to include the correct startup files and update the linker settings to reflect the new memory address ranges.

The relevant startup files are:

$(SDK_ROOT)/modules/nrfx/mdk/gcc_startup_nrf52833.S

$(SDK_ROOT)/modules/nrfx/mdk/system_nrf52833.c

Also remember to replace the preprocessor flag "NRF52840_XXAA" with NRF52833_XXAA in your makefile.

[quote user=""]Now, I have been able to program my DK by adding the dependencies of the nRF52833 in my SDK. [/quote]

Did you update the MDK files in /nRF5_SDK_15.0.0_a53641a/modules/nrfx/mdk/ with files with one of the more recent MDK releases here: https://www.nordicsemi.com/Products/Development-tools/nRF-MDK?

Best regards,

Vidar