Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watchdog Messages with Omnibus Nano V6 and latest master #14606

Closed
anbello opened this issue Jun 15, 2020 · 8 comments
Closed

Watchdog Messages with Omnibus Nano V6 and latest master #14606

anbello opened this issue Jun 15, 2020 · 8 comments

Comments

@anbello
Copy link
Contributor

anbello commented Jun 15, 2020

Issue details
I built ArduCopter from master (82480f0) for Omnibus Nano V6 after adding
define HAL_WITH_DSP 1
to hwdef.dat to have dynamic FFT, I already did this with past version without any problems.

After reboot (sometimes), I see messages relative to watchdog that resolves after next reboot, then the copter works (and fly) with no problems.

Another problem I see with this board is that the logs I get often miss some messages, this is true even without the mod to have dynamic FFT, this board writes log on flash memory. Maybe the two problems are related, I don't know.

Follows an extract of messages on GCS and (attached) a tlog and dflog.


[MAV 001:1] SUCCESS: Executed CMD: 246
[MAV 001:1] Found corrupt log 7 at 0x5471, erasing
[MAV 001:1] Calibrating barometer
[MAV 001:1] Initialising ArduPilot
[MAV 001:1] Barometer 1 calibration complete
[MAV 001:1] INS: alloc 6144 bytes for ISB (free=64144)
[MAV 001:1] EKF3 IMU0 buffs IMU=6 OBS=2 OF=5 EN:5, dt=0.0120
[MAV 001:1] EKF3 IMU0 initialised
[MAV 001:1] EKF3 IMU0 tilt alignment complete
[MAV 001:1] RCInput: decoding IBUS
[MAV 001:1] Found 7 complete logs at 0x0001-0x5470
[MAV 001:1] Baro: skipping calibration after WDG reset
[MAV 001:1] INS: alloc 6144 bytes for ISB (free=64144)
[MAV 001:1] Restored watchdog attitude -1 0 -0
[MAV 001:1] EKF3 IMU0 buffs IMU=6 OBS=2 OF=5 EN:5, dt=0.0120
[MAV 001:1] EKF3 IMU0 initialised
[MAV 001:1] EKF3 IMU0 tilt alignment complete
[MAV 001:1] WDG: T6 SL419 FL0 FT0 FA0 FTP0 FLR0 FICSR0 MM0 MC0
[MAV 001:1] IE32768 IEC13 TN:
[MAV 001:1] PreArm: Internal errors 0x800 l:225 ,watchdog_rst
[MAV 001:1] WDG: T6 SL419 FL0 FT0 FA0 FTP0 FLR0 FICSR0 MM0 MC0
[MAV 001:1] IE32768 IEC13 TN:
[MAV 001:1] WDG: T6 SL419 FL0 FT0 FA0 FTP0 FLR0 FICSR0 MM0 MC0
[MAV 001:1] IE32768 IEC13 TN:
[MAV 001:1] WDG: T6 SL419 FL0 FT0 FA0 FTP0 FLR0 FICSR0 MM0 MC0
[MAV 001:1] IE32768 IEC13 TN:
[MAV 001:1] PreArm: Internal errors 0x800 l:225 ,watchdog_rst
[MAV 001:1] WDG: T6 SL419 FL0 FT0 FA0 FTP0 FLR0 FICSR0 MM0 MC0
[MAV 001:1] IE32768 IEC13 TN:
[MAV 001:1] SUCCESS: Executed CMD: 246

Version
ArduCopter V4.1.0-dev (82480f0)

Platform
[ ] All
[ ] AntennaTracker
[x] Copter
[ ] Plane
[ ] Rover
[ ] Submarine

Airframe type
X quadcopter

Hardware type
Omnibus Nano V6

Logs
2020-06-14 16-10-48.tlog.zip

20-06-14_14-26-00.zip

@anbello
Copy link
Contributor Author

anbello commented Jun 16, 2020

I did other test with master from yesterday (7f42930) and I see no more WDG messages, maybe this commit form @tridge 7f42930 solved the issue.

@rmackay9
Copy link
Contributor

@anbello, well, that would be great if this has fixed it. This fix you mention is included in Copter-4.0.4-rc2.

@tridge
Copy link
Contributor

tridge commented Jun 17, 2020

I suspect it is just that your dataflash is fully erased now, so you're not getting the delays. I doubt my change fixed it

@peterbarker
Copy link
Contributor

@anbello you could try setting LOG_DISARMED and waiting for stuff to fill up and then doing a log-erase; that should trigger the watchdog.

@anbello
Copy link
Contributor Author

anbello commented Jun 17, 2020

@anbello you could try setting LOG_DISARMED and waiting for stuff to fill up and then doing a log-erase; that should trigger the watchdog.

I will do asap.
How can I know when the flash is full? Will I see a message?

@andyp1per
Copy link
Collaborator

You won't see a message - the log will just wrap. You will know when listing the logs gives you a single log of 16Mb. You can speed this up by setting your LOG_BITMASK to everything

@anbello
Copy link
Contributor Author

anbello commented Jun 17, 2020

I did as @peterbarker said above, for two times, and I see no watchdog messages.
It seems all OK.

@peterbarker
Copy link
Contributor

Thanks @anbello

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants