Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I have recently been debugging some hardware for a BCM20732S in which the App is the simple hello_sensor App. The 20732S board has P0 connected to a PB just as the TAG2 board has. The app runs fine on the TAG2 board and P0 updates/increments Hello x indication/notification.
On the BCM20732S the device connects/pairs fine and I can 'Write' to the HANDLE_HELLO_SENSOR_CONFIGURATION to blink the LED different amounts but as soon as I allow indications/notifications and Press P0 it updates Hello 0 to Hello 1 but then the device stops responding completely. I notice a difference in the Debug Output in that the module prints out "Stop Powersave!!!" that prints out when I use the BCM20732S but does not get printed out with the TAG2 board/SOC. After the first P0 button press the device no longer responds to button presses or if I try to update the HANDLE_HELLO_SENSOR_CONFIGURATION and it certainly appears the device has gone into a DEEP_SLEEP mode as P14/P38 which is attached to the LED drops to GND.
Any ideas on why the same firmware behaves differently on the SOC than the Module?
I have already implemented the XTAL Warmup addition to the project.