[removed]

[critor]

No problem, we need tests on real hardware for revisions A-V too.

• you need to have Boot1.5 4.4 as the 1st image in your Boot2 partition - usually the case if you've updated to 4.4/4.5 - check with BtMg
• then with BtMg, flash either the nanoloaderCAS_OS.img.tns or nanoloaderNONCAS_OS.img.tns available at https://github.com/parrotgeek1/TI-Nspir ... boot15_exp as 2nd image in your Boot2 partition

No. The boot1.5 is included inside the nanoloader.img

But since BtMg let you flash image by image, no real need to include Boot1.5.
Users can get it somewhere else.

Also, distributing your tool with as few TI code as possible would be better in my opinion.
They'll have fewer valid reasons to ask your hosting service to remove the file.

[critor]

@parrotgeek1
Here's a new unlisted video.

It's better, but the progress bar still seems to jump directly from 25% to 50%.
Are you sure you specified the right values ?

I can't use the syscalls so I am calculating the percentage to draw based on the amount of boot2 that has been decompressed. I'm almost certain my calculations don't make any sense though. They are in imageloader.c

Multiplying the added percentage by 2 would seem to match.

[parrotgeek1]

.

[parrotgeek1]

.

[critor]

I think it would be better too.

[critor]

Ok, here is a script based on your makenanoloader.sh to have just the payload in clean nanoloader*.bin.tns :

Code: Select all

#!/bin/bash
a=norun
[ "$1" == "run" ] && a=
for i in CAS_OS NONCAS_OS; do
echo $i
cd nanoloader
echo "#define $i" > casos.h
cd ndless_loader
make clean
make
cd ..
make clean
make
rm -f casos.h
cd ..
cp nanoloader/loader.bin nanoloader$i.bin.tns
done

And attached is nanomaker, an Ndless tool to build the flashable nanoloader image directly on your calculator.
So for the user, no need to have Cygwin/Linux and use the command line.
And for you, no need to include Boot2/Boot1.5 images anymore.

A tutorial could be based on something like this :

• send nanoloaderCAS_OS.bin.tns or nanoloaderNONCAS_OS.bin.tns to your calculator
• send nanomaker to your calculator
• download Boot2 4.0.3 image and send it to your calculator
• download Boot1.5 4.4 image and send it to your calculator
• open nanomaker on the calculator
• select the payload file (nanoloaderCAS_OS.bin.tns or nanoloaderNONCAS_OS.bin.tns)
  
• select the Boot2 image (4.0.3 is better)
  
• note the generated image name
  
• with BtMg, overwrite the 1st image in your Boot2 partition with Boot1.5 4.4 (unless it's already there)
• with BtMg, overwrite the 2nd image in your Boot2 partition with the generated image

[parrotgeek1]

.

[critor]

Feel free to include the tool source code in your nanoloader github and to modify it as you wish.

Can we aim at a release or not yet ? Just to know if I can start writing a tutorial with captures of the current tools or not.

[parrotgeek1]

.

[critor]

Also, can you make nanomaker explicitly refuse to use a boot2 other than 4.0.3?

I'm not sure it's a good idea.

Some tinkerers might need other Boot2 versions.
Maybe to run and test CM or CX development OSes, after modifying nanoLoader of course.

But even if TI still doesn't know about nano Loader, since TI already knows about nBoot+ControlX using an exploit in Boot2 4.0.3, I wouldn't be surprised if some next hardware revisions became incompatible with Boot2 4.0.3.
So people buying CX calculators in the next months might need a more recent Boot2 image.
Even if it won't be easy to update nanoLoader to auto-install Ndless in this case, it should still be easy to run any OS.

And also, even if we can check the Boot2 image, we can't really check the payload image...