reboot error: bad data at sector / Fehler bei reboot

      reboot error: bad data at sector / Fehler bei reboot

      Edit: translated to English / changed title too

      Hi, I have some troubles during reboot.
      If the NetDCU6 boots normal from power off (coldboot) everything is fine. But when I do a reboot with "reboot hardware" in netdcucfg, then the systems hangs during the boot. To fix this I have to disconnect the NetDCU6 from power and do a fresh start, then it will boot fine again.

      Hallo, habe da ein Problem beim rebooten:
      wenn ich die NetDCU6 normal boote (Kaltstart), dann bootet diese ohne Probleme und funktioniert ganz normal.
      Führe ich allerdings später im netdcucfg "reboot hardware" aus, dann bleibt diese während dem booten stecken, nur ein erneutes ein und ausschalten lässt die NetDCU6 wieder erfolgreich booten.


      Following shows the error case with Kernel V1.33 directly after "reboot hardware":
      Dieser Fehler ist bei jedem "reboot hardware" nachzuvollziehen, im Bootlog mit Kernel V1.33 tauchen während dem Reboot unter anderen folgende Meldungen auf:

      Brainfuck Source Code

      1. ...
      2. NDCUCFG V: 021 started. Platform: NetDCU6
      3. Rebooting .<-66>.
      4. Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built Jun 13 2005 12:21:50
      5. Size of SDRAM memory: 32 MB
      6. Windows CE Bootloader for AMD Alchemy Built May 16 2007 at 12:35:08
      7. Portions copyright (c) 2004 F&S Elektronik Systeme GmbH
      8. Boot Loader, Version 1.12
      9. CPU running at 396000000 Hz
      10. Size of SDRAM memory: 32 MB
      11. BOOT FLASH: SST DEVCODE: 39VF040
      12. T: InitFlash ... Complete!
      13. FindRegistryValue: using registry 1
      14. System ready!
      15. Preparing for download...
      16. Press >S< to step into monitor...
      17. AUTO BOOT enabled
      18. Checking to see if a Windows CE image has been previously flashed...done
      19. Copying kernel from Flash to 0xA1300000, size 7179064, sectors 14022
      20. Kernel read from flash disk started ..........ERROR: d line 137: FMD: bad data at sector 17. No corrections are done.
      21. .ERROR: d line 137: FMD: bad data at sector 21. No corrections are done.
      22. ..ERROR: d line 137: FMD: bad data at sector 2. No corrections are done.
      23. .ERROR: d line 137: FMD: bad data at sector 4. No corrections are done.
      24. .ERROR: d line 137: FMD: bad data at sector 14. No corrections are done.
      25. ...
      26. //<------------------------------------------- I shortened the log here by taking out more "bad data at sector" errors
      27. //<------------------------------------------- Hier folgen noch einige "bad data at sector" Fehlermeldungen
      28. ...
      29. .. finished in 4246 milliseconds
      30. Kernel decompression started ...................................................... finished in 526 milliseconds
      31. Found pTOC signature.
      32. Launching image at 80004004h...
      33. OEMCheckSignature: start= 0x0, offset= 0x0, launch= 0x0, downloaded= 0x0
      34. ---------------------------------
      35. ROMHDR Info (pTOC = 0x80A7C540)
      36. ---------------------------------
      37. dllfirst = 0x01DD01E8, dlllast = 0x02000000
      38. physfirst = 0x80004000, physlast = 0x80A7DCC8
      39. nummods = 0x00000086
      40. ulRAMStart = 0x80A7E000, ulRAMFree = 0x80AA6000, ulRAMEnd = 0x81DD4000
      41. ulCopyEntries = 0x00000001, ulCopyOffset = 0x802B9FE4
      42. ulProfileLen = 0x00000000, ulProfileOffset = 0x00000000
      43. numfiles = 0x0000003B
      44. ulKernelFlags = 0x00000000, ulFSRamPercent = 0x80808080
      45. ulDrivglobStart = 0x00000000, ulDrivglobLen = 0x00000000
      46. usCPUType = 0x0166, usMiscFlags = 0x0000
      47. pExtensions = 0x80005F28
      48. ulTrackingStart = 0x00000000, ulTrackingLen = 0x00000000
      49. --------------------------------
      50. OEMLaunch: Start 0x00000000 Length 0x00000000 Launch 0x00000000 Header 00000000
      51. Jumping to image at 0x80004004...
      52. //<------------------------------------------- At this line the system hangs
      53. //<------------------------------------------- An dieser Stelle wird nicht mehr weiter gebootet.

      Following the case on a normal (cold) boot when the device is turned on, as you can see there is no error, the sysytem boots, everything is fine:
      Bei einem normalen Kaltstart ist von diesen Meldungen nichts zu sehen und es geht ganz normal wie folgender Log zeigt:

      Brainfuck Source Code

      1. Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built Jun 13 2005 12:21:50
      2. Size of SDRAM memory: 32 MB
      3. Windows CE Bootloader for AMD Alchemy Built May 16 2007 at 12:35:08
      4. Portions copyright (c) 2004 F&S Elektronik Systeme GmbH
      5. Boot Loader, Version 1.12
      6. CPU running at 396000000 Hz
      7. Size of SDRAM memory: 32 MB
      8. BOOT FLASH: SST DEVCODE: 39VF040
      9. T: InitFlash ... Complete!
      10. FindRegistryValue: using registry 1
      11. System ready!
      12. Preparing for download...
      13. Press >S< to step into monitor...
      14. AUTO BOOT enabled
      15. Checking to see if a Windows CE image has been previously flashed...done
      16. Copying kernel from Flash to 0xA1300000, size 7179064, sectors 14022
      17. Kernel read from flash disk started ........................... finished in 3559 milliseconds
      18. Kernel decompression started ...................................................... finished in 547 milliseconds
      19. Found pTOC signature.
      20. Launching image at 80004004h...
      21. OEMCheckSignature: start= 0x0, offset= 0x0, launch= 0x0, downloaded= 0x0
      22. ---------------------------------
      23. ROMHDR Info (pTOC = 0x80A7C540)
      24. ---------------------------------
      25. dllfirst = 0x01DD01E8, dlllast = 0x02000000
      26. physfirst = 0x80004000, physlast = 0x80A7DCC8
      27. nummods = 0x00000086
      28. ulRAMStart = 0x80A7E000, ulRAMFree = 0x80AA6000, ulRAMEnd = 0x81DD4000
      29. ulCopyEntries = 0x00000001, ulCopyOffset = 0x802B9FE4
      30. ulProfileLen = 0x00000000, ulProfileOffset = 0x00000000
      31. numfiles = 0x0000003B
      32. ulKernelFlags = 0x00000000, ulFSRamPercent = 0x80808080
      33. ulDrivglobStart = 0x00000000, ulDrivglobLen = 0x00000000
      34. usCPUType = 0x0166, usMiscFlags = 0x0000
      35. pExtensions = 0x80005F28
      36. ulTrackingStart = 0x00000000, ulTrackingLen = 0x00000000
      37. --------------------------------
      38. OEMLaunch: Start 0x00000000 Length 0x00000000 Launch 0x00000000 Header 00000000
      39. Jumping to image at 0x80004004...
      40. Windows CE Kernel for MIPS Built on Jan 23 2006 at 13:14:58
      41. NetDCU6 V1.33 - Firmware Init
      42. Copyright (c) 2004 F&S Elektronik Systeme GmbH
      43. Build: May 23 2007/07:48:33
      44. OEMInit: call OEMKitlStart
      45. OEMInit: Process BootArgs
      46. Hook interrupts
      47. InitClock: CP0
      48. BOOT FLASH: SST DEVCODE: 39VF040
      49. OEMInit: MainMemoryEndAddress is 0x81dd4000
      50. OEMInit: MainMemoryEndAddress is 0x82000000
      51. OEMInit() finished
      52. ...
      53. //<------------------------------------------- normal boots to a running system
      54. //<------------------------------------------- hier wird normal und erfolgreich zu Ende gebootet.

      I upgraded a few days ago from Kernel V1.20 to V1.33, on both Kernels I have the same issues, so an update changed nothing on this point. Everything else is working fine, except the reboot troubles.

      The question is, why works a clean, fresh boot fine, but a reboot fails with "bad data at sector"?

      Bis vor wenigen Tagen war darauf der Kernel V1.20 im Einsatz, ich habe diesen nun auf die aktuelle V1.33 aktualisiert. Bei beiden Kernel Versionen war der Fehler genau der gleiche, ein Update hat also den Fehler nicht beheben können. Wie gesagt, das Gerät und WinCE 4.2 arbeiten, bis auf diese Reboot-Probleme, einwandfrei.

      Die Frage ist also warum schlägt nur der Reboot mit "bad data at sector" fehl, der Kaltstart aber nicht?
      Wie kann ich es beheben?

      Re: kein Reboot möglich - bad data at sector

      Hallo,

      ich habe ein ähnliches Problem mit der Systemfunktion zum Reboot, allerdings auf einem F3S Kernel (Version 2.03). Rufe ich die Funktion

      Source Code

      1. KernelIoControl(
      2. IOCTL_HAL_REBOOT,
      3. NULL,
      4. 0,
      5. NULL,
      6. 0,
      7. NULL);


      auf, erhalte ich im darauffolgenden Neustart folgende Ausgabe:

      Source Code

      1. Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built Mar 13
      2. 2003 23:05:28
      3. Size of SDRAM memory: 32 MB
      4. Windows CE Bootloader for AMD Alchemy Built Jun 13 2007 at 16:18:06
      5. Portions copyright (c) 2004 F&S Elektronik Systeme GmbH
      6. Boot Loader, Version 2.0
      7. Size of SDRAM memory: 32 MB
      8. BOOT FLASH: SST DEVCODE: 39VF040
      9. T: InitFlash ... Complete!
      10. InitBootpart ... Complete!
      11. FindRegistryValue: using registry 1
      12. System ready!
      13. Preparing for download...
      14. Press >S< to step into monitor...
      15. Checking to see if a Windows CE image has been previously flashed...done
      16. Copying kernel from Flash to 0x81300000, size 7181212, sectors 14026
      17. Kernel read from flash disk started FMD: ReadPage() ECC detected uncorrectable D
      18. ata Error! (Addr:5977)


      Anschließend tut sich nichts mehr. Erst nach einem Neustart wird wieder regulär gebootet.
      Weiß jemand Rat?


      Grüße, Kaiser

      Re: kein Reboot möglich - bad data at sector

      There seems to be a problem with the kernel compression. I have noticed that the soft reboot is working well when kernel compression is disabled in bootloader. Unfortunatly the real reason for this behavior can not be determined currently. We will post in this thread if there are some new expertises.
      Software developer, F&amp;S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

      Re: reboot error: bad data at sector / Fehler bei reboot

      Thank you for the answer, I translated my thread above from german to english.

      What is difference between a reboot and coldboot on a NetDCU, maybe something doesn't get a clean reset as it should - this could be the starting point for searching the error.

      Re: reboot error: bad data at sector / Fehler bei reboot

      I turned compression of with Z0, but then i get this error:

      Brainfuck Source Code

      1. Press >S< to step into monitor...
      2. AUTO BOOT enabled
      3. Checking to see if a Windows CE image has been previously flashed...done
      4. Copying kernel from Flash to 0xA0004000, size 7179064, sectors 14022
      5. Kernel read from flash disk started ........................... finished in 3558 milliseconds
      6. Image not found at 0x80004000

      If I turn it on again with Z1 then its booting normal.
      But the adress is different:

      Brainfuck Source Code

      1. Press >S< to step into monitor...
      2. AUTO BOOT enabled
      3. Checking to see if a Windows CE image has been previously flashed...done
      4. Copying kernel from Flash to 0xA1300000, size 7179064, sectors 14022
      5. Kernel read from flash disk started ........................... finished in 3559 milliseconds
      6. Kernel decompression started ...................................................... finished in 547 milliseconds
      7. Found pTOC signature.
      8. Launching image at 80004004h...

      What is wrong? -do I have to reflash it after I change compression mode?

      Re: reboot error: bad data at sector / Fehler bei reboot


      What is wrong? -do I have to reflash it after I change compression mode?

      Yes, after enabling/disabling the compression, the kernel has to be flashed again.
      Software developer, F&amp;S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.