October 2019 - Celadon

Re: [01.org Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build

by Fan, Yugang

For “Can I just disable them in device/intel/project-celadon/cel_apl/device.mk ?”, GFX team can’t answer this as it related to whole system integration I think. For APL NUC 4K support, we didn’t find 4K EPIC. And APL NUC hardware EDS shows HDIM only support max resolution 4K 3840x2160 30fps, and we also known that 4K also met some flicker issues due to display buffer side limitation when enabling some GFX feature, e.g. RBC. APL IVI may can boot to 4K 3840x2160 60fps, but we don’t know if there are some other potential issue. For different result of APL IVI and APL tablet of 4K 3840x2160 60fps, I got info that we haven’t verified APL tablet for long time, there should has some diffs, but not sure if we need continue investigate it as no 4k EPIC found. Above are all I know, so possible way is: we start to verify 4K 3840x2160 30fps(but not sure it is make sense to use 30 fps for 4k, or force using 1080P 60 fps for big resolution) for APL if we need support 4K, and figure out if we need limit the max resolution to 4K 3840x2160 30fps in somewhere, e.g. some config files/vbt. Best regards, Yugang From: Dominik Louven [mailto:dlouven@videro.com] Sent: Thursday, May 9, 2019 11:58 AM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello everyone, Any news on this ? Best regards, Dominik Louven On 6. May 2019, at 12:12, Dominik Louven <dlouven(a)videro.com<mailto:dlouven@videro.com>> wrote: Hi Swaroop, Thank you in advance. To be a little more specific. I would like to exclude all car components from the cel_apl build. Can I just disable them in device/intel/project-celadon/cel_apl/device.mk ? Please let me know if you find a way to exclude the car components from the compilation , because my NUC is not embedded in a car =) Best regards, Dominik Louven On 6. May 2019, at 12:09, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik Please give me some time , I will check and let you know after taking a clean tablet build from GitHub Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Monday, May 6, 2019 3:26 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, It works fine now, I can boot into OS with celadon_apl-userdebug. Is it possible to disable the car launcher and car applications in the build ? Best regards, Dominik Louven On 3. May 2019, at 12:24, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik Celadon is for tablet and cel-apl is for APL NUC IVI Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Friday, May 3, 2019 3:08 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, I used : lunch celadon-userdebug Maybe that’s the issue here. I will try again with your steps. What’s the different between the celadon and the cel-apl build ? Best regards, Dominik Louven On 3. May 2019, at 11:35, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominic I used a local build based on WW13 BIOS VERSION --> AYAPLCEL.86A.0059.2018.1226.1422 We used below steps to compile • source build/envsetup.sh • lunch cel-apl-userdebug • make SPARSE_IMG=true flashfiles -j4 Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Friday, May 3, 2019 3:02 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, That is weird. Did you use the same manifest ww201913 ? What BIOS version is your NUC running on and do I have set specific settings in the BIOS ? Did you compile the OS with different steps ? Best regards, Dominik Louven On 3. May 2019, at 11:29, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik, When I connect my NUC6CAYH (APL) to an 4K Display (View Sonic) There was no issue for us in booting to home screen Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Friday, May 3, 2019 2:42 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, Thanks a lot. If you need any more information please let me know. Best regards, Dominik Louven On 3. May 2019, at 11:08, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik We are checking at our end , Will update shortly Regards Swaroop From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Dominik Louven Sent: Friday, May 3, 2019 1:49 PM To: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello everybody, I have checked out the latest stable branch ww201913.xml . When I connect my NUC6CAYH (APL) to an 4K Display (resolution 3840x2160) I am unable to boot into the launcher. The NUC hangs in android boot screen. What can I do ? Please find logs below : logcat https://pastebin.com/d8eGtPha dumpsys https://pastebin.com/UjrxC5PW bugreport https://drive.google.com/open?id=1oy9uQqqMpG_95Vsm4sUpH6pRjqnscPhN I am running the latest BIOS on my NUC and the os was compiled using : source build/envsetup.sh lunch celadon-userdebug make SPARSE_IMG=true flashfiles -j4 Best regards, Dominik Louven -- Celadon mailing list Celadon(a)lists.01.org<mailto:Celadon@lists.01.org> https://lists.01.org/mailman/listinfo/celadon

11 months

8
9
0 / 0

[CELADON] Android Q Official APL_NUC based on 2019_WW41 Release

by Balan, Swaroop

