Ndless 1.7 for TI-Nspire

[calcforth]

Thank you for your response, and this will surely resolve the problem, cause I'm with the GCC 4.4x .
I'm looking forward to installing GCC 4.5x on ubuntu 10.04, any sugestions ?

Tough question. You can try to use Debian packages (as recommended in this thread) or compile it yourself. There are bunch of precompiled packages floating around, but I'm not sure which are good and which are not.

[Goplat]

Excellent!

One bug I noticed: After running ndless_tests.tns, the cursor moves too fast. sleep() isn't setting the timer counter reset value back properly (reading 900D0000 gets its current value, not its reset value), so it ends up speeding up the timer interrupt by a random amount.

[Levak]

Well ...
I finaly managed to compile it (thanks to calcforth)
But, I couldn't manage to run asm/C progs which worked perfectly before with Ndless 1.7.
The error is  : "This file cannot be opened nia nia nia".

The instation made double random-pixel lines with the StackOverflow pie-chart instead of the batteries symbol.

The installation worked :
- disconnected
- connected to a USB 3.0 port

The installation failed (freeze clock) :
- connected to a USB 2.0 port

(tested a few times)

[DJ Omnimaga]

It still does, this is another issue currently without solution. Fortunately the faster installation makes this less painful.
(but notice that this is a feature you won't find in any calculator shell. Ndless v1.x got you used to it )

Which feature? Requiring a re-install every reboot? Because for me Ndless 1.0 did not uninstall itself after rebooting.

[ExtendeD]

One issue:  After installing Ndless on the emulator, it will not let me send files to it (it says "Unknown OS Version")

The Initialize vector on which nspire_emu depends should be restored to the OS value, I'll fix this. As a workaround you can use "Connect" before installing Ndless.

sleep() isn't setting the timer counter reset value back properly (reading 900D0000 gets its current value, not its reset value)

Ok, thanks.

But, I couldn't manage to run asm/C progs which worked perfectly before with Ndless 1.7.

So you noticed that:
- The installation fails for you without computer and USB 3.0 is required
- The program loader doesn't work.
I forgot to give the CAS address for ins_lowmem_hook_addrs in install.c, but this is probably not the cause of the problem. I didn't take the time for CAS tests, did you try it on nspire_emu?

It still does, this is another issue currently without solution. Fortunately the faster installation makes this less painful.
(but notice that this is a feature you won't find in any calculator shell. Ndless v1.x got you used to it )

Which feature? Requiring a re-install every reboot? Because for me Ndless 1.0 did not uninstall itself after rebooting.

Yes, I mean this was an uncommon feature which could exceptionally be provided by Ndless 1.0.

[Levak]

But, I couldn't manage to run asm/C progs which worked perfectly before with Ndless 1.7.

So you noticed that:
- The installation fails for you without computer and USB 3.0 is required
- The program loader doesn't work.
I forgot to give the CAS address for ins_lowmem_hook_addrs in install.c, but this is probably not the cause of the problem. I didn't take the time for CAS tests, did you try it on nspire_emu?

Not exactly.
The "complete" procedure works perfectly when the Nspire is disconnected.
On the Other hand, when I've got the Nspire connected to my USB 2.0 port, it simply freezes like before.
But, the USB 3.0 port lets ndless reboot the calc and "install" it-self, just like before.

The bug is partially corrected, the Nspire haven't to be connected if you want to install ndless.

I think the non-asm-openning problem is due to the missing adresses in install.c, it was just the same problem when we didn't get the hook adresses for CAS.

This will surely resolve the problem.

[DJ Omnimaga]

It requires USB 3.0? If someone has an old computer, like my Intel Celeron, which has some USB 2.0 and the original version, does that means they cannot use Ndless?

[Munchor]

It requires USB 3.0? If someone has an old computer, like my Intel Celeron, which has some USB 2.0 and the original version, does that means they cannot use Ndless?

Wha-a-a-a-at?

Hope not!

[Levak]

It requires USB 3.0? If someone has an old computer, like my Intel Celeron, which has some USB 2.0 and the original version, does that means they cannot use Ndless?

... you didn't follow the topic
I made tests on the old beta, and FOR ME, JUST FOR ME BECAUSE NOBODY CONFIRMED, I had to be connected to an high-speed USB port (I showed on a picture).
Some had to hot-plug the TI Nspire while installing Ndless (it didn't work for me, this was an example)

Today, I can manage to installa Ndless DISCONECTED from the computer.
On the other hand, if I want to connect the Nspire to the computer while installing Ndless, I have to connect it to this high-speed USB port, otherwise the install fails.

I repeat it as many time it will be known : nobody has confirmed my tests, those are just suppositions, even if I am sure that FOR ME it works like this.

Anyway, I'm looking forward to updating the install.c and add the hook adresses for CAS and port the results here.

edit for ExtendeD : in install.c

well, I found the CAS address for "lowmem" array

Code: Select All | Copy To Clipboard

1 2 3

// OS-specific // call to the dialog box display warning about low memory unsigned const ins_lowmem_hook_addrs[] = {0x10012F24, 0x10012E6C};

but it hasn't solved the old problem : can't open asm progs after hot-reboot.

edit2: found another in stage2.c

Code: Select All | Copy To Clipboard

1 2 3

// after the inflate loop, we want to simulate a null-return check and quit static unsigned const s2_tizip_hook_addrs[] = {0x1019708C, 0x101990A4};

but it hasn't solved the old problem : can't open asm progs after hot-reboot.

edit3 : in bootstrapper.S

Code: Select All | Copy To Clipboard

1 2 3

bs_stack_unwind_addrs: .long 0x101975FC, 0x10197700 .long 0x10199614, 0x10199718

WIIIIIN !!!!

[bsl]

Dont forget to update syscalls-light_cas-1.7.c and syscalls_cas-1.7.c

fseek cas1.7 should be 0x102a6ffc
vsprintf cas1.7 should be 0x102a49e8

The order of the calls is different in syscalls-light_cas-1.7.c - edit carefully

[calc84maniac]

Does the Nspire OS contain the realloc routine? I'd imagine this could be a very useful routine to have.

[apcalc]

In the IDC files ExtendeD posted a while back, it says that realloc is at 0x102A1248 in the OS 1.7 non CAS and at 0x102A3258 in OS 1.7 CAS.

[DJ Omnimaga]

It requires USB 3.0? If someone has an old computer, like my Intel Celeron, which has some USB 2.0 and the original version, does that means they cannot use Ndless?

... you didn't follow the topic
I made tests on the old beta, and FOR ME, JUST FOR ME BECAUSE NOBODY CONFIRMED, I had to be connected to an high-speed USB port (I showed on a picture).
Some had to hot-plug the TI Nspire while installing Ndless (it didn't work for me, this was an example)

First of all, this topic has 17 page and Omnimaga gets 300+ posts a day. I can't be bothered to read through 17 pages of messages everytime I want to make sure something was not mentionned by a person in particular before.
Secondly, this is a Ndless update. It's obvious that there may be differences and that I could have asked about USB 3.0 because of that.
3: I did not even know USB 3.0 existed. I thought 2.0 was still the standard.
4: You are not allowed to reply to other forum members with that tone on Omnimaga, even less trying to make them sound retarded like you just tried to do above. Consider this as a first warning. I rated down your post because of that.

Quoted from the board rules:

Omnimaga est un site Internet dédié à la programmation de jeux vidéos sur calculatrices graphiques TI, sur PC et la création de musique. En plus des programmes de notre groupe de programmeurs, nous offrons aussi les meilleurs jeux de rôles (RPG) disponibles pour toutes les marques de calculatrices graphiques. Nous avons aussi un salon de discussion IRC (en anglais seulement) pour ceux qui aime le clavardage. Notre but est d'offrir un environnement de discussion amical pour tout programmeur désirant apprendre, offrir ou recevoir de l'aide, montrer leur travail ou simplement discuter. Pour garantir un tel environnement, nous avons écrit une charte que tous les membres du forum et du canal d'Omnimaga doit suivre:

Ce forum de discussion et le salon de clavardage sont disponible pour tout le monde comme privilège. Par contre, soyez informés que les messages publiés par les membres ne représentent pas nécessairement la vision ou l'opinion de la communauté d'Omnimaga et même si nous nous assurons que le forum ne contienne pas de contenu entrant en infraction avec ces règlements, nous ne somme pas parfait et ce contenu peut parfois passer innaperçu. N'hésitez pas à nous signaler les cas d'abus s'il y a lieu. Les comportements et contenus suivants ne sont pas permis sur le forum ni le canal IRC #omnimaga:

1: Messages agressifs, provocateurs (communément appelés "trolls"), insultants et discriminatoires envers une personne ou un groupe de personnes.
2: Commentaires négatifs/agressifs/destructifs injustifié envers le projet d'un membre (comme dénigrer un jeu entier juste pour sa taille de fichier, le nombre de fichiers ou le langage de programmation utilisé même si le jeu est excellent) dans le but de le décourager.

Red: yelling by using ALL-CAPS letters.
Blue: trying to put me down by making me feel stupid

Just because on TI-BANK and United-TI certain people can put down (en français vous dîtes "diminuer" je crois?) members who ask simple questions and miss the answer buried among the previous three hundred messages without worrying if they will feel welcome anymore or not, and that without much consequences, it doesn't mean that they are allowed to do so on Omnimaga. Such behavior can lead to a permanent ban. It is our goal to make sure all members remain friendly to people who have less knowledges on things so those members feel welcome. Thank you for understanding.

Maybe I should disable the forums completly in November, because this seems like the troll months...

Anyway, I don't have OS 1.7 installed right now but could anyone test if he can run into this USB problem?

[Goplat]

I don't think it has anything to do with USB versions. As I understand it, success or failure of Ndless installation is basically pseudorandom and depends on how much free memory you have. So plugging/unplugging USB cables, creating/deleting documents - anything that causes the OS to allocate or free memory, might change it from working to not working or vice versa.

[ExtendeD]

Goplat: Yes, you're probably right.

Levak: Thanks, I forgot this one.

Does the Nspire OS contain the realloc routine? I'd imagine this could be a very useful routine to have.

It does, with many other already identified. Please post a patch for any change you make to common.h and os.h to help me integrate it quickly.