Open namasikanam opened 3 years ago
Furthermore, we notice that the color of status LEDs are:
PWR | B/E | ACT | |
---|---|---|---|
FMU | solid green | solid amber | \ |
IO | solid green | solid amber | flashing blue |
The solid amber of FMU B/E indicates that the firmware of the FMU seems in error. What possible reasons for that?
I tried to listen to any logging output from Serial 5, which I assume to be the system console port. But there is nothing when booting.
However, when I booted another firmware, PX4 Flight Stack Stable Release, I can capture the output from Serial 5 (shown below).
Is Serial 5 not the system console port of the SMACCMPilot firmware? If it is, the SMACCMPilot firmware seems to go into the error state even before any logging. How could it happen?
Hi, we are trying to reproduce this amazing project. But we strangely stuck after just uploading the firmware. We are students from Tsinghua formal verification group, not very familiar with embedded developing and pixhawk. We really need and appreciate any help!
What we have done
Description of strange phenomenon
Expected behavior
Context