[cid:image001.png@01CFE4A4.BAC02DC0] Android Q CELADON 2019_WW41 Release [cid:image008.png@01CF54D4.99DD97B0] October 22nd 2019 - The Android SI team announces [APL-NUC][Kernelflinger] [2019WW41] [Celadon Q Master branch QP1A.190711.019] release. * Manifest : https://github.com/projectceladon/manifest/blob/master/stable-build/ww201... * Celadon Binary : https://github.com/projectceladon/celadon-binary/blob/master/ww201941/cel... (Pre-Production binary) * Release Notes : https://github.com/projectceladon/celadon-documentation/blob/master/sourc... * Documentation : https://01.org/projectceladon/documentation 21-Oct-2019<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> Note * Android Q is supported on Intel Platform and Apollo Lake NUC (NUC6CAYH<https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc...>) is the leading platform for IVI configuration (lunch target: celadon_ivi). * This is a Pre-Production binary Q Release for evaluation and development purposes and it cannot be used for production purposes. Integrated Features<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> * Graphics Memory Allocator (Gralloc) 1.0 * HDMI display support * HWC 2.3 support for Display * Mass Storage USB 2.0 and 3.x devices are supported * adb & fastboot supported over USB 2.0 * adb over DbC is supported * adb over WIFI and Ethernet is supported * Audio playback over USB and 3.5mm Headset supported * Wi-Fi 802.11 a/b/g/n/ac and Bluetooth 4.2 * Wired Ethernet support * Android Kernelflinger boot support * Thermal Daemon is enabled for project |C|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> * Video Codec support on |C|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> Decoder * AVC High profile @ Level 5.1 (4k@30fps<mailto:4k@30fps>) * HEVC Main and Main 10 profile @ Level 5 (4k@30fps<mailto:4k@30fps>) Note Main 10 with BT2020 and ST2084 information is not supported * VP9 profile 0 @ Level 5 (4k@30fps<mailto:4k@30fps>) * Vp8 8 bits 1080p@60fps<mailto:1080p@60fps> Encoder * AVC High profile @ level 4.1 (1080P@30fps<mailto:1080P@30fps>) * HEVC Main profile @ Level 4 (1080P@30fps<mailto:1080P@30fps>) * Art-extension is enabled * f2fs filesystem support enabled * S3 Suspend/Resume is supported * Audio decoders supported: MP3, AAC-LC, AAC-ELD, HEAAC, HEAAC-V2, VORBIS, OPUS, FLAC, PCM/WAV * Audio Encoders supported: AAC-LC, AAC ELD, HEAAC, HEAAC-V2, PCM/WAV * SDHCI host controller is enabled * Security * SELinux enforcing, File Based Encryption, Trusty, Keymaster 3.0 * Reference solution - TPM based h/w binding reference implementation * User guide: ? SELinux Configuration and Rules ? How to Enable or Disable Trusty for Debugging * Flashing binaries via |PFT|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> * To reduce the flash time, Platform flash Tool can be used with the following configurations: ? Blank_without_lock (used for first time install or GPT layout change case) ? Update_without_lock (used for image update on installed device) If your device is in unlocked state: * "Blank_without_lock" duration is 30% of "Blank" * "Update_without_lock" duration is 5% of "Update" Important Notes and Remarks<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> |C|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> build has been validated on |NUC|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> Kit NUC6CAYH<https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc...> in the following function domains: Component Results Comments Wi-Fi OK Wi-Fi Hotspot OK BT OK File Transfer Protocol Audio Playback over USB/3.5mm Headset OK MP3, AAC-LC, AAC-ELD, HEAAC, HEAAC-V2, VORBIS, OPUS, FLAC, PCM/WAV formats supported Audio Record over USB HS/3.5mm Headset-in/Main Mic OK AAC-LC, AAC-ELD, HEAAC, HEAAC-V2, PCM/WAV formats supported adb connect over WIFI OK adb connect over Ethernet OK Display /Touch and Gesture OK Storage/SD Card OK Security OK Boot/Kernel OK USB devices over OTG OK Ethernet OK Fastboot OK Web browsing OK Video playback OK H264/H265/MPEG2/VP8/VP9 Video Playback Known Issues<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> * Flashing time takes longer while using the kernel flinger method (~30mins), To reduce the flash time, Platform flash Tool can be used. Also the "installer.cmd" file can be altered (as per the PFT configurations) and flashed using kernel flinger method. * adb over wifi and ethernet works only after, setprop service.adb.tcp.port 5555 and restart of USB debugging. * Device seen offline for 4-5 seconds on disconnect and reconnect of dbc cable. * Time and lock icon are displayed once on Android Start Animation when power on the DUT when connected with dual display. * Time flickers on All apps screen when launch Intel@Phone<mailto:Intel@Phone> Doctor and touch menu button. * Glitch observed while the DUT is booting to UI at the intel logo screen. To subscribe/unsubscribe: - subscribe/unsubscribe celadon mailing list using : https://eclists.intel.com/sympa/review/1a-weekly_release , also visit link : https://lists.01.org/mailman/listinfo/celadon

1 year

1
0
0 / 0

