Thanks!
I sent the file, and will test the backup image when I finish testing ATSC on the Vu+ Zero. EB
Printable View
Thanks!
I sent the file, and will test the backup image when I finish testing ATSC on the Vu+ Zero. EB
The ATSC solution from Sundtek works on the Zero as expected.
[Only registered and activated users can see links. Click Here To Register...]
I will check the backup file issue next.
Looks like that file bricked the Zero when the backup was reloaded. Will have to recover it and see if I made a mistake somewhere or if it is a bad file.
Recovered by reloading VIX. Please send another test file as that one bricks the box. Thanks.
What do you mean exactly by bricked ?, My definition of bricked is the receiver being rendered totally inorerable, IE dead. which is obviously not the case if you were able to reflash another image to it.
Does it cause the image to crash or put it into a bootloop or prevent it booting up ??. The more detailed info you can give the better along with any debug logs or crash logs etc, also could you try generating a serial log of a backup being created with just the default image ?.
Basically I need any and all info / diagnostic data to be able to debug this as the main guy working on it (Andy) does not have this receiver on which to test.
Let's use the term bootloop then. Since you do not have but one led, and a black screen, it is hard to tell what happened.
I will connect to the RS232 port and do it all again. Doing this should generate a log so we can see exactly what happened or is happening.
OK try this. Extract this new archive and FTP the imagemanager.py file to the same location as before (backup the original.pyo file with the same name) then reboot the receiver, the receiver it self will generate a new .pyo file from this .py file if that makes sense ??.
p.s for those who don't know
.py files are human readable python files
.pyo are machine readable python files.
let me know what happens please.
If the above file allows you to create a backup let me know if it also creates a file called force.update
Thanks.
Smooth...Works flawlessly as far as I can tell.
The force.update file is in there too.
You may commit that one. Tell them THANKS! EB
No worries mate, I will let Andy know it's ok to submit the fix to the GIT.Quote:
Originally Posted by el bandido [Only registered and activated users can see links. Click Here To Register...]