-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem flashing on a Miracelbox MBtwin #12
Comments
Hmmmmm.....I can (now) see an oddity in the Py3 image build. The kernel.bin is not a multiple of 512. |
Is the ofgwrite “GUI” visible on the TV screen? You could try doing this:
|
What is that?Looks like it belongs to a Beyonwiz T3. |
The GUI starts up, the first "block" is filled in on the top progress bar - then the screen goes blank. At this point it is looping and filling the messages log with that error message. The command being run is:
|
It's a Miraclebox MBTwin. Which, IIRC, is very similar. |
Can you please execute this in Telnet: This won’t flash your box (because of -n switch), but it maybe shows the problem. Please post the output. |
That finds nothing wrong...
|
"peteru" is a Beyonwiz developer and "T3" is a Beyonwiz model so no clue what that is doing in mbtwin build. |
Similar paths are mentioned through the dvb.ko file. Possibly he was involved in compiling it (10 years ago)? Anyway, it's the same file that gets used when successfully flashing my Py2-Vix made backup. |
Please flash the image via USB to confirm that it works. Do you have a serial cable for the box? |
It does. Slow, but it gets there and then I can boot into the Py3 version of OpenVix.
No. |
And if you first stop e2 and then flash from telnet? |
I actually tried a reflash of the image (from my now-running Py3 Vix) and that also failed (screen blanked shortly after the "start").
That ^C^C^C is me trying to get out of it, but it's hung (looping in the kernel). Again, it hadn't actually flashed anything, as a power off/on brought back my Py3 Vix. However, one further wrinkle. So it seems to be something specific to that one image file(?). |
So, a quick recap.
|
And I've found out what the problem is!!! The build process produces an image file that contains So the problem is related to the Now, I do remember some time (years?) ago that the original OpenVix start-up splash banner went away and was replaced by a plain |
Ofgwrite don’t use splash.bin. I still don’t understand how this can cause problems… |
According to the log it might hang while opening the framebuffer. Is not 100% sure but this is one of the steps after the last log message. |
OK. Having got the system to flash without the |
I'm trying to (couch) flash a build of the Python3 build of OpenVix.
The image build has completed OK and I have this:
but when I try to couch flash this ofgwrite starts up, then the screen goes blank and nothing further happens.
The syslog is reporting (lots of) this error:
If I reboot the box at this point it boots back to the previous image (indicating that no flashing took place at all?)
If I take a full image backup of the current (Python2-based) system and couch flash that all is OK.
That image is:
so it doesn't look as though it's an image size issue (as this one is larger)
Any ideas as to what the problem actually is?
The text was updated successfully, but these errors were encountered: