I am not able to find a device which can reproduce this issue.
The alarm signal status is passed from firmware, here should be the uboot.
As you mentioned above, you used fwts-live image to test your device.
The graphic pass but command line not, which fwts-live you used for testing?
And could you provide the fwts-live test log, graphic and commnand line one?
I am guessing if it is the issue that when setwakeuptime and your device haven't set the Pending to false before FWTS has already got the Pending status.
I don't know if your device can boot to Ubuntu, if yes, I could sent you some test patches for dumping some messages and testing, you can build the fwts and run directly.
I am not able to find a device which can reproduce this issue.
The alarm signal status is passed from firmware, here should be the uboot.
As you mentioned above, you used fwts-live image to test your device.
The graphic pass but command line not, which fwts-live you used for testing?
And could you provide the fwts-live test log, graphic and commnand line one?
I am guessing if it is the issue that when setwakeuptime and your device haven't set the Pending to false before FWTS has already got the Pending status.
I don't know if your device can boot to Ubuntu, if yes, I could sent you some test patches for dumping some messages and testing, you can build the fwts and run directly.