Sorry if it sounded like I was saying that you and Levak were putting new TI-BANK members down, it was an example of if you ever decided to do it you may not have any problems, not necessarly saying you were actually doing it. I should probably have said that differently. I'll edit that part of my post to make sure it won't be taken that way anymore. I was saying TI-BANK and United-TI because I do remember people there doing that. I even intervened in one topic to explain that everyone has to start somewhere. Sorry about that.

I don't think it has anything to do with USB versions.

Actually it kida does. USB 1.x, 2.0 and 3.0 are joined but separate (like oil and water): they have different protocols (if you'll see topology in your device tree list you'll see that USB 1.x devices are connected to UHCI or OHCI hub, USB 2.0 devices to EHCI hub and USB 3.0 devices to xHCI hub), they use different resources, etc. In case of USB 3.0 they even use different wires!

Well, it's nice information to have, but how it's related to our Ndless woes? Well, the answer is simple: since USB 3.0 connector combines three interfaces in one connector it actually takes longer for it to detect the version of USB device is using! And that means that that Ndless have more time to do it's magic before USB hub will start hammering OS with interrrupts (USB 1.x and 2.0 are fully passive - they only generate activity on slave device when hub asks them to do something; USB 3.0 is different but here it's not very relevant because TI-Nspire does not support USB 3.0).

It means that while USB 3.0 per se should not affect Ndless in any way using USB 3.0 connector may help to make the procedure more robust. That's all. Now the only question is: just what is the troubling part of Ndless which makes it impossible to do any work in the presense of the interrupts and can we reduce this "window of vulnerability"? If we can do it then USB 2.0 or may be 1.x connectors should work too.

I have a doubt with ndless. When you install it, what exactly happens? Like, I can't find a video. But can you calculate, use it as normal.

And when you install, when you turn off anything happens?

Please explain me because I'm quite curious

I have a doubt with ndless. When you install it, what exactly happens? Like, I can't find a video. But can you calculate, use it as normal.

And when you install, when you turn off anything happens?

Please explain me because I'm quite curious

You can do what ever you want, either work like before, or run asm progs.
Ndless will "just" by-pass the verification of a valid document and "add" the possibilitie of documents that begin with "PRG"
ExtendeD will surely explain better than me.

Quote from: Levak on November 25, 2010, 02:44:35 pm

You can do what ever you want, either work like before, or run asm progs.
Ndless will "just" by-pass the verification of a valid document and "add" the possibilitie of documents that begin with "PRG"
ExtendeD will surely explain better than me.

Hum. Without ndless I can run Asm progs?

No.

Quote from: Goplat on November 23, 2010, 06:35:29 pm

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

Do I need to hard-code the OS value? I can't see any port to read the reset value.

Yeah, there seems to be no way to retrieve the reset value from the hardware (aside from looping while polling the port to get which value comes after 0). Might be best to hard-code the OS value.

wow, finally. thanks man!!!

btw: do u already know how long it's gonna take until the stable release??