Pocket Reform System Controller issue?

I have been fighting random system controller communication issues.

Reform-Check

Leaving the system on or off plugged in to power or not the battery level in the OS will go to zero and the keyboard controller will show a T . I can not narrow down how or when it will error out.
To reset it I may need to flip the hardware power switch one or more times.

Is there a way to reset it via the command line?
I have not reseated cables and screen position does not seem to effect anything.

Thank you for any reccomendations.

I have a new System Controller + accompanying keyboard firmware in the works and almost ready to release which has a new command line interface directly in the keyboard OLED, which will help debug issues like this. Lets hope I can get a beta out later today.

4 Likes

This sounds good, I will need to tweak the keyboard and recompile with my layout but that all sounds great.

I have updated to the latest firmware. Unfortunately the issue seems to persist though different symptoms. Is the new API documented or is there a command that can test the system controller to keyboard communication or reset the system controller?
The below post seems to also be related. This is making me wonder if it is also related to attempting custom cpupower settings. I have been attempting to throttle the CPU to reduce heat. I will retry with default settings.

The way i feel it is similar is that only a hard system controller power cycle seems to fix the issue.
Currently my battery status does not show up properly.
Keyboard display show status run may or may not show the system controller firmware number 20260819. it seems like it is trying to show depending on device status at time of the request.

dmesg is shoming this continuosly.

[ 1317.088021] mnt_sc spi0.0: cmd failed after 10 retries!
[ 1317.088073] power_supply BAT0: driver failed to report voltage_now' property: -16 [ 1317.719314] mnt_sc spi0.0: cmd failed after 10 retries! [ 1317.719366] power_supply BAT0: driver failed to report status’ property: -16
[ 1317.745483] mnt_sc spi0.0: mntsc: couldn’t parse response: err maxp
[ 1318.314478] mnt_sc spi0.0: cmd failed after 10 retries!
[ 1318.314531] power_supply BAT0: driver failed to report status' property: -16 [ 1318.946650] mnt_sc spi0.0: cmd failed after 10 retries! [ 1318.946703] power_supply BAT0: driver failed to report status’ property: -16
[ 1319.770855] mnt_sc spi0.0: cmd failed after 10 retries!