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

by **GuyInFreezer** » 30 Aug 2018, 17:00

Hello!

So I followed the instruction and managed to put CAS OS in my calculator.

In About page, it says that my boot 2 code version is 255.25.5.65535. Is this normal?

And if it isn't normal, is it tied to why the cas patcher isn't working?

The OS is 4.5.

by **critor** » 30 Aug 2018, 22:01

Yes, the fake Boot2 version is normal. It's to prevent the Boot2 from being updated to an incompatible version.
It has nothing to do with the CAS patches.

by **GuyInFreezer** » 31 Aug 2018, 13:55

Ah, I see.

Also, apparently my calculator is crashing on any math input, not just a CAS function X.X
Any suggestion on where to start to fix this?

EDIT: To clarify, ndless is working. The calculator works as intended if non-CAS OS is installed.

by **critor** » 31 Aug 2018, 15:40

If any math input crashes, then the problem is with the patch.

If you installed the 4.5 CAS OS on a non-CAS calculator, the patch is this one :
https://github.com/parrotgeek1/TI-Nspir ... 0.1180.tns

It has to be put in a /ndless/startup/ folder.

Then to enable it you'll need either to :
- open the patch once
- restart your calculator with the reset button on the back

by **GuyInFreezer** » 02 Sep 2018, 02:56

Oh, silly me. I didn't think about actually running the patcher.
Thanks!

by **critor** » 02 Sep 2018, 09:13

Thanks for confirming it works.

by **kittensauce** » 01 Oct 2018, 01:29

Hello. I asked a few questions on the first page of this thread, and now I have a few more!

1. Does ControlX still overclock the calculator? I recall it doing so in earlier versions, but now it displays "CPU=198" when booting, which I believe is the default clock speed.
2. Is there any way to

completely

uninstall nBoot/ControlX, and restore the calculator to its factory configuration? I tried doing so a while ago by haphazardly deleting partitions and restoring images (it wasn't a very good idea, in retrospect) so I could give the calculator to someone who didn't need any sort of third-party software. While it worked (for the most part), I was left with the black & white boot screen, and I fear I might have messed something up in nsPartManagic.

Thanks again!

by **parrotgeek1** » 01 Oct 2018, 04:38

kittensauce wrote:Hello. I asked a few questions on the first page of this thread, and now I have a few more!

1. Does ControlX still overclock the calculator? I recall it doing so in earlier versions, but now it displays "CPU=198" when booting, which I believe is the default clock speed.
2. Is there any way to
completely
uninstall nBoot/ControlX, and restore the calculator to its factory configuration? I tried doing so a while ago by haphazardly deleting partitions and restoring images (it wasn't a very good idea, in retrospect) so I could give the calculator to someone who didn't need any sort of third-party software. While it worked (for the most part), I was left with the black & white boot screen, and I fear I might have messed something up in nsPartManagic.

Thanks again!

1) it does; 156 is the default on A-V
2) to fix that you need to flash the appropriate "standard v2" manuf for the calculator (in the archives here)

by **kittensauce** » 03 Oct 2018, 01:08

parrotgeek1 wrote:1) it does; 156 is the default on A-V
2) to fix that you need to flash the appropriate "standard v2" manuf for the calculator (in the archives here)

1) Oh, thanks for correcting me. I assume that 196MHz is the safest "universal" clock speed? Would it be possible to change the overclock values to those provided by Nover's autoconfiguration? Would it even be safe to set the values above average that early in the boot process?
2) Thanks, I'll keep that in mind. I don't have access to the calculator at the moment, but I'll try to fix it if I ever have the chance.

by **critor** » 03 Oct 2018, 10:56

196MHz is the highest safe optimal value. Higher frequencies aren't that interesting because :
- a AHB slightly higher than 66MHz is likely to silently but progressively corrupt your NAND data
- and if you lower the AHB, it will be much lower than 66MHz and thus impact the NAND performances

The next value which can be set with a 66MHz AHB is 264MHz, and I've never seen a CX calculator able to reach that.

Also, I've already seen some (rare) CX calculators being unreliable at more than 210MHz.
So hard-coding a value much higher than 196MHz in ControlX is dangerous.

But note that if you have Ndless + Nover set up, you'll calculator will still be overclocked from 196MHz to the highest safe value detected/set in Nover once the OS is launched.