Hello,
We are having some troubles with the RC32K clock. The problem is that we are not able to make a connection while in sleep mode using RC32K, but it does work with the XTAL32K. We can see using Snippet Tool that the connection dies when it is being established. This is something that we had noticed a while back but since we had read here that changes were to be made to the RC32K code in the next SDK we waited for it to come out.
We now today finally tried the new SDK 3.0.2.0 and unfortunately the reporter_fh project does not appear to work at all for us. The code execution stops at 0x00000EEE shortly after returning from SystemInit() in system_ARMCM0.c, but we can not trace it any further. We have tried this on several different computers on both Keil 4 and Keil 5 and on two different dev-kit's.
So to summarize our questions:
1) How can we get the BLE connection to work while using the RC32K clock in sleep mode?
2) Why is the new SDK 3.0.2.0 not working and how can we get it to work? Does this update require a new daughterboard?
Thanks!
嗨Joacimwe,你能否证实you have 01 Silicon daughterboard ? The SDK 3.0.2 doesn't support 00 Silicon, only 01. If you have a 00 daugtherboard, I can organise a swap-out for you. (01 vs 00 is just ROM update).
Best regards,
JE_Dialog
Hi. How do we easiest check which version (-00 or -01) we have?
Hi Joacimwe, the part marking for all production variants will have a 00 or 01 in the device code on the part marking. Pre-release versions were ES4 (00) or ES5 (01) so it may also be marked ES4 or ES5.I dont have exact part marking to hand, but have requested that (should be in datasheet but someone has forgotten to put that in - will correct that ). I will send you a message so you can pass me your shipping details in private should we need to get you a 01 daughterboard. Best regards JE_Dialog