Hi, My Skybox M3 with no apparent reason, started to loop on the boot. When it is powered it goes from L001 to L100 then STYP and at that point it reboots. It happened when I switched mains on (was with mains off) updated newcamd.list file via USB and powered it off. When powered it back on, it started the boot loop. No firmware changes. http://www.digital-kaos.co.uk/forums...-cable-233298/ Found this thread, did tried to update via RS232 but it never solved the problem (boot loop still there). Anyone can help me please explaining how should I recover my 2 dead Skybox M3. TY
Skybox M3 stuck in a bootloop. boots -> L001...L100 -> STYP -> reboot (boot loop)
Collapse
X
-
Thank you for your reply. I did use 2 diferentes PSU. One PSU has 12v and 5A, so unfortunatly not PSU.Comment
-
Thank you 4 your reply. This is the only line I had.
CWS_MULTIPLE = .................................................. ....................... 01 02 03 04 05 06 07 08 09 10 11 12 13 14. Thanks in advance.Comment
-
There is a method to solve your problem , Change your firmware size to 8M , You must have 2 files , one is your firmware (4M size), the other bin file is size 4M, ( all the value in file is zero). Merge the two files to a NEW FIRMWARE(8M size), Recovery the new firmware to your flash with RS232 NULL cable, I think all will be OK. By the way ,Please be careful :5536-3000= 2536, too many ports !!!!Comment
-
Thank you for the reply. I'm a bit stuck how to create a file with 4Mb filled with zeros and then how to merge them. Could you please post a step by step how to or if you have the files, post them. Thank you.There is a method to solve your problem , Change your firmware size to 8M , You must have 2 files , one is your firmware (4M size), the other bin file is size 4M, ( all the value in file is zero). Merge the two files to a NEW FIRMWARE(8M size), Recovery the new firmware to your flash with RS232 NULL cable, I think all will be OK. By the way ,Please be careful :5536-3000= 2536, too many ports !!!!Last edited by t4rz; 9 April, 2013, 11:49.Comment
-
I have done the bin file for you .Attached FilesComment
-
Thank you Leon. You saved my 2 skybox M3. I did upgrade with your reset firmware and VOILA! it worked 100%. Thank you millions times. For the sake of forum information: The file F3_M3_F5_reset.rar has 2013-03-27 firmware and nothing on the TPS_PROG. As name states, it is a reset firmware. It saved my 2 skybox M3 that boot fine, go until L100 fine, goes to Styt and then reboots. I did nothing before that happened than update newcamd.list and restart on one box, and the other box it was a change of time zone then box restarted. In my opinion, this boxes have a issue with power stability (capacitors) or power lack (power adaptor with few mA) that leads to a failure in what is read from RAM when it is saving to ROM as it needs (eg: as box powers off to save state on ROM). Leon, do you have any idea what happened to these 2 boxes as I did nothing like using others TPS_PROG or update firmware or so?Comment
-
You have too many TCP/IP ports in your new***.list files, the max port count is 32 . It will cause your box reset . Please be careful.Thank you Leon. You saved my 2 skybox M3. I did upgrade with your reset firmware and VOILA! it worked 100%. Thank you millions times. For the sake of forum information: The file F3_M3_F5_reset.rar has 2013-03-27 firmware and nothing on the TPS_PROG. As name states, it is a reset firmware. It saved my 2 skybox M3 that boot fine, go until L100 fine, goes to Styt and then reboots. I did nothing before that happened than update newcamd.list and restart on one box, and the other box it was a change of time zone then box restarted. In my opinion, this boxes have a issue with power stability (capacitors) or power lack (power adaptor with few mA) that leads to a failure in what is read from RAM when it is saving to ROM as it needs (eg: as box powers off to save state on ROM). Leon, do you have any idea what happened to these 2 boxes as I did nothing like using others TPS_PROG or update firmware or so?Comment
-
Tried a different cable, the other power supply, other firmware. It turned out that one of the contacts on the board was not soldered. Soldered it and download the firmware properly.Comment

Comment