This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - critor
Pages: 1 ... 98 99 [100] 101 102 ... 137
1486
« on: March 17, 2011, 03:24:08 pm »
I managed to get the old 1.1.7xxx boot log through RS232.
Boot Loader Stage 1 (1.1.7314)
Build: 2007/2/23, 20:43:36
Copyright (c) 2006, 2007 Texas Instruments Incorporated
Using developer keys
Last boot progress: 17816
Clocks: CPU = 90MHz AHB = 45MHz APB = 22MHz
Available system memory: 37292
PM is turning the device OFF
PM has turned the device ON
SDRAM memory test: Pass
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Checking for NAND: NAND Flash ID: ST Micro NAND256R3A
Boot option: Normal
Loading DIAGS software...
Error reading/validating DIAGS image
Error loading DIAGS. Switching to BOOT2.
Loading BOOT2 software...
99%
BOOT1: loading complete (339 ticks), launching image.
Boot Loader Stage 2 (1.1.7314)
Build: 2007/2/23, 20:48:12
Copyright (c) 2006, 2007 Texas Instruments Incorporated
Using developer keys
Clocks: CPU = 90MHz AHB = 45MHz APB = 22MHz
Initializing graphics subsystem.
Checking for NAND: NAND Flash ID: ST Micro NAND256R3A
Boot option: Normal
Initializing filesystem.
Datalight Reliance v2.10.1150
Copyright (c) 2003-2006 Datalight, Inc.
Datalight FlashFX Pro v3.00 Build 1358
Nucleus Edition for ARM9
Copyright (c) 1993-2006 Datalight, Inc.
Patents: US#5860082, US#6260156.
Filesystem ready.
Loading Operating System...
100%
ðxâ À~ÃÏàzó=~ÃCÀžOæâž'˜óñž?OhÌšžOx3Ï~h4€LÀ
Beginning system initialization.
Preparing file system. This takes a while...
POSIX layer initialized.
POSIX devices initialized.
Datalight Reliance v2.10.1150
Copyright (c) 2003-2006 Datalight, Inc.
Datalight FlashFX Pro v3.00 Build 1358
Nucleus Edition for ARM9
Copyright (c) 1993-2006 Datalight, Inc.
Patents: US#5860082, US#6260156.
POSIX file system initialized.
File system ready.
* P3 mode battery door detection
System build date: Feb 26 2007, 10:28:12
Available memory: 25556776 bytes
Purging temporary files...
Launching system...
1487
« on: March 17, 2011, 03:20:08 pm »
Don't worry Goplat: I have something like 10 TI-Nspire CAS+ with either OS 1.0.554 either OS 1.0.526.
I can brick some of them by trying to flash a Boot2, an OS, or a diags through RS232.
(but I'm pretty sure a newer production OS won't work without flashing a newer production Boot2, as the OS is not located at the same place in the filesystem).
1488
« on: March 17, 2011, 02:58:43 pm »
After being silent for more than 4 years as if they were under NDA, less than a hour ago a TI-Nspire CAS+ "talked" for the 1st time in the World! Boot Loader Stage 1 (1.0.526)
Build: 2006/8/11, 6:25:18
Copyright (c) 2006 Texas Instruments Incorporated
Using production keys
Last boot progress: 10514
System clock: 78 MHZ
SDRAM memory test: Pass
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Checking for NAND: NAND Flash ID: ST Micro NAND256W3A
-- Bad Block list --
0x00058000 (22)
0x001F0000 (124)
-- Bad Block list end --
Loading DIAGS software...
Error reading/validating DIAGS image
Loading BOOT2 software...
99%
BOOT1: loading complete (924 ticks), launching image.
Boot Loader Stage 2 (1.0.526)
Build: 2006/8/11, 6:29:51
Copyright (c) 2006 Texas Instruments Incorporated
Using production keys
Initializing graphics subsystem.
Checking for NAND: NAND Flash ID: ST Micro NAND256W3A
Initializing USB and networking.
Initializing filesystem.
Datalight Reliance v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Registered to #9DE08703
FlashFX sample project for the OMAP5912 OSK running Nucleus
Datalight FlashFX Pro v2.0 Build 966
Nucleus Edition for ARM9
Copyright (c) 1993-2005 Datalight, Inc.
Patents: US#5860082, US#6260156.
Detected FfxDelay() parameters: Count=60132 MicroSec=8192 Shift=13
FFX: NAND chip manufacturer: ST Micro (20) chip NAND256W3A (75)
Filesystem ready.
-- Bad Block list --
0x00058000 (22)
0x001F0000 (124)
-- Bad Block list end --
Loading Operating System...
100%
BOOT2: loading complete (3272 ticks), launching image.
Beginning system initialization.
Preparing file system...
Datalight Reliance v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Registered to #9DE08703
FlashFX sample project for the OMAP5912 OSK running Nucleus
Datalight FlashFX Pro v2.0 Build 966
Nucleus Edition for ARM9
Copyright (c) 1993-2005 Datalight, Inc.
Patents: US#5860082, US#6260156.
Detected FfxDelay() parameters: Count=58930 MicroSec=8192 Shift=13
FFX: NAND chip manufacturer: ST Micro (20) chip NAND256W3A (75)
File system ready.
phoenix dhcp server w/ VOODOO built 12-Jul-2006 (start at 545)
phoenix enum server built 12-Jul-2006
phoenix dhcp hook fwd w/ VOODOO built 12-Jul-2006 (start at 545)
System build date: Aug 28 2006, 18:55:11
Available memory: 25803332 bytes
Launching system...
phoenix file mgt server built 12-Jul-2006 (start at 645)
pn-srv2-636: pol_init = 0Notice it is not using the "developer keys", but the "production keys"...  If you need a picture for a news, you can take this. Next step: flashing a production TI-Nspire CAS boot2.
1489
« on: March 17, 2011, 08:45:33 am »
I'm pretty sure it will be exactly like the TI-83+.fr: the standard OS (english) coming with the "Français" application preinstalled.
Just remove this application, and you get a standard TI-83+.
I don't see the point for TI to develop (and then update) a different z80 OS.
1490
« on: March 16, 2011, 04:15:32 pm »
The old Nspire CAS+ prototype OS 1.0 can't open documents created by more recent production TI-Nspire OSes.
The TI-Nspire CAS+ prototype OS 1.0 can't exchange data through USB with production TI-Nspire.
And nobody has been able up to now to update the TI-Nspire CAS+ prototype OS 1.0...
If it's a money problem, you can find TI-Nspire CAS ClickPads allmost as cheap as TI-Nspire CAS+.
You'll be able to do much more on them...
1491
« on: March 16, 2011, 02:09:24 pm »
Ok, he used a scanner. But strangely, the photo in the 1st post was a "photo" and seemed to show the same problem... Or maybe it's another silly protection from TI?  There were frightened Casio could copy their screen, so there's a feature that makes it unreadable on scanned pictures and photos! :P
1492
« on: March 16, 2011, 01:18:47 pm »
2 more Nspire CX photos with a better angle seem to confirm the screen problem: http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/forum.cgi?read=180206Strangely, the Casio Prizm screen looks much better in all available photos and videos with various angles... So let's sum up things: The TI-Nspire ClickPad screen was just scrap... The TI-Nspire TouchPad screen is just scrap... The TI-Nspire CX screen will still be scrap... It may be important to make another news about this now that we have good photos... if there's still someone being able to do it here. (I'm very sad about what's happening to the best english-speaking TI calculators forum...)
1493
« on: March 16, 2011, 10:22:49 am »
The screen shift issue is actually caused by reads and writes from the screen i/o. A memcpy-ied screen buffer should be used for the reads. Could you check if there is anything like this in your code?
mViewer is using its own 16-bits screen buffer. mViewer's viewer is using 2 buffers. The screen is refreshed by switching the buffers addresses. But mViewer's browser is reading/writing directly on a single buffer... And debug messages too...
1494
« on: March 14, 2011, 10:04:54 pm »
That's small. The LCD is the same size, anyway, AFAICT.
Pretty interesting, but if the only change is the size, it doesn't seem terribly worth it to me  (not to mention it probably only has 48KiB RAM).
I probably won't be able to answer you about the RAM before june. By the way, you've got an HD image here: http://ti.bank.free.fr/index.php?mod=news&ac=commentaires&id=1003(just click on the link below the image)
1496
« on: March 14, 2011, 05:36:03 pm »
Yes, with a slightly smaller case, made possible mostly by the new arrow keys. TI is even less imaginative than what you were thinking!
1499
« on: March 11, 2011, 05:34:06 am »
Thanks for that great test, DJ. How many Mb large is your image? I don't think providing a Ndless 1.7 build is really useful. Ndless 2.0 is forward compatible and quite stable now.
My Ndless 2.0 build doesn't work with Ndless 1.7. There are still some very minor bugs with Ndless 2.0. Your work on this is great, don't misunderstand. But some of those rare and minor bugs, might become quite annoying during an exam. I got: - problems with the screen offset, making it sometimes partially unreadable (rare) - reboots (rare) The 1st one is not present with Ndless 1.7 to my knowledge. So I think it's important for some months to let ClickPad users choose between both Ndless versions.
1500
« on: March 10, 2011, 08:25:40 pm »
mViewer 3.0 has just been uploaded on TI-Bank. The archive includes 2 builds: - one for Ndless 1.7 and compatible (Ndless 1.3/1.4) - one for Ndless 2.0 Of course, the Ndless 1.7 build doesn't include any TouchPad code. All Ndless 2.0 specific instructions are commented out by macros, and when possible replaced by Ndless 1.7 compatible code. http://ti.bank.free.fr/index.php?mod=archives&ac=voir&id=2014Please test and report any problem. Thank you very much.
Pages: 1 ... 98 99 [100] 101 102 ... 137
|
Show Posts
