52 replies to this topic

[mikel]

Thanks first of all.

As startup1 I can flash something different and test it a little. Then report when something works.

[littlesat]

When you flash our image via USB you should have the following files in the boot STARTUP folder.... you have different files...

Therefore I recommend remove all the STARTUP_ you have now (keep the STARTUP file without underscore) and replace them by these files... Than mode 12 should work again....

 

I suggest it was an ancient time when you flashed your box with an USB... or it was done with an image that did not have all the required STARTUP_ files...

Attached Files

•  StartupFiles_h7.zip   1.88KB   9 downloads

Edited by littlesat, 10 February 2020 - 10:58.

[mikel]

Thanks Littlesat,

 

Can I do this without USB flash and only exchange files?
Find only the following files in the boat.
What content should be exchanged or what solution is there, your zip file has a different description.

Where do the new files belong?

 

STARTUP
STARTUP_1
STARTUP_2
STARTUP_3
STARTUP_4

[littlesat]

Yep... you should be able to delete the current files and replace them by the one I posted here... Then mode 12 should work again.

These files you can delete

 

STARTUP_1
STARTUP_2
STARTUP_3
STARTUP_4

 

(do not delete the current STARTUP file!!!)

 

The files do belong to the device where you have now the STARTUP file... I know you're able to mount it...

Edited by littlesat, 11 February 2020 - 13:25.

[mikel]

Hello Littlesat,

 

Unfortunately did not work, box no longer starts, brought back to life via Startup1.
All images tested so far run with Modus12, that is PLI_7.0, 6.2 and of course the third-party images HDF and ATV. It certainly doesn't make sense to invest more work here, maybe set everything up again, on occasion!

 

Thanks for your effort Littlesat.

[littlesat]

Your ‘boot’ stuff in your box is not what it should be....!!!! It has different files than we should have and that is fully proven!!! I recommend you reflash your box completely to get the boot stuff to the latest stuff as it should be....

Edited by littlesat, 12 February 2020 - 11:41.

[mikel]

Thank you for your effort Littlesat, will do everything again if possible.

[littlesat]

From my side sorry for the inconvenience.... 

 

Here you can see how the nine STARTUP files are made...

 

https://github.com/z...ltiboot.bbclass

 

And that is the latest we have in our current USB flash image.... And those include the MODE_12 STARTUP files.

Edited by littlesat, 12 February 2020 - 14:31.

[mrvica]

did other image teams catch up with latest zgemma bbs, if he flash USB image all partions are gone, he will have to set up all again, other images than OpenPLi may not be compatible

[mikel]

Hello Littlesat,

 

can't i bring https://github.com/z...ltiboot.bbclass into my image?
Maybe that will work. If that is possible, of course I need instructions on how to do it. Or if the transfer is only via USB Flash, then the other images may no longer work and that would not help me either.

 

Thank you.

[littlesat]

When was the last time you fully reflashed your box... I suggest long long long time ago so most likely you've one of the first 'bootloaders'.

[mike]

The new set-up is already something, then probably must flash again with USB.

Can I try to install a new boot loader?
Where can I find the latest for the box?

 

Thank you

Edited by mike, 13 February 2020 - 16:13.

[mike]

New image or is bootloader enough?

[twol]

@Littlesat - OpenPli and the OE-A use different STARTUP files for the HD51 and H7 - this has always been the case.

This means you have to check for the simple OE-A STARTUP_x  files which are  setup for boxmode 1 and for boxmode 12 do a Replace (1 -> 12).

For OpenPli you have to choose the correct BOXMODE startup.

 

The vendors (Zgemma/ Mutant) know what is used by both OpenPLi and the OE-A and still allow both to be different - hence the issues...... they are really unhelpfull

 

Depending on which image is installed first (usb) flash you will have different STARTUP files

Edited by twol, 13 February 2020 - 19:58.

[littlesat]

Nope.... our bsp is from the manufacturer and with us you get the startup files the manufacturer describes.... when the first image you installed deviates now.... they create their own bsp and are far behind...
The way we do it now was discussed by us directly with the manufactures which results in the extra mode1 and mode 12’srartup files.... so when it not works you need to flash a new first image first...

[mikel]

This confirms my tests, only with PLI7.2 there are problems with the Modus12, it can be good, as Littlesat says, that the manufacturer's specifications are included here, if the other manufacturers don't do it, it works differently. If you now flash Pli_7.2 via USB, the other images do not work in Modus12, so no one is helped.

In summary, it is therefore clarified why all other current images from the other image builders and also the PLI_6.2 work in mode 12, these still have the old structure, i.e. a deviation from Pli_7.2.

 

Here you should come to a common denominator!

 

@Littlesat - OpenPli and the OE-A use different STARTUP files for the HD51 and H7 - this has always been the case.

This means you have to check for the simple OE-A STARTUP_x  files which are  setup for boxmode 1 and for boxmode 12 do a Replace (1 -> 12).

For OpenPli you have to choose the correct BOXMODE startup.

 

The vendors (Zgemma/ Mutant) know what is used by both OpenPLi and the OE-A and still allow both to be different - hence the issues...... they are really unhelpfull

 

Depending on which image is installed first (usb) flash you will have different STARTUP files

 

[twol]

Nope.... our bsp is from the manufacturer and with us you get the startup files the manufacturer describes.... when the first image you installed deviates now.... they create their own bsp and are far behind...
The way we do it now was discussed by us directly with the manufactures which results in the extra mode1 and mode 12’srartup files.... so when it not works you need to flash a new first image first...

@Littlesat - reality is that there are two different systems and both can be handled (as it is in pre Develop  builds) - if you don't then these crashes will continue.

The OE-A were supporting many of these boxes before you supported in OpenPli, and then you expect them to change because you have a "manufacturers supplied" bsp and your code only supports that bsp!  

[littlesat]

Even OpenATV is using somehow my multiboot code now. It had hardcoded stuff in SystemInfo.py. I did remove this in develop and go for a scan in STARTUP_ files to make this more softcoded. It is indeed not compatible anymore with the hardcoded stuff.

For now I also do not have any overview or idea how make this somehow backwards compatible. 

I think we SHOULD have all the possibilities as STARTUP_.. files in the 'boot' device.

When everyone wants to keep blind and stuck on history and hardcode stuff that is not my fault.

Edited by littlesat, 14 February 2020 - 09:52.

[mikel]

Thank you again for your effort Littlesat, so you know halfway why.

[littlesat]

I fully understand why...

 

I just downloaded from the H7 openatv 6.3 and when I verify the boot partition here it has only STARTUP, STARTUP_1, STARTUP_2, STARTUP_3 and STARTUP_4. OpenATV and maybe all the other images do miss the MODE_12 option here. So to solve this we can only fallback to code that directly writes a STARTUP file in a hardcoded way. Or disable mode 12 support when you have the old (=OE-A) boot device.

Edited by littlesat, 14 February 2020 - 10:39.