C1000 Nand Woes (maybe)...

[ArKay]

OK, It looks like I may have messed something up and am I hoping someone can help me out here.


I went into the D+M menu to check for bad NAND blocks - after the test was done I went back to the menu page (using the cancel key to get there) and powered the unit off.

Now it will only power on to the D+M menu. Won't power on normally. Won't power on with the 'On' button held to try to reflash the ROM

Making a leap that somewhere stumbling through the menus I may have erased the NAND (although I didn't think I did) I went and downloaded NAND backups and restores.

I can't get any of them to work.

Trying the NAND update I get :

CF Update
---Found Orders ---
Error !!!

Using the NAND Backup Restore instructions from Trisoft (and the files) and putting them in Backup_Files folder on the CF card I simply get :

NAND Restore from CF

file : SYSTC100.DBK
not exist file

Anyone have an idea it won't work ?
Am I missing a step beyond having the file eith on the root of the CF card (or in the Backup_Files directory), powering on to the D+M menu and going to the correct menu choice and letting it rip ?

Is this simply a signal that the files aren't viable ?

Anyone have a NAND backup or full backup for a C1000 they would be willing to email me ?

Thanks in advance for any help that might get my C1000 back and running.

[InSearchOf]

Seems like your CF card isnt recognized.... is it formated fat16?

Late

[tml]

Now it will only power on to the D+M menu.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167204\"][{POST_SNAPBACK}][/a][/div]

You either have to exit the menu or reset or something like that. Can't remember precisely.

Using the NAND Backup Restore instructions from Trisoft (and the files) and putting them in Backup_Files folder on the CF card I simply get :
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167204\"][{POST_SNAPBACK}][/a][/div]

For NAND restore, format your CF card as fat (not fat32) and put the SYSTC100.DBK in the root directory. The backup folder is for system backups.

And remember: Don't panic.

[Capn_Fish]

Taking out the battery and putting it back in or hitting the reset switch should allow you to get out of the D+M menu.

If you had erased your flash, you wouldn't be able to get to the D+M menu in the first place/get back to it. You'd have to use the Fn+D+M menu, so that's not an issue.

[ArKay]

Taking out the battery and putting it back in or hitting the reset switch should allow you to get out of the D+M menu.

Oh, I can get in and out of the D+M menu... but that's it. Hitting the reset switch gets it 'out' of the D+M menu - and seems to turn it off. Hitting the power button turns it off... and hitting it again causes it to power on to the D+M menu.

If you had erased your flash, you wouldn't be able to get to the D+M menu in the first place/get back to it. You'd have to use the Fn+D+M menu, so that's not an issue.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167210\"][{POST_SNAPBACK}][/a][/div]

Good to know. But the fact that the _only_ thing it will boot to is the D+M menu (not the reflashing menu or the regular boot up sequence) has me concerned.
Removing the battery, hitting the reset button, just plugging in the AC adapter with no battery, with a battery, etc. causes nothing to happen. No charge light, no booting, no menus other than the D+M menu can be gotten to.  

Any ideas ? Anybody ?

[adf]

the recommendation for people with similar issues derived from u-boot is ctl-D-M, as far as I've seen here.
Look around at the pdaxrom threads on this topic, or even search in the pdaxrom forums using uboot and flash as your terms.  see what is said. ymmv, of course.

[Meanie]

Taking out the battery and putting it back in or hitting the reset switch should allow you to get out of the D+M menu.

Oh, I can get in and out of the D+M menu... but that's it. Hitting the reset switch gets it 'out' of the D+M menu - and seems to turn it off. Hitting the power button turns it off... and hitting it again causes it to power on to the D+M menu.

If you had erased your flash, you wouldn't be able to get to the D+M menu in the first place/get back to it. You'd have to use the Fn+D+M menu, so that's not an issue.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167210\"][{POST_SNAPBACK}][/a][/div]

Good to know. But the fact that the _only_ thing it will boot to is the D+M menu (not the reflashing menu or the regular boot up sequence) has me concerned.
Removing the battery, hitting the reset button, just plugging in the AC adapter with no battery, with a battery, etc. causes nothing to happen. No charge light, no booting, no menus other than the D+M menu can be gotten to.  

Any ideas ? Anybody ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167227\"][{POST_SNAPBACK}][/a][/div]

There is a flag in the DM menu that says something like Diagnostic Mode on (y/n) and it needs to be set to N. It probably has been changed to Y...

[ArKay]

There is a flag in the DM menu that says something like Diagnostic Mode on (y/n) and it needs to be set to N. It probably has been changed to Y...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167236\"][{POST_SNAPBACK}][/a][/div]

Found the flag you are talking about - it's in the Extras menu and lists 'clear diag flag' and 'normal diag mode' for options. Bootflg : ---- is the current setting. With the Bootflg on Diag it will only boot to the diag mode.

With it set to ---- (or cleared as the case may be) it won't boot normally, won't boot to the reflashing menu - but it will boot to the D+M menu. I realize I said this in a somewhat confusing manner so I'll say it differently. Just hitting the power button does _not_ cause it to boot into the D+M menu (with the flag cleared)... it does nothing. As does the reset button/hold down the 'OK' button and trying to add power version of getting to the reflashing menu. The only method that will get life out of the little guy is holding down D+M as power is applied via AC Adapter. That's it. Not that it boots there regardless of what I try.

I hope that explains it better. Thanks for the hint though - it just isn't the case here.