Hello; I'm building Celadon for development purposes. I'd like to 'unlock' the device and so far I've been removing 'flashing lock' from installer.cmd script to achieve this. However, now I noticed this does not work anymore. If I remove 'flashing lock' line, the device won't boot at all. Is this a bug somewhere or is there another way to unlock? Thanks; // Tapani

Hi; Thanks for the steps, I'll try these out. BTW is there any plan to update to Mesa 18.3.x or 19.x at some point? Right now it seems to be 18.2.6 which is starting to be old, most distributions have more new version and new Mesa would have new features as example AHardwareBuffer support.

// Tapani On 3/8/19 2:19 PM, Ren, Chenglei wrote: >      CC Tan Ming, thanks. >      Hi Tapani, I tried last week and remove "flashing lock" does > work. Do you use the latest code? I will try latest code next week. >      I use following steps to remount DUT. >      Steps to remount: >                 Enable the UEFI shell boot option >                 Press F2 to enter the BIOS setup program. >                 In the 'Advenced' -> 'Boot' -> 'Boot Configuration' -> > 'Boot Devices', enable the 'Internal UEFI Shell' check box. >                 Reboot device >                 Only do the above steps for one time. >                 Prepare for a USB disk, format it as vfat file system. >                 Unzip the generated celadon-flashfiles-eng.xxxxxx.zip > to the USB disk. >                 Modify the installer.cmd in the USB disk. >                 Delete the line of 'flashing lock' >                 Plugin the USB disk to KBL NUC. >                 Power on KBL NUC, press the F10 to enter the BIOS boot > menu. >                 Select boot to UEFI shell. >                 Do not press ESC key to skip run the startup.nsh, let > the startup.nsh to run >                 Reboot the device. >                 Enter Android shell, use adb shell or serial port. >                 Su to root. >                 run the following commands: >                     a. avbctl disable-verity >                     b. avbctl disable-verification >                 Reboot the device. >                 Unlock the device, AND format/erase the data partition >                     Modify the installer.cmd in the USB disk. >                                Only has one line: >                                format data >                                Note: if you create a new file, please > change the file type to ASCII. The default new file type in 'edit' > command is UNICODE. >                 Plugin the USB disk to KBL NUC. >                 Power on KBL NUC, press the F10 to enter the BIOS boot > menu. >                 Select boot to UEFI shell. >                 Do not press ESC key to skip run the startup.nsh, let > the startup.nsh to run >                 Reboot the device. > > Thanks, > Chenglei > > -----Original Message----- > From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of > Tapani Pälli > Sent: Friday, March 8, 2019 8:10 PM > To: celadon(a)lists.01.org > Subject: Re: [01.org Celadon] flashing process > > I just realized that it could be also because of the changes I've made > (in Mesa driver side) .. however since I don't have way to capture or > see the log I'm not sure if this would be the case. Usually I can see > the Android boot logo even if surfaceflinger is not able to start but > now it simply stucks in the very first screen displaying Intel logo > and bunch of red errors from bootloader. > > In any case, it would be helpful if someone can confirm that 'flashing > lock' can be safely removed. > > Thanks! > > > On 3/8/19 1:48 PM, Tapani Pälli wrote: >> Hello; >> >> I'm building Celadon for development purposes. I'd like to 'unlock' >> the device and so far I've been removing 'flashing lock' from >> installer.cmd script to achieve this. However, now I noticed this does >> not work anymore. If I remove 'flashing lock' line, the device won't >> boot at all. >> Is this a bug somewhere or is there another way to unlock? >> >> Thanks; >> >> // Tapani > -- > Celadon mailing list > Celadon(a)lists.01.org > https://lists.01.org/mailman/listinfo/celadon >

Tapani Pälli wrote: > BTW is there any plan to update to Mesa 18.3.x or 19.x at some point? https://github.com/intel/external-mesa has been based on 18.3 release for quite some time now. I suppose the Celadon process has changed and is no longer actively tracking that repo?

On 3/11/19 12:43 AM, Strasser, Kevin wrote: > Tapani Pälli wrote: >> BTW is there any plan to update to Mesa 18.3.x or 19.x at some point? > > https://github.com/intel/external-mesa has been based on 18.3 release > for quite > some time now. I suppose the Celadon process has changed and is no longer > actively tracking that repo? > Yeah sorry, it seems to be based on 18.3.2 now, not sure how I managed to repo sync some old stuff :/ Then all is actually fine! Something seems fishy with upstream repo so I'll try to check what is going wrong.