[Tuto] [EN/FR] Install/Installer nBoot + ControlX (+Linux)

→ **MyCalcs** profile · by **heimdall** » 18 Jan 2018, 08:21

parrotgeek1 wrote:
heimdall wrote:You said it takes about 4-5 minutes, it's been 10 and still like this. Running i7-2860QM 2.5GHz - 3.6GHz on Turbo with 8GB of RAM if that matters.

on my computer I have an SSD so it's faster

heimdall wrote:On side note, is it normal that os.bin is 32MB?

yes, it's a dump of the ram lol

Yeah, I have a dirty old 1TB 5400RPM HDD

→ **MyCalcs** profile · by **heimdall** » 18 Jan 2018, 08:22

parrotgeek1 wrote:
heimdall wrote:I forked parrotgeek's repo, I am not sure how you use github, I usually download from it, not upload to it

https://github.com/deadmeatpt/TI-Nspire/tree/deadmeatpt-patch-4.5.0/patchfinder
it's the cas_patch_4.5.0.1180.tns

Thanks but there's a bug in it, where it doesn't find a certain kind of patch, directly referencing 900a002c:

1095cdec: e59f3bbc ldr r3,[1095d9b0] = 900a002c
1095cdf0: e5933000 ldr r3,[r3]

But related to 4.5? It seems to work fine in mine. Might be just a function or so

→ **MyCalcs** profile · by **critor** » 19 Jan 2018, 20:07

Changed the sdram size from 64 to 32MB in the manuf shared previously.
nBoot is still crashing on 32MB CX/Color prototypes, so it's something else :

Code: Select all: Boot Loader Stage 1 (3.00.DEVBUILD) Build: 2010/9/14, 16:30:29 Copyright (c) 2006-2010 Texas Instruments Incorporated Using developer keys Last boot progress: 65 Warning at PC=00007718: Bad write_byte: 0001c634 00 Available system memory: 33196 Checking for NAND: NAND Flash ID: Generic 1 GBit (0xA1) SDRAM size: 32 MB Wakeup Event: ON. SDRAM memory test: Pass Clearing SDRAM...Done. Clocks: CPU = 132MHz AHB = 66MHz APB = 33MHz Unlocked! Boot Loader Stage 1 (3.00.DEVBUILD)

→ **MyCalcs** profile · by **critor** » 20 Jan 2018, 12:19

My patch was based on nBoot v1.

Strangely, by restarting everything from scratch with nBoot v2, it now seems to works.

Code: Select all: Boot Loader Stage 1 (3.00.DEVBUILD) Build: 2010/9/14, 16:30:29 Copyright (c) 2006-2010 Texas Instruments Incorporated Using developer keys Last boot progress: 65 Warning at PC=00007718: Bad write_byte: 0001c634 00 Available system memory: 33196 Checking for NAND: NAND Flash ID: Generic 1 GBit (0xA1) SDRAM size: 64 MB Wakeup Event: ON. SDRAM memory test: Pass Clearing SDRAM...Done. Clocks: CPU = 132MHz AHB = 66MHz APB = 33MHz Unlocked! Clearing SDRAM...Done. Clearing SDRAM...Done. Boot option: Normal Read of bootdata failed Loading code from Diags... Diags size invalid! Error reading/validating DIAGS image Error loading DIAGS. Switching to BOOT2. Loading BOOT2 software... Error reading/validating BOOT2 image Error loading BOOT2, looking for pre-installed images. Checking for DIAGS image in pre-install area. No DIAGS image found. Checking for BOOT2 image in pre-install area. No BOOT2 image found. Error loading BOOT2, install new version. Checking battery level. Battery level is OK. Ready to download BOOT2 software... Begin XMODEM file transfer.

Download : archives_voir.php?id=1340731

Note that ControlX is currently built for Boot1 3.0.0.99, and is not compatible with Boot1 3.0.0.DEVBUILD.
It's probably not complicated to adapt it, but I have no working TI-Nspire Color prototype to test it.

→ **MyCalcs** profile · by **heimdall** » 21 Jan 2018, 00:56

critor wrote:My patch was based on nBoot v1.

Strangely, by restarting everything from scratch with nBoot v2, it now seems to works.

