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 ... 19 20 [21] 22 23 ... 137
301
« on: July 17, 2013, 08:53:25 am »
Ok, so we have to make nLaunch work on the TI-Nspire emulator in CX mode with only 32MB SDRAM.
I think this should do.
CX mode 32MB SDRAM: nspire_emu /MX
CX mode 64MB SDRAM: nspire_emu /MX /R
302
« on: July 15, 2013, 04:06:47 pm »
 It wasn't easy to find, but the omitted Casio calculator (at the right of the only HP calculator) is a fx-5800P Super-FX Plus. I've now added it.
303
« on: July 15, 2013, 01:25:43 pm »
Yes, there: http://cncalc.org/Lots of developpers and hackers, for both TI and Casio.
304
« on: July 15, 2013, 01:13:15 pm »
I agree with the point about how the OS uses the available hardware. If it does it's job nicely, (and judging from the thread it does) then why make a problem out of it.
According to the other thread with the 2nd test, it doesn't. http://ourl.ca/19207/354214;topicseen#new
305
« on: July 15, 2013, 12:12:00 pm »
The chinese calculators community cnCalc.org had the honor of being invited by Casio China in its skyscraper in Shanghai. At the corner of a corridor, cnCalc could find the full paper version of the Prizm fx-CG20 color calculator manual, which is not included with the calculator.  But here is the real purpose of the visit, the comparative test of the new ClassPad fx-CP400 color calculator of back to school 2013!  Many reference models were therefore available at Casio China to achieve an accurate comparative test: Texas Instruments calculators: - TI-92
- TI-Nspire CM-C
- TI-Nspire CX
Casio calculators: - fx-5800P
- fx-9750Gii
- fx-9860Gii
- fx-9860Gii SD
- ClassPad 330 Plus
Hewlett Packard calculators: CnCalc welcomes the great attention that was ported to the design of the fx-CP400, and the high quality of its screen. For the drawbacks, we note some criticisms of the minimalist keyboard and the difficulty of entering expressions on the touch screen, but it might be because the touch screen interface needs the user to be used to it. More importantly, cnCalc finds the fx-CP400 performances disappointing . Although more powerful than the ClassPad 300/330, the fx-CP400 is more than 2x slower as the Prizm fx-CG20 for running BASIC programs. As a comparison, the Prizm fx-CG20 would have to be downclocked from 58MHz to 25MHz for similar performances... This is due to the additional cpu-time needed to handle the huge color screen. The fx-CP400 therefore has the same performance problem as the TI-84 Plus C Silver Edition. Crossposted from: http://tiplanet.org/forum/viewtopic.php?t=12677&lang=en
306
« on: July 15, 2013, 11:42:57 am »
In several previous news, we had already announced you the new color touchscreen ClassPad from Casio, the fx-CP400 for back to school 2013. Helder7 from Casiopeia has published what I believe to be the first test of this new calculator he has managed to obtain. Several people made fun about the hardware of this new calculator, assumed to be largely inferior to the one of the TI-Nspire CX and HP-Prime. But we must also consider another factor, whether the OS uses hardware optimally or not. Helder7 seems to have experienced no discomfort with this calculator he qualifies as a serious competitor to the TI-Nspire CX, although he concludes, however, that the latter is better. He's even released you some small programs!  Crossposted from: http://tiplanet.org/forum/viewtopic.php?t=12636&lang=en
307
« on: July 15, 2013, 11:31:23 am »
Triple-posting. I finally got a reply from the Ndless team, which does confirm my main hypothesis. The current nLaunch(y) CX code needs 64MB RAM in order to work. The TI-Nspire CM has only 32MB RAM and this will have to be fixed. The current nLaunch(y) for CX only work with 64mb of RAM.
Some adresses in memory are hard-coded and fall in the over 60 mb of the memory, which does not exists if you only have 32mb. One of these adresses is at the very beginning, before anything gets printed.
308
« on: July 13, 2013, 08:35:21 pm »
And after some simple test,I believe pin 25 in J04 should be RST,so I think if J04 really contain JTAG signals,pinout should be like this:
GND 1 2 GND
Vcc 3 4 Square-wave
High 5 6 Square-wave
High 7 8 Square-wave
TBD 9 10 Square-wave
GND 11 12 Square-wave
GND 13 14 GND
TRST 15 16 TBD
TDI 17 18 GND
TMS 19 20 Square-wave
TCK 21 22 Square-wave
TDO 23 24 RS232 Output (115'200,8,n,1)
RST 25 26 RS232 Input
GND 27 28 GND
GND 29 30 GND
I will test it on next Monday,and of course,I wonder what pin9\pin16 and these strange square wave really are
Could you test and confirm those pins? Just connecting the RST pin to ground doesn't seem to trigger any reset.
309
« on: July 12, 2013, 07:18:25 pm »
What *might* be possible if you can't wait, would be to recompile Nlaunch by including some NAND-fixing code in preloader.c.
You would nead to:
- read the 16 first NAND pages (each page is 2048-bytes) to a buffer (I've never tried to read/erase/write less than 16 pages at a time)
- modify the model ID from 0x10 to 0x12 in the buffer
- erase the 16 first NAND pages
- flash the 16 first NAND pages with the buffer content
Before trying on your calculator, check that such code works on the emulator in CX mode with CX Boot2 3.1.
Make the program as simple as possible in order to use as few syscalls as possible, as every syscall will have to be (re)defined with CX Boot2 3.1 addresses.
You'll need to find read_NAND, nand_erase_range and write_NAND syscalls addresses in the Boot2.
310
« on: July 12, 2013, 05:11:57 am »
Ok. I hope someone will have the time to dig into Nlaunch code.
But unfortunately, we're in the middle of the summer, and I got no reply from the Ndless team for now.
You might have to way a little, but please don't throw away your calculator.
There is no reason Nlaunch won't work on the TI-Nspire CM someday.
311
« on: July 11, 2013, 08:51:53 am »
Ok, let's focus on what happens on the 1st reboot after sending Nlaunch.tco.
The Boot2 is supposed to start at 60%.
You're getting a freeze without any error message or anything printed in the top left-hand corner of the screen? Please confirm this. It would mean the Boot2 tries to launch Nlaunch, but crash for some reason.
If you press the reset button again, what do you get? The same thing?
Just a little idea: could you retry to install Nlaunch after using the maintenance menu to reformat your filesystem?
On TI-Nspire CX, filesystem starts at NAND page 0x800, but on TI-Nspire CM it does start at NAND page 0x7C0.
312
« on: July 10, 2013, 07:26:25 pm »
Ok, Y+Z+reset seems perfectly normal:
firstloader_cx.c:
void main(void) {
const char *preloader_path = "/documents/nlaunch/preloader.tns";
display_msg_to_screen(u"Y",0,0);
*(volatile unsigned*)0x90060C00 = 0x1ACCE551;
*(volatile unsigned*)0x90060008 = 0;
*(volatile unsigned*)0x90060C00 = 0;
mkdir("/phoenix/install/");
rename(preloader_path, (char *)0x118D9DA4);
display_msg_to_screen(u"Z",0,0);
boot2_HW_reset();
__builtin_unreachable();
}
What is not normal, is Nlaunch not being started upon reboot by the CX Boot2 3.1 on the CM hardware.
313
« on: July 10, 2013, 08:11:55 am »
Do you have the time to see if some characters are outputted to the top left-hand corner of the screen before the reboot when sending nlaunch.tco ?
314
« on: July 10, 2013, 07:25:37 am »
If it was so easy to inject code and use Boot2 3.1 syscalls, we wouldn't have waited for Nlaunch CX.
Solving this critic problem means making Nlaunch (or a similar tool) work with the CX Boot2 on your CM hardware.
And we should first try to determine where it does crash and why.
The TI-Nspire CM hardware has only 32MB RAM instead of 64MB on a real TI-Nspire CX.
This might have some issues with overflow exploits for example...
To help us determining where Nlaunch does crash you might try to modify its source code by adding some ouputs to the top left-hand corner of the screen or to RS232.
315
« on: July 10, 2013, 06:03:10 am »
In this first post, I'll try to explain comprehensively what I understand of this critic problem for other readers. Correct me if I'm wrong. nsNandMgr doesn't work on the latest TI-Nspire emulator release in CM mode, although it works like a charm in classic or CX mode. So unfortunately, we have no way to simulate exactly what you did - so it's important to be very accurate.nsNandMgr does forbid some hazardous/untested things, yes. So if I understand well, correct me if I'm wrong, you (guys) did modify the source in order to bypass those securities. You did then: - use nsNandMgr to change the model ID in NAND-Manuf from 0x12 (TI-Nspire CM) to 0x10 (TI-Nspire CX)
- use RS232 to flash CX Boot2 3.1.0.16
Question: how did you use RS232 on a model which has no Dock/J01 connector? Did you use the internal J04 connector? Note: you could have flashed the Boot2 from nsNandMgr, before or after modifying the NAND ID. So now, you have: - a TI-Nspire CM hardware
- model ID 0x10 (TI-Nspire CX) in NAND-Manuf
- the common TI-Nspire CX/CM Boot1 3.0.0.99
- the TI-Nspire CX Boot2 3.1.0.16
- User Flags 0b00010 (TI-Nspire CM) in ASIC
In that condition, it's normal for your calculator: - to reject CAS and CM OSes with an "Invalid program ID" error because of the NAND-manuf model ID
- to reject CX OSes with a "Missing ASIC user flags" error because of the ASIC User Flags
Yes, your calculator is in a condition where it won't accept any 'normal' OS anymore. Such calculators are usually referred as 'bricked' calculators. Changing the 80E0 field in an OS file to match the ASIC user flags can't work because this field data belongs to the signed data.
Pages: 1 ... 19 20 [21] 22 23 ... 137
|
Show Posts
