Hi, I've ported the HelloChirp Firmware to my MCU and I'm experiencing a strange behavour.
The sensor is found, the firmware is uploaded and seems to start correctly but the operating frequency resulting from RTC calibration is totally wrong.
I checked the INT line during RTC calibration and a 100ms impulse is present, as supposed.
Am I missing something?
Any suggestion would be really appreciated.
Hi, let me extend your problem. I got the same issue and lack of information. Driver suppose to customize RTC calibration value as I understand. RTC uses only for Device self-triggered mode. Well, I can't found any information about what RTC value must be except for default 100 ms value. Please give us more information about working modes, timings inside the code and another possible information. This is terrible for porting driver to another MCU without completed datasheet information. First of all, TDK development board firmware has some magic timings and delays and they are floating with expected numeric value in the code, when you try to discover signal from board via oscilloscope.
Hi,
I'm having the same Issue. Did anyone ever figure out how to solve this or what the issue is exactly?
When I'm reading the op_freq value used in the samples_to_mm() calculation, the frequency varies wildly and will never output accurate range readings. Peak in anplitude samples is ok. Strangely the frequency will vary by a few Hz on each reset but will vary wildly (i.e. a few 100kHz) if you power down/up.