Panic, bus_fault

[gusgonnet]

Do you have log.info() or serial.print/ln in your code?

There are little issues here and there depending how they are used in the firmware:

Photon 2 does not tolerate Log.info() with a NULL value

Hey, This works fine on Argons and Borons when the variable command is NULL: Log.info("test: %s", command); But it does not work well on Photon 2 (5.8.2 and potentially other deviceOS versions). AI was quick to flag this as a potential red flag: Logging Pointers: Ensure that Log.info can handle NULL pointers gracefully, as logging NULL might cause issues in some logging implementations. Of course, these issues can (and should) be avoided in code, but I realize now that I was relying too …

Is the fw logging on event handlers? do not do it:

SerialLogHandler Issues on Photon 2: Causing BLE Message Duplicates and Delays?

Hi, I am working on a project where two Photon 2's connect via BLE. I have removed the calls to the BLE APIs from BLE handlers per Particle's recommendation. I have also created threads that keep up the BLE conectivity alive. I am using message queues (os_queue) to send messages from BLE handlers to the loop() thread safely. Using DeviceOS 5.9.0 on both devices. Few things that are puzzling me: A- Messages from the peripheral device seem to be duplicated ON the central device Example: T…