0 Members and 1 Guest are viewing this topic.
Warning at PC=100BC918: Bad read_word: fffbc410
I suspect it's more code left over from the CAS+, trying to access now-nonexistent peripherals.
Do you think such code code be usefull in our attempts to dump/flash the CAS+?
Error at PC=0000A624: NAND flash: read nonexistent page 7fffff Backtrace:Frame PrvFrame Self Return StartA400A568: A400A588 A400A56C 0000A75C 0000A5E0A400A588: A400A7D8 A400A58C 0000AF38 0000A71CA400A7D8: A400AA18 A400A7DC 0000D348 0000AEECA400AA18: A400AA90 A400AA1C 00000DD4 0000D304A400AA90: A400AAA8 A400AA94 00004578 000009C8A400AAA8: A400AAAC A400AAAC 00000000 00004550debug>
IMAGE: verifying file "/tmp/TI-Nspire.tnc"Error at PC=1184DB24: NAND flash: read nonexistent page 7fffff Backtrace:Frame PrvFrame Self Return Start11A2F3A0: 11A2F3C0 11A2F3A4 1184DC5C 1184DAE011A2F3C0: 11A2F610 11A2F3C4 1184E438 1184DC1C11A2F610: 11A2F850 11A2F614 1197AE80 1184E3EC11A2F850: 11A2F8F0 11A2F854 1197F9D8 1197AE3C11A2F8F0: 11A31BB8 11A2F8F4 1197F520 1197F9C411A31BB8: 11A324A0 11A31BBC 118011C4 1197E9D811A324A0: 11A324E8 11A324A4 1188BD30 118008A011A324E8: 11A32500 11A324EC 1182FCF4 1188BC9411A32500: 11A32504 11A32504 00000000 1182FCCCdebug>
Waiting for OS download.Starting Connectivity services.Initializing USB subsystem...Warning at PC=11877D28: Bad write_byte: e59ff018 00debug> cWarning at PC=11877D28: Bad write_byte: e59ff019 80debug> cWarning at PC=11877D28: Bad write_half: e59ff028 0040debug> cWarning at PC=11877D28: Bad write_byte: e59ff01a 00debug> cWarning at PC=11877D28: Bad write_word: e59ff02c 00000000debug> cWarning at PC=11877D28: Bad write_byte: e59ff030 00debug> cWarning at PC=1187A39C: Bad read_byte: e59ff018debug> cWarning at PC=1187A39C: Bad read_byte: e59ff019debug> cWarning at PC=1187A39C: Bad read_word: e59ff030debug> cWarning at PC=1187A39C: Bad read_byte: e59ff019debug> cWarning at PC=1187A400: Bad read_byte: e59ff018debug> cWarning at PC=1187A400: Bad read_word: e59ff088debug> cWarning at PC=1187A430: Bad read_word: e59ff090debug> cWarning at PC=1187A448: Bad read_byte: e59ff01adebug> cWarning at PC=1187A4C0: Bad read_byte: e59ff01adebug> cWarning at PC=1187A504: Bad read_half: e59ff028debug> cWarning at PC=1187A504: Bad read_byte: e59ff018debug> cWarning at PC=1187A504: Bad read_byte: e59ff018debug> cWarning at PC=1187A504: Bad read_byte: e59ff01adebug> cWarning at PC=1187A504: Bad read_byte: e59ff019debug> cWarning at PC=1187A588: Bad read_byte: e59ff019debug> cWarning at PC=1187A5B4: Bad read_word: e59ff098debug>
1199a7f4: /tmp/manifest_img1199a80c: /tmp/TI-Nspire.tnc
This is looking more CAS+ like:Code: [Select]1199a7f4: /tmp/manifest_img1199a80c: /tmp/TI-Nspire.tnc
Then, why is this boot2 so big?Unoptimized code?
00002edc: e1a0c00d mov r12,sp00002ee0: e92dd800 stmdb sp!,{r11-r12,lr-pc}00002ee4: e24cb004 sub r11,r12,0000000400002ee8: e24dd008 sub sp,sp,0000000800002eec: e50b0010 str r0,[r11 - 010]00002ef0: e50b1014 str r1,[r11 - 014]00002ef4: e51b3010 ldr r3,[r11 - 010]00002ef8: e5933000 ldr r3,[r3]00002efc: e3530000 cmp r3,0000000000002f00: 0a000011 beq 00002f4c00002f04: e51b2014 ldr r2,[r11 - 014]00002f08: e51b3010 ldr r3,[r11 - 010]00002f0c: e5933000 ldr r3,[r3]00002f10: e5933000 ldr r3,[r3]00002f14: e5823000 str r3,[r2]00002f18: e51b3014 ldr r3,[r11 - 014]00002f1c: e5932000 ldr r2,[r3]00002f20: e51b3014 ldr r3,[r11 - 014]00002f24: e5823004 str r3,[r2 + 004]00002f28: e51b2014 ldr r2,[r11 - 014]00002f2c: e51b3010 ldr r3,[r11 - 010]00002f30: e5933000 ldr r3,[r3]00002f34: e5823004 str r3,[r2 + 004]00002f38: e51b3014 ldr r3,[r11 - 014]00002f3c: e5932004 ldr r2,[r3 + 004]00002f40: e51b3014 ldr r3,[r11 - 014]00002f44: e5823000 str r3,[r2]00002f48: ea000008 b 00002f7000002f4c: e51b2010 ldr r2,[r11 - 010]00002f50: e51b3014 ldr r3,[r11 - 014]00002f54: e5823000 str r3,[r2]00002f58: e51b2014 ldr r2,[r11 - 014]00002f5c: e51b3014 ldr r3,[r11 - 014]00002f60: e5823000 str r3,[r2]00002f64: e51b2014 ldr r2,[r11 - 014]00002f68: e51b3014 ldr r3,[r11 - 014]00002f6c: e5823004 str r3,[r2 + 004]00002f70: e24bd00c sub sp,r11,0000000c00002f74: e89da800 ldmia sp,{r11,sp,pc}
000029c4: e5903000 ldr r3,[r0]000029c8: e3530000 cmp r3,00000000000029cc: 15933000 ldrne r3,[r3]000029d0: 05801000 streq r1,[r0]000029d4: 15831004 strne r1,[r3 + 004]000029d8: 15813000 strne r3,[r1]000029dc: 15902000 ldrne r2,[r0]000029e0: 05811004 streq r1,[r1 + 004]000029e4: 15821000 strne r1,[r2]000029e8: 15812004 strne r2,[r1 + 004]000029ec: 05811000 streq r1,[r1]000029f0: e12fff1e bx lr
Oh thank you for checking so fast By the way, what do you think about that "page 7fffff" error?
Quote from: critor on April 01, 2011, 07:39:13 pmOh thank you for checking so fast By the way, what do you think about that "page 7fffff" error?It's a bug in TI's code for reading the "bootdata". If it can't find it, it tries to read from offset FFFFFFFF, because they didn't do the error checking quite right. This was fixed in later versions.Presumably the effect on real hardware would be that either the read fails, or it reads the last actual page of flash. Either way, the code won't get a valid bootdata structure, so the end result is it just uses the default.
Does this mean the "downgrade protection" (included in bootdata) won't work on this model if I don't update the boot2 ?