[GH-ISSUE #158] Epsilon Beta version #49

New issue

Closed

opened 2026-05-06 13:14:49 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-06 13:14:49 +02:00

Owner

Originally created by @loretoparisi on GitHub (Feb 12, 2022).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/158

I have installed Epsilon Beta 18:

{
	"id": 82,
	"version": "18.0.0",
	"patch_level": "27aa79b",
	"device_model": {
		"id": 2,
		"name": "N0110"
	},
	"size": 2561053
}

available here

while having before the stable:

{
	"id": 80,
	"version": "17.2.0",
	"patch_level": "d72084e",
	"device_model": {
		"id": 2,
		"name": "N0110"
	},
	"size": 2537821
}

that is available here.

In both cases I cannot install upsilon, and I cannot revert back to a version of Epsilon <= 16 ( It seems that dfu file is not available).

I have then tried the following

   dfu-util -i0 -a0 -s 0x20030000:force:leave -D flasher.verbose.bin
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0483:a291
Device DFU version 0100
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0100
Warning: DfuSe option used on non-DfuSe device
Device returned transfer size 2048
DfuSe interface name: "Flash"
Downloading element to address = 0x20030000, size = 26712
Erase   	[=========================] 100%        26712 bytes
Erase    done.
Download	[=========================] 100%        26712 bytes
Download done.
File downloaded successfully
Submitting leave request...
Transitioning to dfuMANIFEST state

and then

mbploreto:~ loretoparisi$ dfu-util -D /Users/loretoparisi/Downloads/epsilon.dfu 
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Match vendor ID from file: 0483
Match product ID from file: a291
Multiple alternate interfaces for DfuSe file
Opening DFU capable USB device...
Device ID 0483:a291
Device DFU version 0100
Claiming USB DFU Interface...
Setting Alternate Interface #1 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0100
Device returned transfer size 2048
DfuSe interface name: "SRAM"
DfuSe interface name: "Flash"
File contains 1 DFU images
Parsing DFU image 1
Target name: ST...
Image for alternate setting 0, (2 elements, total size = 1131000)
Setting Alternate Interface #0 ...
Parsing element 1, address = 0x90000000, size = 1121480
Erase   	[=========================] 100%      1121480 bytes
Erase    done.
Download	[=========================] 100%      1121480 bytes
Download done.
Parsing element 2, address = 0x08000000, size = 9504
dfu-util: Last page at 0x0800251f is not writeable

I have then attempt use the Connection Kit for unlocked Numworks here and the flashing app porting of WebDFU to Numrworks vendor here, failing in both cases, getting errors like

Start address 0x8000000 outside of memory map bounds

So in my understanding, as soon as you upgrade from Numworks web site, there is no way anymore to restore, until doing since risky hack (here in French)

Being a TI-89 user and developer of the old days, and remembering when Texas Instruments decided to provide the OS of the TI-89 open to emulator users (after a long battle from us developers) I find this very frustrating , if there is any help out there is welcome!

Originally created by @loretoparisi on GitHub (Feb 12, 2022). Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/158 I have installed Epsilon Beta 18: ```json { "id": 82, "version": "18.0.0", "patch_level": "27aa79b", "device_model": { "id": 2, "name": "N0110" }, "size": 2561053 } ``` available [here](https://my.numworks.com/firmwares/N0110/beta.dfu) while having before the `stable`: ```json { "id": 80, "version": "17.2.0", "patch_level": "d72084e", "device_model": { "id": 2, "name": "N0110" }, "size": 2537821 } ``` that is available [here](https://my.numworks.com/firmwares/N0110/stable.dfu). In both cases I cannot install `upsilon`, and I cannot revert back to a version of Epsilon <= 16 ( It seems that dfu file is not available). I have then tried the following ``` dfu-util -i0 -a0 -s 0x20030000:force:leave -D flasher.verbose.bin dfu-util 0.11 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ dfu-util: Warning: Invalid DFU suffix signature dfu-util: A valid DFU suffix will be required in a future dfu-util release Opening DFU capable USB device... Device ID 0483:a291 Device DFU version 0100 Claiming USB DFU Interface... Setting Alternate Interface #0 ... Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 0100 Warning: DfuSe option used on non-DfuSe device Device returned transfer size 2048 DfuSe interface name: "Flash" Downloading element to address = 0x20030000, size = 26712 Erase [=========================] 100% 26712 bytes Erase done. Download [=========================] 100% 26712 bytes Download done. File downloaded successfully Submitting leave request... Transitioning to dfuMANIFEST state ``` and then ``` mbploreto:~ loretoparisi$ dfu-util -D /Users/loretoparisi/Downloads/epsilon.dfu dfu-util 0.11 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Match vendor ID from file: 0483 Match product ID from file: a291 Multiple alternate interfaces for DfuSe file Opening DFU capable USB device... Device ID 0483:a291 Device DFU version 0100 Claiming USB DFU Interface... Setting Alternate Interface #1 ... Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 0100 Device returned transfer size 2048 DfuSe interface name: "SRAM" DfuSe interface name: "Flash" File contains 1 DFU images Parsing DFU image 1 Target name: ST... Image for alternate setting 0, (2 elements, total size = 1131000) Setting Alternate Interface #0 ... Parsing element 1, address = 0x90000000, size = 1121480 Erase [=========================] 100% 1121480 bytes Erase done. Download [=========================] 100% 1121480 bytes Download done. Parsing element 2, address = 0x08000000, size = 9504 dfu-util: Last page at 0x0800251f is not writeable ``` I have then attempt use the Connection Kit _for unlocked Numworks_ [here](https://www-fourier.univ-grenoble-alpes.fr/~parisse/nws_en.html) and the flashing app porting of WebDFU to Numrworks vendor [here](https://ti-planet.github.io/webdfu_numworks/n0110/), failing in both cases, getting errors like ``` Start address 0x8000000 outside of memory map bounds ``` So in my understanding, as soon as you upgrade from Numworks web site, there is no way anymore to restore, until doing since risky hack ([here in French](https://tiplanet.org/forum/viewtopic.php?f=113&t=25191)) Being a TI-89 user and [developer](https://github.com/loretoparisi/control-system-toolbox-for-ti89) of the old days, and remembering when Texas Instruments decided to provide the OS of the TI-89 open to emulator users (after a long battle from us developers) I find this very frustrating , if there is any help out there is welcome!

BreizhHardware closed this issue

2026-05-06 13:14:49 +02:00

BreizhHardware commented

2026-05-06 13:14:50 +02:00

Author

Owner

@apoleon33 commented on GitHub (Feb 12, 2022):

you got it right, the only way to install a different firmware after installing e16, e17 etc is to "unblock" your numwork using the tutorial you found in french.

@apoleon33 commented on GitHub (Feb 12, 2022): you got it right, the only way to install a different firmware after installing e16, e17 etc is to "unblock" your numwork using the tutorial you found in french.

BreizhHardware commented

2026-05-06 13:14:50 +02:00

Author

Owner

@Lauryy06 commented on GitHub (Feb 14, 2022):

Yes, we are sorry but we are not able to help you, so I will close the issue...

@Lauryy06 commented on GitHub (Feb 14, 2022): Yes, we are sorry but we are not able to help you, so I will close the issue...

BreizhHardware referenced this issue

2026-05-06 13:16:19 +02:00

[PR #49] [MERGED] Allow themes to override default colors #221