Code: Select all
Boot Loader Stage 1 (3.00.DEVBUILD) Build: 2010/9/14, 16:30:29 Copyright (c) 2006-2010 Texas Instruments Incorporated Using developer keys Last boot progress: 65 Warning at PC=00007718: Bad write_byte: 0001c634 00 Available system memory: 33196 Checking for NAND: NAND Flash ID: Generic 1 GBit (0xA1) SDRAM size: 64 MB Wakeup Event: ON. SDRAM memory test: Pass Clearing SDRAM...Done. Clocks: CPU = 132MHz AHB = 66MHz APB = 33MHz Unlocked! Clearing SDRAM...Done. Clearing SDRAM...Done. Boot option: Normal Read of bootdata failed Loading code from Diags... Diags size invalid! Error reading/validating DIAGS image Error loading DIAGS. Switching to BOOT2. Loading BOOT2 software... Error reading/validating BOOT2 image Error loading BOOT2, looking for pre-installed images. Checking for DIAGS image in pre-install area. No DIAGS image found. Checking for BOOT2 image in pre-install area. No BOOT2 image found. Error loading BOOT2, install new version. Checking battery level. Battery level is OK. Ready to download BOOT2 software... Begin XMODEM file transfer.

Download : archives_voir.php?id=1340731

Note that ControlX is currently built for Boot1 3.0.0.99, and is not compatible with Boot1 3.0.0.DEVBUILD.
It's probably not complicated to adapt it, but I have no working TI-Nspire Color prototype to test it.

I know a guy who had one (not sure if he still has it). He bricked it once, I managed to unbrick it. He installed OS 3.6, I reflashed boot2 3.1 and used nlaunchy to get it back running and did a bootD clean up. If he still has it, I can see if he either gives me or sells me, that probably would give us some margin to work here.

Also that

Code: Select all: Read of bootdata failed Loading code from Diags... Diags size invalid! Error reading/validating DIAGS image Error loading DIAGS. Switching to BOOT2. Loading BOOT2 software... Error reading/validating BOOT2 image Error loading BOOT2, looking for pre-installed images. Checking for DIAGS image in pre-install area. No DIAGS image found. Checking for BOOT2 image in pre-install area. No BOOT2 image found. Error loading BOOT2, install new version. Checking battery level. Battery level is OK. Ready to download BOOT2 software... Begin XMODEM file transfer.

Doesn't look so good

→ **MyCalcs** profile · by **parrotgeek1** » 21 Jan 2018, 01:13

heimdall wrote:
I know a guy who had one (not sure if he still has it). He bricked it once, I managed to unbrick it. He installed OS 3.6, I reflashed boot2 3.1 and used nlaunchy to get it back running and did a bootD clean up. If he still has it, I can see if he either gives me or sells me, that probably would give us some margin to work here.

You have a development version of Boot2 3.1 and OS 3.6? that would be incredibly useful

→ **MyCalcs** profile · by **heimdall** » 21 Jan 2018, 12:53

parrotgeek1 wrote:
heimdall wrote:
I know a guy who had one (not sure if he still has it). He bricked it once, I managed to unbrick it. He installed OS 3.6, I reflashed boot2 3.1 and used nlaunchy to get it back running and did a bootD clean up. If he still has it, I can see if he either gives me or sells me, that probably would give us some margin to work here.

You have a development version of Boot2 3.1 and OS 3.6? that would be incredibly useful

No no, he tried to install OS 3.6 and it would stay in the black with grey bars and clock not spinning. I knew that 3.6 doesn't has a match for the ASIC chip, so I knew he bricked it. He had boot2 3.2.4 too and minimal OS version 3.6, so I flashed 3.1 with TTL and installed nlaunchy 2.3 (back in the day) with OS 3.1, to use DowngradeFix (no nsNandMgr back then

). So it is running 3.1 again (we uninstalled nlaunchy). I sent him a message, but he is probably sleeping yet.

→ **MyCalcs** profile · by **critor** » 21 Jan 2018, 13:00

Maybe you're talking of a TI-Nspire ClickPad prototype, not a TI-Nspire Color prototype.

TI-Nspire/XXXXXXXXXXX ClickPad DVT1.2/DVT2.0 prototypes have different ASIC flags, and won't launch 3.6+ OSes without the help of an appropriate boot loader.
The only one supporting 3.6+ OSes is Nlaunch CXM 2.5.