Hi all,
We just received the trackpad / keyboard firmware. If it checks-out and we're happy with it I'll try to push it by end of the day on Monday.
I'll update this post in the event that something isn't right with the firmware.
[update Nov 15] Testing the firmware today. The compiling and flashing processes are rather involved, especially the latter, so this will need to be automated as much as possible.
[update Nov 16] We're still working on getting everything functional. As we're going though this process we're also figuring out how much this can be automated for end users. Its taking some time because the source code + documentation we're working with aren't exactly great.
Huge shout-out to @xalius for doing much of the leg-work on this; fixing and making stuff work.
Once we've got it all figured out on our end, I'll make sure to write up proper documentation for the process before pushing it to end-users, including steps to take if you mess something up.
For end users the process will likely consist of running 3 scripts in a sequence. Out of the 3 stages the only really tricky one is number 2 as it requires you to identify the trackpad bus and device.
Here are the stages:
Permit a couple of days to get the flashing process completely ironed out and rock solid.
[update Nov 22]
We have the fix. At the time of writing the fix is being beta tested.
I'll close this thread and start a new one once the fix gets distributed.
We just received the trackpad / keyboard firmware. If it checks-out and we're happy with it I'll try to push it by end of the day on Monday.
I'll update this post in the event that something isn't right with the firmware.
[update Nov 15] Testing the firmware today. The compiling and flashing processes are rather involved, especially the latter, so this will need to be automated as much as possible.
[update Nov 16] We're still working on getting everything functional. As we're going though this process we're also figuring out how much this can be automated for end users. Its taking some time because the source code + documentation we're working with aren't exactly great.
Huge shout-out to @xalius for doing much of the leg-work on this; fixing and making stuff work.
Once we've got it all figured out on our end, I'll make sure to write up proper documentation for the process before pushing it to end-users, including steps to take if you mess something up.
For end users the process will likely consist of running 3 scripts in a sequence. Out of the 3 stages the only really tricky one is number 2 as it requires you to identify the trackpad bus and device.
Here are the stages:
- Stage 1) puts the keyboard in a state that allows you to bypass it for trackpad flashing
- Stage 2) flashes new firmware to the trackpad
- Stage 3) flashes keyboard firmware so it is usable again
Permit a couple of days to get the flashing process completely ironed out and rock solid.
[update Nov 22]
We have the fix. At the time of writing the fix is being beta tested.
I'll close this thread and start a new one once the fix gets distributed.