HI,
HI,
Hi Gandy
Okay, so we found something with some further testing on our end. There seems to be a bad register definition in the nrf54l15_application.svd file, so it reads the wrong register when you write out the POWER_CONSTLATSTAT register value.
Reading the memory from the register location in the nRF54L15 datasheet should return the correct value, and constant latency mode should be running correctly. You should be able to see that from the power consumption for example.
For reference, here's a snippet of where the register address is specified in the datasheet (page 98):
Best regards,
Simon
Hi Gandy
Okay, so we found something with some further testing on our end. There seems to be a bad register definition in the nrf54l15_application.svd file, so it reads the wrong register when you write out the POWER_CONSTLATSTAT register value.
Reading the memory from the register location in the nRF54L15 datasheet should return the correct value, and constant latency mode should be running correctly. You should be able to see that from the power consumption for example.
For reference, here's a snippet of where the register address is specified in the datasheet (page 98):
Best regards,
Simon
HI Simon,
Thanks,I had tested it again,
and theCONSTLATSTAT is Right now:
I: Initialization complete
I: Setting up for packet receiption
I: TASKS_CONSTLAT Address=5010e030
I: CONSTLATSTAT Address=5010e520,0 (Low Power)
*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
I: Enhanced ShockBurst prx sample
D: HF clock started
I: Initialization complete
I: Setting up for packet receiption
I: TASKS_CONSTLAT Address=5010e030
I: CONSTLATSTAT Address=5010e520,1 (TASKS_CONSTLAT)