hatlabs / sh-rpi

Sailor Hat for Raspberry Pi documentation
Other
2 stars 1 forks source link

Documentation incorrect about how to disable Watchdog (solder jumper mentioned does not exist) #18

Open chrisclaydon opened 2 months ago

chrisclaydon commented 2 months ago

The hatlabs website page about the sailor hat says there is a solder jumper to disable the watchdog but I can't see one. The docs explain how it works but they don't say where it is. All the other jumpers are clearly labelled in the drawing and on the PCB. I can't even see an unlabelled jumper which might be it.

I'm not sure whether this is an issue with the documentation or whether the jumper is actually missing from the board.

Background:

I have an issue with the raspberry pi suddenly rebooting itself about ten seconds after another task starts using an I2C device. There is no clash of the I2C IDs and it's not using much bandwidth but if I stop the other task using I2C within ten seconds then the reboot doesn't occur so I'm suspicious that the other i2c device is disrupting the heartbeat signal somehow.

I would like to determine whether the sailor hat is triggering the reboot or whether it is something else like a segmentation fault. I thought disabling the watchdog would be the easiest way to eliminate it but I can't work out how to do that.

Thanks for your help!

chrisclaydon commented 2 months ago

Update: I discovered a command which isn't properly documented on the website: shrpi set watchdog 0 This command disabled the watchdog successfully. The documentation on the "hardware" page of the website referring to solder jumpers in several places is definitely incorrect and should be corrected to point the reader to this command instead.

And the Sailor hat was causing the reboots when the i2c bus was used by another task, it works ok with watchdog disabled. I'm not sure yet why they wouldn't share nicely, they both work ok separately.

mairas commented 2 months ago

Thank you! The solder jumper was a feature of the v1 board and was accidentally left in place in the v2 docs. I have updated the documentation accordingly.

As for the I2C issue - have you verified the devices are using different I2C addresses?