mirror of
https://github.com/UpsilonNumworks/Upsilon.git
synced 2026-05-09 08:25:44 +02:00
[GH-ISSUE #209] Impossible to build binpack #79
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#79
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 @hugo-b-r on GitHub (Apr 8, 2022).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/209
Describe the bug
When trying to build binpack, it returns an error: "file maybe already patched"
To Reproduce
Steps to reproduce the behavior:
Build latest upsilon-dev or just look at the CI/CD
Expected behavior
I really don't understand what's happening. Maybe that having bootloader binpack make make go like there's too much.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
-binpack for n0110
-latest upsilon: 5365718
@Yaya-Cout commented on GitHub (Apr 8, 2022):
The latest CI hasn't this bug…
@Lauryy06 commented on GitHub (Apr 8, 2022):
The CI crashes before reaching binpack...
@hugo-b-r commented on GitHub (Apr 8, 2022):
Yes but why does it crashes ? I have the same problem on my computer
@Lauryy06 commented on GitHub (Apr 15, 2022):
This is a problem with the USB protection and the bootloader (to make a long story short the area where the "magic" key was stored is used by data at 0xFF now, against 0x00 before). I don't know why, but it should be fixed with #205 (as this system changes).