02-22-2019, 08:08 PM
(This post was last modified: 02-22-2019, 08:17 PM by nemunaire.
Edit Reason: wording
)
I tried to find the cause of this issue.
This is not a kernel problem as: a reset in u-boot doesn't work neither, and both calls from u-boot or linux arrived in the ATF function sunxi_system_reset (I was able to print debug messages in this function).
The things that's quite interesting is that the sunxi_system_reset (https://github.com/ARM-software/arm-trus...i_pm.c#L72) makes use of the watchdog to perform a reboot. As we are unable to use the watchdog with the clusterboard, this is coherent with the reboot issue.
Watchdog's registers are correctly set: values are the good ones, given by the A64 user manual, and the instructions flow is stopped after the requested delay (whether asked by the Linux driver or by ATF). Most probably, something went wrong during the reset, perhaps the boot sequence skip the SD/MMC or select FEL mode?
But, this is the same code that is used for Pine64, SOPine, ...
I'm wondering if this also happen on the SOPine baseboard; it could help to know if there is something weird only on the clusterboard side or if it's on the SOPine module.
This is not a kernel problem as: a reset in u-boot doesn't work neither, and both calls from u-boot or linux arrived in the ATF function sunxi_system_reset (I was able to print debug messages in this function).
The things that's quite interesting is that the sunxi_system_reset (https://github.com/ARM-software/arm-trus...i_pm.c#L72) makes use of the watchdog to perform a reboot. As we are unable to use the watchdog with the clusterboard, this is coherent with the reboot issue.
Watchdog's registers are correctly set: values are the good ones, given by the A64 user manual, and the instructions flow is stopped after the requested delay (whether asked by the Linux driver or by ATF). Most probably, something went wrong during the reset, perhaps the boot sequence skip the SD/MMC or select FEL mode?
But, this is the same code that is used for Pine64, SOPine, ...
I'm wondering if this also happen on the SOPine baseboard; it could help to know if there is something weird only on the clusterboard side or if it's on the SOPine module.