Re: Support for NUC8i5BNK

by Christoph Kaser

Great, looking forward to hearing from you :) I have attached a picture of the popup. Regards Christoph On 12.10.2019 02:41, Tan, Ming wrote: > Christoph: > We will try to check the trusty support in NUC8i5BNK. > > Can you share with me the picture of ' popup after android starts that tells me an internal error occurred and I should contact the manufacturer ' ? > > Thank you. > Tan Ming. > > -----Original Message----- > From: Christoph Kaser <lucene_list(a)iconparc.de> > Sent: Friday, October 11, 2019 9:46 PM > To: Tan, Ming <ming.tan(a)intel.com> > Subject: Re: [01.org Celadon] Re: Support for NUC8i5BNK > > Hello Ming, > > Unfortunately, I do not have access to a USB 232 converter at the moment. I will try to get one. > > I tried to use Celadon Q, but there was the same problem: After installation, the system does not boot. On Q, the last message in the log is "Jump to Android Linux Kernel now". > > However, I managed to get Celadon with Android 9 running: I compiled a version without trusty by following https://01.org/projectceladon/documentation/tutorials/security/trusty-ena.... > > This version runs on the NUC8. There is however a popup after android starts that tells me an internal error occurred and I should contact the manufacturer. > So I guess the problem is somewhere in trusty or the TEE. > > Best regards > Christoph > > On 10.10.2019 03:26, Tan, Ming wrote: >> Christoph: >> The red error message has not impact for boot to UI. We already change the log level in new version. >> If you can build the image by self, you can build a userdebug image and add the patch https://github.com/projectceladon/hardware-intel-kernelflinger/pull/5 to check the kernel log? >> You can refer to https://01.org/projectceladon/documentation/blogs/uart#enable-the-serial-... to use a USB RS232 convertor to get a USB serial port. Note: Use a FTDI chip based USB RS232 convertor. >> >> And can you try the Celadon Q? Simple use the newest version of Celadon? >> >> BR/Tan Ming. >> >> >> -----Original Message----- >> From: Christoph Kaser <lucene_list(a)iconparc.de> >> Sent: Wednesday, October 9, 2019 3:30 PM >> To: celadon(a)lists.01.org >> Subject: [01.org Celadon] Re: Support for NUC8i5BNK >> >> Hello Ming, >> >> Thank you for your reply. >> The BIOS version is BECFL357.86A.0074.2019.0916.1548, which should be the newest one available for this board (NUC8BEB). >> I am using a Kingston A1000 M.2-SSD with a size of 240 GB. >> >> After the first boot after the installation, there are the following messages in red (see attached images 1st_boot_*.jpg): >> >> Failed to read counter for simulate: Aborted >> key is not programmed. use the first derived key.: Aborted >> Init RPMB key sucessfully >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> [... something that scrolls by to quickly to read, but contains "invalid vbmeta header" ...] >> with result >> ERROR_INVALID_METADATA >> - setting unbootable. >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> >> After the second boot, there are the following messages (see attached images 2nd_boot_*.jpg): >> >> Failed to read counter for simulate: Aborted >> key is not programmed. use the first derived key.: Aborted >> Init RPMB key sucessfully >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> >> After the third boot, I get (see attached image 3rd_boot_01.jpg): >> >> BOOTLOADER ERROR CODE 01 >> >> Your device has failed verification. >> It is corrupt. It can't be trusted >> and will not boot. >> >> Please contact customer support >> from your device's manufacturer. >> >> And on the left, in red: >> >> Init RPMB key sucessfully >> Failed to read RollbackIndex_0000 EFI variable: Not Found >> No bootable slots found. >> Failed to get avb slot a/b flow result for boot: Invalid >> Parameter >> >> After a while, the image of a broken android is shown with the messages (see attached image 3rd_boot_02.jpg): >> >> BOOTLOADER ERROR CODE 07 >> >> WARNING: >> No valid boot image found. >> >> (etc.) >> >> And the red messages: >> XDCI is disabled. please enable it in BIOS: Unsupported >> Can't run self implemented USB device mode protocol: Unsupported >> Make sure xDCI is enabled in BIOS >> ADB is listening on TCP 172.16.0.165:5555 >> >> I hope the mailing list will allow the attachments. >> >> Best regards >> Christoph >> >> On 09.10.2019 03:58, Tan, Ming wrote: >>> Christoph: >>> For >>> https://media.githubusercontent.com/media/projectceladon/celadon-bina >>> r y/master/ww201851/cel_apl-flashfiles.zip, >>> what is the last picture when boot failed? >>> What BIOS version of your NUC8i5BNK? >>> What storage are you using? >>> >>> BR/Tan Ming. >>> >>> -----Original Message----- >>> From: lucene_list(a)iconparc.de <lucene_list(a)iconparc.de> >>> Sent: Tuesday, October 8, 2019 11:50 PM >>> To: celadon(a)lists.01.org >>> Subject: [01.org Celadon] Support for NUC8i5BNK >>> >>> Hello everyone, >>> >>> I tried to install Celadon on a NUC8i5BNK, but it fails to boot. >>> I tried both a prebuilt celadon image (from >>> https://media.githubusercontent.com/media/projectceladon/celadon-bina >>> r >>> y/master/ww201851/cel_apl-flashfiles.zip) >>> and building my own (from the celadon/p/mr0/master branch). >>> >>> Installation worked fine, but when booting from the disk it fails and >>> eventually displays "Your device is corrupt. It cannot be trusted and >>> will not boot" >>> >>> Should Celadon work on this device? Is there something I can do to >>> make it work, such as disabling verified boot? >>> >>> Regards >>> Christoph >>> -- >>> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an >>> email to celadon-leave(a)lists.01.org >>> -- >>> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an >>> email to celadon-leave(a)lists.01.org >> -- >> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an >> email to celadon-leave(a)lists.01.org >

