[riot-notifications] [RIOT] Hard Fault on iot-lab_m3 platform (#3275)

Kévin Roussel notifications at github.com
Tue Jun 30 11:56:59 CEST 2015


Hello everyone,

When performing extensive experimentations of my RIOT code on IoT-LAB M3 nodes, I regularily encounter `HARD FAULT` panics.

Reading the ARM Cortex-M manual indicates that Hard Faults are non recoverable, hardware-generated exceptions, usually provoked by interruption (mis)management.

Since I also get the impression that in my experimentations, I am sometimes facing problems that might indicate that some IRQs I should receive do not "register" and launch the corresponding handler, I wonder if there could be some problem in RIOT's interruption management on that platform.
More precisely: the ARM NVIC is a complex beast, and there are many ways to have subtle bugs related to its configuration.

Is there many experiments/projects on the `iot-lab_m3` platform? Is anybody encountering similar problems?

---
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/3275
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20150630/d7ed7cf8/attachment.html>


More information about the notifications mailing list