Reach v2.2.2 reboots every 15 minutes or so

Reach Module / M+ / M2 Hardware integration
1

I’ve been experiencing many reboots of the Reach for v2.2.2 when connected to a Pixhawk and sometimes when connected to the laptop via USB. Multiple Reaches on different Pixhawks have had the problem so I don’t believe it is hardware specific. I reported the problem initially here:

I’m attaching a dmesg log file from my Reach that rebooted recently. I noticed this error that might be related:
2.207740] pmic_ccsm rpmsg3: Probed pmic_ccsm rpmsg device
[ 2.207969] pmic_ccsm pmic_ccsm: PMIC-ID: c9
[ 2.207992] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk
[ 2.216972] pmic_ccsm pmic_ccsm: Battery Over heat exception
[ 2.222705] pmic_ccsm pmic_ccsm: Battery Zone changed. Current zone is 5
[ 2.225427] APIC ID: 0

dmesg.log (51.5 KB)

panic.log (111.0 KB)

2

Hi Rob,

We have this reported by other user as well during the weekend and have an idea what might be causing the issue. Will investigate this further today.

3

We found the cause and will be releasing a hot fix later today.

4

Terrific. Do you have an estimated time of release?

5

Guys are uploading it .

1 Like
6

Looks like 2.2.3 is available now! Great work!

7

Yep, please give it a shot and let us know if the issue is gone. Thanks for the report!