Finally... The touchpad works great!

[moonwalkers]

That said, middle click via three finger tap is still difficult. The workaround is to tap very quickly.

As I've mentioned in another topic, three-finger tap works fine if you adjust the maximum time for tap detection. By default it's 180ms, I've increased it on my system to 330ms.

[jpalus]

Didn't work for me. I took a screenshot of the terminal output figuring it'd help but there's no way to attach images directly to the forum.

Code:

>>> Verify mismatch: type=f2, pass=e2, received=d2
EEE Touchpad verify data failed type:242 pass:226
EEE Touchpad erase failed
>>> USB device closed

Had the same issue but in my case I'm guessing it was due to active USB hub attached to PBP that likely kept keyboard powered on even after powering off PBP. After cutting external power from hub update process went fine. Or maybe it was using step-2 for ISO keyboard even though I have ANSI?  (I have ISO PBP with keyboard swapped for ANSI, so at least touchpad is from "ISO" version if it matters). No idea, one of these.

All in all touchpad works way way better now. And even Mod4+arrows started to work.

[PRStoetzer]

I wasn't able to compile the updater using the instructions on Github for Arch Linux. Compilation failed due to a missing file, sys/cdefs.h. I booted Debian via the sdcard and had no issues compiling.

I did, however, have issues using an external USB keyboard after stage 1. I use Arch Linux via https://github.com/SvenKiljan/archlinuxarm-pbp, which uses Tow-Boot. Tow-Boot requires either a CTRL-C or ESC to choose a different boot method. Since I have an ANSI PBP, I wasn't able to use the PBP keyboard or an external keyboard to issue CTRL-C/ESC. Fortunately the external keyboard started working only after Tow-Boot booted Arch, and then I was able to mount the sdcard and run stage 2 and the flash-kb command.

The touchpad is very much improved. That said, middle click via three finger tap is still difficult. The workaround is to tap very quickly. Like another poster, I'm also finding that if I gently brush the touchpad while typing, the touchpad unfortunately will register a click.

This is a major improvement. Thanks!

I had the same issue with compiling. I was able to fix it in Arch by reinstalling the glibc package.

[jpalus]

Yet to see whether it prevents touchpad from starting to behave erratic until machine is rebooted, but yes, definitely an improvement. Though I wouldn't call it perfect just yet.

If this is the same issue as https://forum.pine64.org/showthread.php?tid=11862 then I'm afraid it's not solved. Just got it again on new firmware.

[KC9UDX]

If this is the same issue as https://forum.pine64.org/showthread.php?tid=11862 then I'm afraid it's not solved. Just got it again on new firmware.

If you installed the firmware according to this thread, I would suggest that you probably have unrelated hardware/software problems; only because most of us are not having trouble. Either your trackpad is defective, the microcontroller didn't flash with the new firmware, or, your operating system or further-down-the-line software has a problem.

[jpalus]

If you installed the firmware according to this thread, I would suggest that you probably have unrelated hardware/software problems; only because most of us are not having trouble.  Either your trackpad is defective, the microcontroller didn't flash with the new firmware, or, your operating system or further-down-the-line software has a problem.

And what makes you say that exactly? I already admitted new firmware works way better than before which I guess pretty much proves that it was loaded successfully.

Described issue is not easy to reproduce -- it occurs rarely usually after many hours spent at PBP. If feels almost as if firmware went into some loop which it cannot exit until reboot. It's not something that happens all the time. And judging by this forum I'm not the only one experiencing the issue. Just noted that new firmware does not solve this one. It's possible that touchpad is defective... wouldn't be the first defective part in my PBP.

And I'm all ears to hear how software can be responsible for generating hardware events.

[KC9UDX]

Please don't think I was trying to belittle you. It was a simple statement of logic. If A then B. My point was that this doesn't seem to be something that the new firmware would address, or it would be present in all of them. You have effectively isolated the problem to your device, and those of others with the same problem

Unless you actually measure interrupts with a logic probe, you never really know that software isn't the problem. It's probably not in this case, but it sure can happen, especially these days considering how complicated software has become. Troubleshooting these things is a very painstaking process. No, I'm not saying that you aren't aware of this, or haven't done it.

[midnightcheese]

Huge improvement, thank you!

[bootsup]

I installed the Manjaro package on my early 2021 PBP.

Step 1 and Step 2 were successful. However:

Code:

$ sudo pbp-fwupdate flash-kb firmware/default_ansi.hex

Please note that updating the firmware carries a small risk
of permanently disabling the trackpad and keyboard, effectively
bricking them.  Proceed at your own risk.

Press Ctrl+C within the next five seconds to cancel... 5 4 3 2 1

Segmentation fault

[danacr]

this is so much better! it really makes the touchpad usable, thank you so much!!!