Forum TI-Planet.org

c'est peut-être le Boot2 sur extended avant l'image Linux

pberthou a écrit:Tu vois quelque chose de mal placé? http://a360.co/2tm7cwR

Oui, ControlX n'est pas en 1ère position dans la partition Diags :


Rouvre le fichier "controlx.img" si toujours présent sur ta calculatrice.
Cela devrait ouvrir automatiqument BtMg.
Tu vas alors dans pour la partition Diags, puis pour flasher.
Et cette fois-ci tu mets ControlX tout en haut de la partition Diags, soit avant ton image de Diags 3.91.37 (ne l'écrase pas, elle peut servir de temps à autres).

ça marche nickel

Sinon il y à d'autres restrictions pour les distrib Linux à part la taille?

Je ne sais pas trop - il faut attendre qu'une personne compétente en Linux-Nspire réponde.

Sinon, il y a une limitation sur la taille des partitions. Il faut éviter de faire une partition ExtendeD de plus de 13-14Mio il me semble, car sinon les outils de reflashing peuvent avoir des problème de mémoire.

C'est sûrement améliorable, mais comme il n'existe pour le moment à ma connaissancce pas de 'bonne' image Linux de plus de 6Mio, et que les autes images de Boot2/Diags/ControlX font bien moins que ça, la priorité est faible.

Et est-ce qu'il existe un dépôt/liste d'images déjà testé et fonctionnelles

Le dépôt le plus proche de ce que tu demandes est celui-ci :
https://tiplanet.org/nspire_linux_builds/

Avec des builds remontant hélas à plusieurs années.

C'est exceptionnel que quelqu'un n'ait pas rien à faire de la cible Nspire de Linux
Au moins, le code d'un niveau de qualité production a été mis dans le kernel mainline, donc même si personne ne s'en occupe depuis un moment, un build du kernel mainline pour Nspire devrait assez bien fonctionner.

Le filesystem propriétaire (en deux parties, FlashFX + Datalight Reliance) utilisé par les Nspire n'est pas géré en écriture, et je ne sais même plus s'il l'est en lecture dans les builds normaux.

Lionel Debroux a écrit:Le filesystem propriétaire (en deux parties, FlashFX + Datalight Reliance) utilisé par les Nspire n'est pas géré en écriture, et je ne sais même plus s'il l'est en lecture dans les builds normaux.

nope, you can't read it either. The NAND driver (which never got to mainline) is only for CX, is read-only (but you can change that), has hardcoded partitions (rather than using the values from Manuf), and has broken ECC support.

Hello everybody, I am new here speaking, but I've been working with all the information you (Ti-Planet, Omnimaga, ndlessly, basically the Nspire community) gave me since 2012. I have my Nspire CX since early 2012, it's a revision C. I've been following all the updates on the calc you guys gave me since ndless 3.1, but I abandoned it when OS 4.0 came out. Now all of a sudden tools to partition the nspire appear and boot1 exploits appear, I am impressed

This is my story, I flashed nboot, controlx in my diags partition, and boot2 4.0.3 in my extended partition (I still have boot2 3.1 in my main boot2 partition, and it didn't ruined everything). Everything worked fine, but last night I got a bit drunk and used an old version of nsNandMgr and flashed diags partition (don't ask why, I also don't know). Conclusion, it wiped controlx, and my extended partition (by the way, I keep controlx alone in diags partition, and in extended partition I keep both boot2 4.0.3 and my diags dump). After I pressed reset, I was greeted with the old nspire B/W bootscreen, and it would load to half of it and then reboot. Tried to boot to maintenance mode ( + + ) Didn't work... Diags ( + + ) didn't work either. So I had a brick... But wait

How I fixed it:

The only way to fix it would be trying to understand what was happening. I had my nspire TTL interface "Harness", which is basically 3 old male to male breadboard wires, with one end stripped, on a very small pencil that is the exact size of the dock connector. But I had borrowed my FTDI adapter to a friend that is working with Arduino pro mini. But I had my arduino Mega around, which did the same work.

So from hyperterminal, I concluded it was loading boot2 3.1 completely but after that it would reboot. So boot2 was "fine". I took a chance and flashed a diags image to diags partition by pressing the key combo, I knew it would wipe that partition, but worse than it was it couldn't be... I flashed my diags dump image (I keep everything in my laptop just because...) And it would boot in a white screen and reboot immediately, so nothing done either... and I took my battery out for 10 secs, so that I could at least see the screen

Then, while thinking in another way to repair it, my friend says "send it to the factory", I said "I don't even have the stock manuf.img in it, they won't repair" and then the switch flicked... nBoot was still installed!

I opened hyperterminal, inserted diags flash keycombo ( + + ), it said it wipped my diags image, and flashed ControlX.img in diags partition (taking the risk). And since I knew after flashing a new diags, it would change bootD boot mode to diags first, I wasn't worried. I pressed and after it rebooted, it worked! It was in ControlX. I just pressed Z to uninstall nBoot, installed OS 3.1 and ndless, and flashed everything back to normal, even my stock manuf.img

Conclusion: always keep a backup of every nspire partition, and I am not sure that after last night trauma, I will reinstall controlX and nboot that soon

Don't drink and nspire, kids

Sorry for long text, but nothing would be possible if I didn't learn with all of you guys. I never created an account, but I needed to share my story with you guys.