Same HEX, same SoC, different results??

RE: Same HEX, same SoC, different results??

Brian_H — Wed, 07 Feb 2024 23:56:13 GMT

*facepalm*

It's because west build -t menuconfig doesn't modify any files that survive erasing the build directory. So when I did that and rebuilt, it went back to the default of expecting an external oscillator.

Problem solved. Thank you for the tip that got me pointed in the right direction.

RE: Same HEX, same SoC, different results??

Brian_H — Wed, 07 Feb 2024 23:34:37 GMT

The note about the 32kHz crystal rings a faint bell. To be clear, I have had an earlier version of this code running on my project; this is after I made some changes and rebuilt that I can't get it to run.

How would I adjust that clock selection? Is it in a DTB overlay, or a config option?

RE: Same HEX, same SoC, different results??

hmolesworth — Wed, 07 Feb 2024 23:15:24 GMT

As a guide, this kind of issue is typically caused by the difference in hardware, as the development board has a 32.768kHz crystal on the board whereas the module does not unless you added one. Note the uBlox BMD-360 does not have the 32.768kHz crystal internally, it only has the 32MHz crystal.

"3.6 Clocks The BMD-360 requires two clocks, a high frequency clock and a low frequency clock. The high frequency clock is provided on-module by a high-accuracy 32 MHz crystal as required by the nRF52811 for radio operation. The low frequency clock can be provided internally by an RC oscillator or synthesized from the fast clock, or externally by a 32.768 kHz crystal. An external crystal provides the lowest power consumption and greatest accuracy. Using the internal RC oscillator with calibration provides acceptable performance for Bluetooth low energy applications at a reduced cost and slight increase in power consumption"

Should the absent 32.768kHz crystal indeed be the issue, the LF clock in the build must be specified as other than an external crystal otherwise chaos ensues.

Edit: Also the stand-alone module used to be supplied with Rigado/uBlox firmware, boot stuff, which has to be erased; the development board does not.