1 year

3
5
0 / 0

Configure display resolution

by lucene_list＠iconparc.de

Hello everyone, I am running Celadon on an Intel NUC attached to a no-name display (via HDMI). Unfortunately, this display seems to report the supported resolutions in the wrong order, so every OS selects 1920x1080 as default resolution, even though the display supports 3840x2160. When running another OS, I can change the resolution in the settings and it works. But on Celadon, I did not find a way to specify the preferred display resolution (not even in the source build). Is there a way to select the resolution? Best regards Christoph

1 year

7
7
0 / 0

Support for NUC8i5BNK

by lucene_list＠iconparc.de

Hello everyone, I tried to install Celadon on a NUC8i5BNK, but it fails to boot. I tried both a prebuilt celadon image (from https://media.githubusercontent.com/media/projectceladon/celadon-binary/m...) and building my own (from the celadon/p/mr0/master branch). Installation worked fine, but when booting from the disk it fails and eventually displays "Your device is corrupt. It cannot be trusted and will not boot" Should Celadon work on this device? Is there something I can do to make it work, such as disabling verified boot? Regards Christoph

1 year

3
3
0 / 0

Reminder: Project Celadon October Technical Community Meeting

by Mcdonald, Senalka

Join us at the Project Celadon October Technical Community Meeting We recently launched monthly Technical Community Meetings for Project Celadon to provide a space to discuss Celadon features and listen to community feedback. Over time, as we continue exploring community interests and involvement, we'll increase the cadence of these meetings. TCMs will typically be held the second week of each month. Some of the technical topics up for discussion span across boot, security, storage, debug, power/performance and more. We'll also be looking to you, the Celadon community, for guidance on additional topics of interest. October TCM Topic: Celadon Security Essentials and Enterprise Usage with Celadon - Learn about platform hardening with Celadon, as well as new security features for Android 10 and Android Enterprise. Download Calendar Invitation: https://drive.google.com/uc?export=download&id=1AKFYg72zk6KbAUKtJoxaM9V4u... View Previous Months Presentations: https://drive.google.com/open?id=1OwaL5-JJWzIljWkVVNeSgf9JzIaVJIOh MEETING DETAILS Asia Pacific Thursday, October 10, 10:30am (India) Thursday, October 10, 1pm (China) North America Wednesday, October 9, 10pm (Pacific Time, USA & Canada) Direct Meeting Link: https://intel.webex.com/meet/sahluwal (Recommended to use Chrome instead of Internet Explorer when joining meeting using a browser) * Chairperson: Yogesh Marathe, mailto:yogesh.marathe@intel.com, Intel * Presenter: Luhai Chen, mailto:luhai.chen@intel.com, Intel * Online conference link: https://intel.webex.com/meet/sahluwal * Access code: 598 858 630 Online conference phone: * US: +1-210-795-1110 or +1-866-662-9987 (Toll Free) * China: +86-400-810-0111 or +86-10-800-712-2435 (Toll Free) * Germany: +49-69-2222-7804 or +49-0800-000-3331 (Toll Free) * India: +91-80-61275208 or +91-000-800-852-1234 (Toll Free) Privacy Notice - http://www.intel.com/privacy Cookies - https://www.intel.com/content/www/us/en/privacy/intel-cookie-notice.html Terms of Use - https://www.intel.com/content/www/us/en/legal/terms-of-use.html Unsubscribe - https://lists.01.org/postorius/lists/celadon.lists.01.org/ Manage Preferences - https://lists.01.org/postorius/lists/celadon.lists.01.org/

1 year

1
0
0 / 0

Project Celadon October Technical Community Meeting

by Mcdonald, Senalka

Join us at the Project Celadon October Technical Community Meeting We recently launched monthly Technical Community Meetings for Project Celadon to provide a space to discuss Celadon features and listen to community feedback. Over time, as we continue exploring community interests and involvement, we'll increase the cadence of these meetings. TCMs will typically be held the second week of each month. Some of the technical topics up for discussion span across boot, security, storage, debug, power/performance and more. We'll also be looking to you, the Celadon community, for guidance on additional topics of interest. October TCM Topic: Celadon Security Essentials and Enterprise Usage with Celadon - Learn about platform hardening with Celadon, as well as new security features for Android 10 and Android Enterprise. Download Calendar Invitation: https://drive.google.com/uc?export=download&id=1AKFYg72zk6KbAUKtJoxaM9V4u... View Previous Months Presentations: https://drive.google.com/open?id=1OwaL5-JJWzIljWkVVNeSgf9JzIaVJIOh MEETING DETAILS Asia Pacific Thursday, October 10, 10:30am (India) Thursday, October 10, 1pm (China) North America Wednesday, October 9, 10pm (Pacific Time, USA & Canada) Direct Meeting Link: https://intel.webex.com/meet/sahluwal (Recommended to use Chrome instead of Internet Explorer when joining meeting using a browser) * Chairperson: Yogesh Marathe, mailto:yogesh.marathe@intel.com, Intel * Presenter: Luhai Chen, mailto:luhai.chen@intel.com, Intel * Online conference link: https://intel.webex.com/meet/sahluwal * Access code: 598 858 630 Online conference phone: * US: +1-210-795-1110 or +1-866-662-9987 (Toll Free) * China: +86-400-810-0111 or +86-10-800-712-2435 (Toll Free) * Germany: +49-69-2222-7804 or +49-0800-000-3331 (Toll Free) * India: +91-80-61275208 or +91-000-800-852-1234 (Toll Free) Privacy Notice - http://www.intel.com/privacy Cookies - https://www.intel.com/content/www/us/en/privacy/intel-cookie-notice.html Terms of Use - https://www.intel.com/content/www/us/en/legal/terms-of-use.html Unsubscribe - https://lists.01.org/postorius/lists/celadon.lists.01.org/ Manage Preferences - https://lists.01.org/postorius/lists/celadon.lists.01.org/

1 year

1
0
0 / 0

Re: Not able to connect to wifi network

by Gaurav Gupta

Jeevaka, To answer your question we cannot see a reason why DhcpClient is getting new IP address. We are running base OS without any changes from our side. How do we debug this? Can you give us any networking or Wifi patch that will generate more logs? Sathish, can you provide Jeevaka exact 'repo sync' command that you used to fetch this OS from github? Thanks On Wed, Sep 25, 2019 at 1:25 PM Badrappan, Jeevaka < jeevaka.badrappan(a)intel.com> wrote: > > > Hi Gaurav, Sathish, > > > > Could you please check why the IP address is getting renewed quite > frequently? (log snippet end of this email) > > > > Is there any change done on top of the celadon code base? > > > > I did verify Wi-fi with latest code base and issue not seen with KBL NUC > which uses the same connectivity module and firmware. > > > > *Synched to Android 9 code base with following commands* > > repo init -u https://github.com/projectceladon/manifest -b > celadon/p/mr0/master -m default.xml > > repo sync > > > > Find the logs captured with the above code base and KBL NUC. > > > > Thanks and Regards, > > Jeevaka > > > > 09-23 17:23:27.769 2938 4323 D DhcpClient: Received packet: > d4:63:c6:61:b4:9a ACK: your new IP /192.168.0.100, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:31.124 2938 4323 D DhcpClient: Received packet: > 6c:56:97:eb:5b:41 ACK: your new IP /192.168.0.104, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:33.632 2938 4323 D DhcpClient: Received packet: > 0c:cb:85:ca:4d:bd ACK: your new IP /192.168.0.102, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:34.807 2938 4323 D DhcpClient: Received packet: > 6c:56:97:eb:5b:41 ACK: your new IP /192.168.0.104, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:38.305 2938 4323 D DhcpClient: Received packet: > 54:e1:ad:e0:39:e4 ACK: your new IP /192.168.0.101, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:38.402 2938 4323 D DhcpClient: Received packet: > 6c:56:97:eb:5b:41 ACK: your new IP /192.168.0.104, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:41.081 2938 4323 D DhcpClient: Received packet: > b0:fc:36:11:56:8b ACK: your new IP /192.168.0.106, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:43.708 2938 4323 D DhcpClient: Received packet: > b0:fc:36:11:56:8b ACK: your new IP /192.168.0.106, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:47.073 2938 4322 D DhcpClient: Unicasting DHCPREQUEST > ciaddr=192.168.0.108 request=0.0.0.0 serverid=null to /192.168.0.1:67 > > 09-23 17:23:47.074 2938 4323 D DhcpClient: Received packet: > 94:c6:91:13:ee:45 ACK: your new IP /192.168.0.108, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:23:47.074 2938 4322 D DhcpClient: Renewed lease: IP address > 192.168.0.108/24 Gateway 192.168.0.1 DNS servers: [ 192.168.0.1 > 192.168.0.1 ] Domains DHCP server /192.168.0.1 Vendor info null lease 60 > seconds > > 09-23 17:23:47.077 2938 4322 D DhcpClient: Scheduling renewal in 29s > > 09-23 17:23:47.077 2938 4322 D DhcpClient: Scheduling rebind in 52s > > 09-23 17:23:47.077 2938 4322 D DhcpClient: Scheduling expiry in 59s > > > > 09-23 17:23:57.876 2938 4323 D DhcpClient: Received packet: > d4:63:c6:61:b4:9a ACK: your new IP /192.168.0.100, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:04.045 2938 4323 D DhcpClient: Received packet: > 0c:cb:85:ca:4d:bd ACK: your new IP /192.168.0.102, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:04.137 2938 4323 D DhcpClient: Received packet: > 54:e1:ad:e0:39:e4 ACK: your new IP /192.168.0.101, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:08.788 2938 4323 D DhcpClient: Received packet: > 6c:56:97:eb:5b:41 ACK: your new IP /192.168.0.104, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:10.419 2938 4323 D DhcpClient: Received packet: > b0:fc:36:11:56:8b ACK: your new IP /192.168.0.106, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:17.076 2938 4322 D DhcpClient: Unicasting DHCPREQUEST > ciaddr=192.168.0.108 request=0.0.0.0 serverid=null to /192.168.0.1:67 > > 09-23 17:24:17.077 2938 4323 D DhcpClient: Received packet: > 94:c6:91:13:ee:45 ACK: your new IP /192.168.0.108, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:17.078 2938 4322 D DhcpClient: Renewed lease: IP address > 192.168.0.108/24 Gateway 192.168.0.1 DNS servers: [ 192.168.0.1 > 192.168.0.1 ] Domains DHCP server /192.168.0.1 Vendor info null lease 60 > seconds > > 09-23 17:24:17.079 2938 4322 D DhcpClient: Scheduling renewal in 29s > > 09-23 17:24:17.079 2938 4322 D DhcpClient: Scheduling rebind in 52s > > 09-23 17:24:17.079 2938 4322 D DhcpClient: Scheduling expiry in 59s > > 09-23 17:24:28.065 2938 4323 D DhcpClient: Received packet: > d4:63:c6:61:b4:9a ACK: your new IP /192.168.0.100, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:29.483 2938 4323 D DhcpClient: Received packet: > 54:e1:ad:e0:39:e4 ACK: your new IP /192.168.0.101, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > > > 09-23 17:24:32.851 3598 3598 D ViewRootImpl[NavigationBar]: > updatePointerIcon called with position out of bounds > > 09-23 17:24:32.957 2938 2949 D WifiService: setWifiEnabled: false > pid=3598, uid=10012, package=com.android.systemui > > > > > > 09-23 17:24:34.397 2938 4323 D DhcpClient: Received packet: > 0c:cb:85:ca:4d:bd ACK: your new IP /192.168.0.102, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:38.635 2938 4323 D DhcpClient: Received packet: > b0:fc:36:11:56:8b ACK: your new IP /192.168.0.106, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:39.229 2938 4323 D DhcpClient: Received packet: > 6c:56:97:eb:5b:41 ACK: your new IP /192.168.0.104, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:47.080 2938 4322 D DhcpClient: Unicasting DHCPREQUEST > ciaddr=192.168.0.108 request=0.0.0.0 serverid=null to /192.168.0.1:67 > > 09-23 17:24:47.081 2938 4323 D DhcpClient: Received packet: > 94:c6:91:13:ee:45 ACK: your new IP /192.168.0.108, netmask /255.255.255.0, > gateways [/192.168.0.1] DNS servers: /192.168.0.1 /192.168.0.1 , lease > time 60 > > 09-23 17:24:47.083 2938 4322 D DhcpClient: Renewed lease: IP address > 192.168.0.108/24 Gateway 192.168.0.1 DNS servers: [ 192.168.0.1 > 192.168.0.1 ] Domains DHCP server /192.168.0.1 Vendor info null lease 60 > seconds > > 09-23 17:24:47.085 2938 4322 D DhcpClient: Scheduling renewal in 29s > > 09-23 17:24:47.085 2938 4322 D DhcpClient: Scheduling rebind in 52s > > 09-23 17:24:47.085 2938 4322 D DhcpClient: Scheduling expiry in 59s > > > > *From:* Gaurav Gupta <gaurav(a)trainingdata.io> > *Sent:* Wednesday, September 25, 2019 11:17 PM > *To:* Sathish <satish.chevuru(a)gmail.com> > *Cc:* Badrappan, Jeevaka <jeevaka.badrappan(a)intel.com> > *Subject:* Re: [01.org Celadon] Not able to connect to wifi network > > > > Jeevaka, can you conclude anything from those logs? > > Wifi is not working for us and it is slowing us down. We need to get this > product out. > > > > > > On Mon, Sep 23, 2019 at 10:26 AM Sathish <satish.chevuru(a)gmail.com> wrote: > > Please find the logs attached. > > > > Thanks, > Sathish > > > > On Mon, Sep 23, 2019 at 9:17 AM Badrappan, Jeevaka < > jeevaka.badrappan(a)intel.com> wrote: > > Hi, > > > I am not able to connect to my wifi network. > > I am seeing the below message in logcat. > > I can see the router has provided a DHCP message with the IP > details, > > but I don't see the IP being assigned to wlan interface. > > > > 09-06 04:02:17.418 3582 5678 D WificondControl: Scan result ready > > event > > 09-06 04:02:17.420 3582 3603 I EthernetTracker: > > interfaceLinkStateChanged, iface: wlan0, up: false > > 09-06 04:02:17.421 3582 3679 D WificondScannerImpl: Filtering out > > 1 scan results. > > 09-06 04:02:17.429 7681 7681 D WifiSettings: > > onAccessPointChanged (singular) callback initiated > > 09-06 04:02:17.431 7681 7681 I chatty : uid=1000(system) > > com.android.settings identical 14 lines > > 09-06 04:02:17.431 7681 7681 D WifiSettings: > > onAccessPointChanged (singular) callback initiated > > 09-06 04:02:17.432 7681 7681 D WifiSettings: > > onAccessPointsChanged (WifiTracker) callback initiated > > 09-06 04:02:22.423 2677 7811 E wifi hal: Out of event poll > > 09-06 04:02:22.423 2677 7811 E wifi hal: Timeout on event socket > > 09-06 04:02:26.279 3582 4450 I WifiService: startScan uid=1000 > > 09-06 04:02:26.285 2677 7811 E wifi hal: Out of event poll > > 09-06 04:02:26.285 2677 7811 D wifi hal: Data on event socket 0 > > 09-06 04:02:26.285 2677 7811 D wifi hal: Drv Event 33 received > > 09-06 04:02:27.844 3582 4877 D DhcpClient: Received packet: > > 54:e1:ad:e0:39:e4 ACK: your new IP /192.168.0.102 <http://192.168.0.102> > , > > netmask /255.255.255.0 <http://255.255.255.0> , gateways [/192.168.0.1 > > <http://192.168.0.1> ] DNS servers: /192.168.0.1 <http://192.168.0.1> > > /192.168.0.1 <http://192.168.0.1> , lease time 60 > > 09-06 04:02:28.174 3582 4877 D DhcpClient: Received packet: > > 0c:cb:85:ca:4d:bd ACK: your new IP /192.168.0.100 <http://192.168.0.100> > , > > netmask /255.255.255.0 <http://255.255.255.0> , gateways [/192.168.0.1 > > <http://192.168.0.1> ] DNS servers: /192.168.0.1 <http://192.168.0.1> > > /192.168.0.1 <http://192.168.0.1> , lease time 60 > > 09-06 04:02:29.617 2677 7811 E wifi hal: Out of event poll > > 09-06 04:02:29.617 2677 7811 D wifi hal: Data on event socket 0 > > 09-06 04:02:29.617 2677 7811 D wifi hal: Drv Event 34 received > > 09-06 04:02:29.617 3582 4450 D WificondControl: Scan result ready > > event > > 09-06 04:02:29.620 3582 3603 I EthernetTracker: > > interfaceLinkStateChanged, iface: wlan0, up: false > > 09-06 04:02:29.628 7681 7681 D WifiSettings: > > onAccessPointChanged (singular) callback initiated > > 09-06 04:02:29.628 7681 7681 I chatty : uid=1000(system) > > com.android.settings identical 14 lines > > 09-06 04:02:29.628 7681 7681 D WifiSettings: > > onAccessPointChanged (singular) callback initiated > > 09-06 04:02:29.628 7681 7681 D WifiSettings: > > onAccessPointsChanged (WifiTracker) callback initiated > > 09-06 04:02:34.622 2677 7811 E wifi hal: Out of event poll > > 09-06 04:02:34.622 2677 7811 E wifi hal: Timeout on event socket > > > > > > my build details are as below: > > [ro.build.characteristics]: [tablet] > > [ro.build.date]: [Wed Aug 21 13:33:22 IST 2019] > > [ro.build.date.utc]: [1566374602] > > [ro.build.description]: [celadon-eng 9 PPR2.181005.003.A1 > > eng.sathis.20190821.133419 test-keys] > > [ro.build.display.id <http://ro.build.display.id> ]: [celadon-eng > 9 > > PPR2.181005.003.A1 eng.sathis.20190821.133419 test-keys] > > [ro.build.fingerprint]: > > [celadon/celadon/celadon:9/PPR2.181005.003.A1/sathish08211333:eng/test- > > keys] > > > > > > > > celadon:/ # ifconfig > > ....... > > wlan0 ....... Driver iwlwifi > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 TX bytes:0 > > > > celadon:/ # > > > > > > Please let me know , if i am missing any configuration changes > > Could you share kernel logs(adb shell dmesg > dmesg) and also complete > aplogs? > > Thanks and Regards, > Jeevaka > > > > > -- > > Gaurav, > > Co-founder & CEO, TrainingData.io > > +1-917-386-3396 > > 228 Webster Street, > Palo Alto, > > CA, 94301 > > > -- Gaurav, Co-founder & CEO, TrainingData.io +1-917-386-3396 228 Webster Street, Palo Alto, CA, 94301

1 year

1
0
0 / 0

Re: [01.org Celadon] Celadon Digest, Vol 17, Issue 18

by Gnanasekaran, Sundar

Hi Tapani, Please try below command from host side: adb tcpip 5555 Thanks, G Sundar -----Original Message----- From: Celadon <celadon-bounces(a)lists.01.org> On Behalf Of celadon-request(a)lists.01.org Sent: Friday, September 27, 2019 12:30 AM To: celadon(a)lists.01.org Subject: Celadon Digest, Vol 17, Issue 18 Send Celadon mailing list submissions to celadon(a)lists.01.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.01.org/mailman/listinfo/celadon or, via email, send a message with subject or body 'help' to celadon-request(a)lists.01.org You can reach the person managing the list at celadon-owner(a)lists.01.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Celadon digest..." Today's Topics: 1. Re: adb over wifi support (Tapani P?lli) ---------------------------------------------------------------------- Message: 1 Date: Thu, 26 Sep 2019 09:46:25 +0300 From: Tapani P?lli <tapani.palli(a)intel.com> To: "Badrappan, Jeevaka" <jeevaka.badrappan(a)intel.com>, Chih-Wei Huang <cwhuang(a)android-x86.org> Cc: "celadon(a)lists.01.org" <celadon(a)lists.01.org> Subject: Re: [01.org Celadon] adb over wifi support Message-ID: <df169abe-483a-7302-2509-30c45748cc6c(a)intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Hi; On 9/24/19 6:32 PM, Badrappan, Jeevaka wrote: >> >> >> On 9/24/19 4:51 AM, Chih-Wei Huang wrote: >>> Badrappan, Jeevaka <jeevaka.badrappan(a)intel.com> ? 2019?9?23? >> ?? >>> ??10:31??? >>>>> Hello; >>>>> After I synced Celadon Q, I noticed adb over wifi does not seem to >>>>> work anymore. When trying to connect, I get 'connection refused'. >>>>> >>>>> Does someone know if there are some build options or perhaps >>>>> modifications to security options to make it work? >>>> >>>> Try the following commands. >>>> >>>> adb shell setprop service.adb.tcp.port 5555 go to CarSetting >>>> developer, re-start usb-debug adb connect <ip>:5555 >>> >>> Have you really tested it? > > Yes tested on KBL NUC commercial device which has adb over usb working. > >>> >>> Actually the property has already been set in current init.*.rc: >>> >>> on boot >>> ... >>> # adb over ethernet >>> setprop service.adb.tcp.port 5555 >>> >>> >>> But it still doesn't work. > Vendor init can't set the system property. So, even if it is set in > service.adb.tcp.port, it won't be set properly. You can confirm that > by querying the property value adb shell getprop > >> >> I tried re-starting usb-debug in 'developer options' to see if it >> matters but it still gives 'connection refused'. I could not do the >> 'adb shell' step command since that requires a working adb connection. > > Could you share the device you are using and also the BIOS version? > My device is KBL NUC, 7i5BNH (bios says 7i5BNB though), BIOS version is: BNKBL357.86A.0040.2017.0210.1749 I don't think BIOS matters though? Adb over wifi works fine with Android Celadon P with this same NUC. // Tapani ------------------------------ Subject: Digest Footer Celadon mailing list Celadon(a)lists.01.org https://lists.01.org/mailman/listinfo/celadon ------------------------------ End of Celadon Digest, Vol 17, Issue 18 ***************************************

1 year

2
2
0 / 0