mirror of
https://github.com/UpsilonNumworks/Upsilon.git
synced 2026-05-09 08:25:44 +02:00
[GH-ISSUE #385] Experimental support for NumWorks N0120 locked model #180
Labels
No labels
bug
duplicate
easy
enhancement
enhancement
fixed
fixed
good first issue
hard
invalid
pull-request
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Upsilon#180
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Robert404-user on GitHub (Oct 29, 2025).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/385
Hi, I’d like to request or at least start a discussion about adding experimental support for the NumWorks N0120. From what I know, the N0120 ships with a patched and locked bootloader that prevents the usual Phi or recovery unlock path used by other models like N0110, so the normal Upsilon installer can’t run on any N0120.
There are hints that low level MCU drivers for the N0120 exist, and someone found relevant HAL and driver files, which might make a port possible if the install or boot process can be adapted, or if an alternate recovery path can be used. It would be great if the Upsilon team could look into whether those drivers can be integrated or if a safe, documented install path, even experimental, could be made available.
If needed, I can help by testing on an N0120.
Thanks!