Alastair D'Silva

I also have the same problem, V+ drops to 5V when the probe is connected, 24V when it's not. Moving the 24V line to one of the fan headers fixes...

After the initial commit to add extra information on docker failures, the following error is frequently seen: Failed to kill container '48118b1b0a9c91345aa06c2b12a0680c13093a2a7b850e6d7fe7cd314409305c'. Error 143: '','' The same sometimes occurs with...

Rebased on current master

Not that I can figure out, It seems to happen sporadically - maybe 1% of the time (which is enough to occur once or twice a day in our environment).

I had a weird (related) issue pop up this morning: [_pipeline_v4.12-rc2-AETYLZGI2S3TTCDSKWSBXVS2QZCBVH] Running shell script + docker inspect -f . linux-cppcheck . Failed to run image 'linux-cppcheck'. Error 143: '42103a5c6138b277f140d269935f2a3c1e8997650db6541f84ee9901a99c336f','' This...

Rebased onto master

Is the BCM mapping intended to be a mapping to the pin on the chip, or the Linux GPIO number? I'm asking as we want to fix up the BCM...

I'm digging through the Allwinner reference manual (http://linux-sunxi.org/images/a/a3/Allwinner_H5_Manual_v1.0.pdf) and it looks like Allwinner don't have the concept of a number for a GPIO line, just the standard ARM Port/Pin names...

I see, so you are labelling the pin in the header with the BCM assignments that were used on (some variant of) a raspberry pi, and then mapping that back...

At the very least, the BCM dicts put forward for the Orange Pi PC & friends, which is just a copy of the board dict, is a red herring, and...