Chat part1

<lukasz> Hi TL
<lukasz> How did they manage to boot the Linux image?
<tllim> yes
<lukasz> but how
<tllim> due to if the Adam build on SD card and Android build on eMMC, the Pinebook Pro will boot fail
<lukasz> Yes
<tllim> all the Pinebook Pro in factory already has Android build
<lukasz> yes
<tllim> this logic is flaw
<lukasz> Ok, so, are we on track?
<tllim> cannot be on track
<lukasz> Right, so I am not sure I understand whats happening right now. They removed the eMMC and booted the OS from SD correct?
<tllim> the China team tested the Adam build and agreed is an efficient build
<lukasz> Sure ^ this we know
<tllim> but is a totally nightmere build for production
<tllim> they will work around the clock and make the first 100 unit production tomatch this build, and this means they needs to work over this weekend
<tllim> however, they refuse on second production build using this Adam build.
<lukasz> Its not a problem with Adams build - its the RK3399 boot sequence
<lukasz> if they have no android on eMMC then its a simple process - we could even automate it for them
<tllim> based on the rock64 testing, production request me to consider ayufan build which is more production friendly
<lukasz> But I tested ayufans build and IT DOES NOT boot over Android on eMMC -- it changes nothing
<tllim> I agreed that the first build is 100 unit, they can bite the bullet and do that.
<tllim> On the second 1500 unit production, this is not possible
<tllim> anyway, this is the fact.
<lukasz> Have them not put Android on the eMMC and problem is solved
<lukasz> have a blank eMMC
<lukasz> If they need to run tests, then they can have a SD with the android build
<lukasz> We can put together a SD -> eMMC flashing build for them
<tllim> lets not argue about asking factory to accomodate again on the second production
<tllim> I have explain the situation
<lukasz> I simply do not see how it makes any difference for them whether they install an eMMC with or without Android on it
<tllim> if the Adam current build cannot be improved to ease the productions, I needs to check with ayufan.
<lukasz> How does using ayufans build change things?
<tllim> how the hell the factory do the production testing without Android test build?
<lukasz> They can have a clean / empty eMMC, and run Android from a SD card
<tllim> based on Chian team study on the ayufan rock64 build sequence, they believe ayufan build match with production flow
<lukasz> Then take out the SD card with android and insert autoflashing Linux SD
<tllim> where is the autiflashing Linux SD?
<lukasz> we can build one. But if they think that they can boot OR flash ayufan's build with an eMMC that has Android on it, then you can tell them they can't. I spent all night, until 5 in the morning, with Adam trying to find a way
<tllim> on the first 100 unit production, factory ok to entertain and also has cause the Pinebook Pro BOM price incarese due to factory expected to work over weekend.
<tllim> this situation cannot repeat on second production build
<tllim> the first question is why Adam build case the boot fail when there is Android build in eMMC?
<lukasz> Because RK3399 is hardwired to grab uboot frist from eMMC THEN from SD. So, in effect, if you have Android on eMMC then android uboot is used and not Adams
<lukasz> The uboot on that A7.1.2 build is over 2 years old
<tllim> in other OS build, when place in SD card, the Android eMMC doesn't hang and just proceed to boot up into Android OS>
<lukasz> Of course, I can boot another android OS too
<lukasz> because it has a special recovery partition
<tllim> then why Adam build hang
<lukasz> no Linux images have that
<lukasz> both ayufan and Adam use uboot to extlinux
<lukasz> both of their builds have been hardcoded to look for bootable parititons on SD over eMMC
<tllim> the Adam build hang and on ayufan build, the Android eMMC will continue boot back to Android OS.
<tllim> brb 10 mins
<lukasz> ok