Hi Stephane.
Thanks for the info, I'll give it a try (on my Windows machine ;) )
By the way, did you try to boot from an NVMe device?
Best regards,
Joel Catala
Director, Engineering
e. joel.catala@xxxxxxxxxx
t. +358 440386111
w. https://www.tuxera.com
-------- Original message --------
From: Stephane Desneux <stephane.desneux@xxxxxxx>
Date: 12/6/19 02:35 (GMT+02:00)
To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [agl-dev-community] AGL HH on H3 + KF
Hi Joel,
As I understand the chapter on https://elinux.org/R-Car/Boards/H3SK#Known_Issues
pointed by Mark, you can fix your H3 by flashing the CPLD with a Windows tool
(#!?*$ ... why Windows?????????? - anyway... I'm sure you have one at hand :)).
This way, you can avoid a board swap on KF.
Also, it would be good to have a confirmation that this procedure solves the
issue on M.2 NVME bus.
Please keep us posted :)
---
Stephane Desneux - CTO - IoT.bzh
stephane.desneux@xxxxxxx - www.iot.bzh
On 05/12/2019 18:34, Joel Catala wrote:
> Hi Mark, Kurokawa-san.
>
> Thank you both for your quick replies.
>
> Iirc my board's serial number is in the range mentioned in the known issue, I'll
> double check on Monday when I get back to it. If indeed the serial number
> matches, it would then explain the issue we face with booting the kernel.
>
> A bit of background, the main reason behind connecting the H3 to the KF was
> exactly to use the m.2 slot (which I believe is what is using the PCIe 1ch) to
> connect an SSD that would contain files that we'd use in our next demo. We can
> do without the SSD, i.e. we could use the onboard eMMC instead.
>
> Next steps:
> - check the serial number and apply changes to the dtb file to work around the issue
> - verify the kernel boots with the modified correct dtb
> - find another H3 that doesn't have this issue
>
> Thanks again for your support.
>
> Best regards,
> Joel Catala
> Director, Engineering
> Tuxera
>
>
> -------- Original message --------
> From: "Silberberger, Mark (CQTM)" <mark.silberberger@xxxxxxxxxx>
> Date: 12/5/19 13:38 (GMT+02:00)
> To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [agl-dev-community] AGL HH on H3 + KF
>
> Hi Joel,
>
>
>
> as Kurokawa-san pointed out, the r8a7795-h3ulcb-4x2g-kf.dtb should be the right
> Device Tree for your configuration.
>
>
>
> Adding to Kurokawa-san’s comments, I’d like to point you to the Known Issues
> listed for the H3 SK on eLinux: https://elinux.org/R-Car/Boards/H3SK#Known_Issues
>
> If you have a Starter Kit in the given Serial Number ranges, the Linux kernel
> will get stuck when processing the pciec1 node in the Device Tree due to PCIe
> 1ch being disabled on the board.
>
> To work around it, you could disable the pciec1 node in the Device Tree, which
> should fix the boot issue. However, I’m not sure if all your peripherals will
> work under that configuration.
>
>
>
> Best regards,
>
> Mark
>
>
>
> *--*
>
> * *
>
> *Mark Silberberger*
> Business Team Vernetztes Infotainment
>
>
>
> *Carmeq GmbH*
> Carnotstr. 4
> D-10587 Berlin
>
>
>
> Mobile: +49.172.8247992
>
> Fax: +49.30.3983 537-199
>
> E-Mail: mark.silberberger@xxxxxxxxxx <mailto:mark.silberberger@xxxxxxxxxx>
> Internet: www.carmeq.com <http://www.carmeq.com/>
>
>
>
> Carmeq GmbH, Sitz / Domicile: Berlin, Registergericht / Court of Registry:
> Amtsgericht Berlin-Charlottenburg, HRB Nr./ Commercial Register No.: 86104 B,
> Geschäftsführer / Management Board: Dr. Stefan E. Ortmann (Sprecher/ Chairman),
> Karl Sempf
>
>
>
> _Wichtiger Hinweis:_Die vorgenannten Angaben werden jeder E-Mail automatisch
> hinzugefügt und lassen keine Rückschlüsse auf den Rechtscharakter der E-Mail zu.
>
> _Important Notice:_The above information is automatically added to this e-mail.
> This addition does not constitute a representation that the content of this
> e-mail is legally relevant and/or intended to be legally binding upon Carmeq GmbH.
>
>
>
> Diese E-Mail und etwaige Anlagen können Geschäftsgeheimnisse oder sonstige
> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
> erhalten haben, ist Ihnen dieser Umstand hiermit bekannt. Bitte benachrichtigen
> Sie in diesem Fall umgehend den Absender und löschen Sie diese E-Mail
> einschließlich etwaiger Anlagen auf irreversible Art und Weise von Ihrem System.
> Diese E-Mail und etwaige Anlagen dürfen im Fall der irrtümlichen Adressierung
> auch nicht kopiert, an Dritte weitergegeben oder anderweitig missbräuchlich
> verwendet werden. Vielen Dank!
>
>
>
> This email could contain confidential or privileged material. Therefore, the
> information transmitted by this email is intended only for specific persons or
> entities. If you received this email as a result of an error, please contact the
> sender immediately and delete the email from your system irreversibly. In this
> case, any copying, dissemination, retransmission, review, or other use of this
> email is strictly prohibited. Thank you very much!
>
>
>
> *Von:* agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx> *Im Auftrag von *kurokawa
> *Gesendet:* Donnerstag, 5. Dezember 2019 11:41
> *An:* agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> *Betreff:* Re: [agl-dev-community] AGL HH on H3 + KF
>
>
>
> Hi Joel
>
>
>
>>H3 Starter Kit RTP0RC77951SKBX010SA03 (LPDDR4: DDR 8GiB(Samsung 2GB x4), eMMC
> 32GB(SanDisk))
>
> Regarding this ID, you should use “r8a7795-h3ulcb-4x2g-kf.dtb. for Kingfisher.
>
> DO NOT use another *-kf.dtb file. (especially, es1-h3ulcb-kf is for old revision SK.
>
> Addition, if you set “r8a7795-h3ulcb-4x2g.dtb”, it will boot only Starter Kit,
> (stand alone),
>
>
>
> https://elinux.org/R-Car/Boards/H3SK#Booting_Linux
>
>
>
>
>
>>Using the r8a7795-h3ulcb-4x2g-kf.dtb, the kernel does not even start.
>
> One idea, please disconnect any device if you insert ? (USB, HDMI, M.2, etc).
>
>
>
> Best regards,
>
> Kurokawa.
>
>
>
> *From:*agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>
> <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>> *On Behalf Of *Joel Catala
> via Lists.Automotivelinux.Org
> *Sent:* Thursday, December 5, 2019 7:10 PM
> *To:* agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>
> *Subject:* [agl-dev-community] AGL HH on H3 + KF
>
>
>
> Hi all.
>
>
>
> Could someone please advise if there is a profile to automatically build HH for
> the H3 + Kingfisher? Using aglsetup.sh -hI cannot see any.
>
>
>
> Building the h3ulcbsucceeds and it boots correctly with the H3 connected to the
> KF (using the r8a7795-es1-h3ulcb-kf.dtbfile) , however some “peripherals” (e.g.
> NVMe SSD on the m.2 slot) do not get detected)
>
> Using the r8a7795-es1-h3ulcb-kf.dtb, booting the kernel was working, however the
> sd card mmcblk device is not present so it hangs waiting for root device.
>
> Using the r8a7795-h3ulcb-4x2g-kf.dtb, the kernel does not even start.
>
>
>
> Environment details:
>
> H3 Starter Kit RTP0RC77951SKBX010SA03 (LPDDR4: DDR 8GiB(Samsung 2GB x4), eMMC
> 32GB(SanDisk))
>
> Kingfisher Advanced M04
>
>
>
> aglsetup.manifest
>
>
>
> # ----------------------------------------------
>
> # This fragment has been generated by aglsetup.sh at setup time
>
>
>
> # distro name
>
> DIST_DISTRO_NAME="AGL"
>
>
>
> # target machine as passed to aglsetup.sh
>
> DIST_MACHINE="h3ulcb"
>
>
>
> # features as resolved by aglsetup.sh
>
> DIST_FEATURES="agl-appfw-smack agl-demo agl-devel agl-hmi-framework agl-pipewire
> agl-profile-graphical agl-profile-graphical-qt5 agl-speech-framework "
>
> DIST_FEATURES_MD5="1fc52838eac52fecb708b86f510e86c3"
>
>
>
> # build host information deduced from os-release
>
> DIST_BUILD_HOST="joel@xxxxxxxxxxxxxxxxxxxxxx <mailto:joel@xxxxxxxxxxxxxxxxxxxxxx>"
>
> DIST_BUILD_OS="Debian GNU/Linux 9 (stretch)"
>
>
>
> # meta directory
>
> DIST_METADIR="/opt/workdir2/agl/hh-h3"
>
>
>
> # timestamp
>
> DIST_SETUP_TS="20191204_113959_UTC"
>
>
>
> # topic
>
> DIST_SETUP_TOPIC=""
>
>
>
> # ------------ end of aglsetup.sh fragment --------
>
>
>
> Build Configuration:
>
> BB_VERSION = "1.40.0"
>
> BUILD_SYS = "x86_64-linux"
>
> NATIVELSBSTRING = "universal"
>
> TARGET_SYS = "aarch64-agl-linux"
>
> MACHINE = "h3ulcb"
>
> DISTRO = "poky-agl"
>
> DISTRO_VERSION = "8.0.3+snapshot-20191205"
>
> TUNE_FEATURES = "aarch64"
>
> TARGET_FPU = ""
>
> SOC_FAMILY = "rcar-gen3:r8a7795"
>
> meta-rcar-gen3 = "HEAD:eaa14f800190abdfd644cedc0945fbbf63d0776d"
>
> meta-rcar-gen3-adas = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta-qt5 = "HEAD:1520d5b2b2beec5e1c3209d3178219e93ef08bca"
>
> meta-agl-profile-graphical-qt5
>
> meta-agl-profile-graphical = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta-speech-framework
>
> meta-pipewire = "HEAD:b11689975e94c57b7a3f835fd9cf34320015e20c"
>
> meta-agl-demo = "HEAD:b18b813c543556544e54c41c541fd121fb002378"
>
> meta-oe
>
> meta-multimedia
>
> meta-networking
>
> meta-python
>
> meta-filesystems = "HEAD:446bd615fd7cb9bc7a159fe5c2019ed08d1a7a93"
>
> meta-agl-profile-core
>
> meta-agl-distro
>
> meta-agl-bsp = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta-security = "HEAD:31dc4e7532fa7a82060e0b50e5eb8d0414aa7e93"
>
> meta-perl = "HEAD:446bd615fd7cb9bc7a159fe5c2019ed08d1a7a93"
>
> meta-security
>
> meta-app-framework = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta
>
> meta-poky = "HEAD:51f6145f8f99a02df1dad937684f014b0172e72a"
>
>
>
>
>
> Does anyone have an idea what the problem could be?
>
>
>
> Best regards,
>
> *Joel Catala*
>
> Director, Engineering
>
> Tuxera
>
>
>
>
As I understand the chapter on https://elinux.org/R-Car/Boards/H3SK#Known_Issues
pointed by Mark, you can fix your H3 by flashing the CPLD with a Windows tool
(#!?*$ ... why Windows?????????? - anyway... I'm sure you have one at hand :)).
This way, you can avoid a board swap on KF.
Also, it would be good to have a confirmation that this procedure solves the
issue on M.2 NVME bus.
Please keep us posted :)
---
Stephane Desneux - CTO - IoT.bzh
stephane.desneux@xxxxxxx - www.iot.bzh
On 05/12/2019 18:34, Joel Catala wrote:
> Hi Mark, Kurokawa-san.
>
> Thank you both for your quick replies.
>
> Iirc my board's serial number is in the range mentioned in the known issue, I'll
> double check on Monday when I get back to it. If indeed the serial number
> matches, it would then explain the issue we face with booting the kernel.
>
> A bit of background, the main reason behind connecting the H3 to the KF was
> exactly to use the m.2 slot (which I believe is what is using the PCIe 1ch) to
> connect an SSD that would contain files that we'd use in our next demo. We can
> do without the SSD, i.e. we could use the onboard eMMC instead.
>
> Next steps:
> - check the serial number and apply changes to the dtb file to work around the issue
> - verify the kernel boots with the modified correct dtb
> - find another H3 that doesn't have this issue
>
> Thanks again for your support.
>
> Best regards,
> Joel Catala
> Director, Engineering
> Tuxera
>
>
> -------- Original message --------
> From: "Silberberger, Mark (CQTM)" <mark.silberberger@xxxxxxxxxx>
> Date: 12/5/19 13:38 (GMT+02:00)
> To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [agl-dev-community] AGL HH on H3 + KF
>
> Hi Joel,
>
>
>
> as Kurokawa-san pointed out, the r8a7795-h3ulcb-4x2g-kf.dtb should be the right
> Device Tree for your configuration.
>
>
>
> Adding to Kurokawa-san’s comments, I’d like to point you to the Known Issues
> listed for the H3 SK on eLinux: https://elinux.org/R-Car/Boards/H3SK#Known_Issues
>
> If you have a Starter Kit in the given Serial Number ranges, the Linux kernel
> will get stuck when processing the pciec1 node in the Device Tree due to PCIe
> 1ch being disabled on the board.
>
> To work around it, you could disable the pciec1 node in the Device Tree, which
> should fix the boot issue. However, I’m not sure if all your peripherals will
> work under that configuration.
>
>
>
> Best regards,
>
> Mark
>
>
>
> *--*
>
> * *
>
> *Mark Silberberger*
> Business Team Vernetztes Infotainment
>
>
>
> *Carmeq GmbH*
> Carnotstr. 4
> D-10587 Berlin
>
>
>
> Mobile: +49.172.8247992
>
> Fax: +49.30.3983 537-199
>
> E-Mail: mark.silberberger@xxxxxxxxxx <mailto:mark.silberberger@xxxxxxxxxx>
> Internet: www.carmeq.com <http://www.carmeq.com/>
>
>
>
> Carmeq GmbH, Sitz / Domicile: Berlin, Registergericht / Court of Registry:
> Amtsgericht Berlin-Charlottenburg, HRB Nr./ Commercial Register No.: 86104 B,
> Geschäftsführer / Management Board: Dr. Stefan E. Ortmann (Sprecher/ Chairman),
> Karl Sempf
>
>
>
> _Wichtiger Hinweis:_Die vorgenannten Angaben werden jeder E-Mail automatisch
> hinzugefügt und lassen keine Rückschlüsse auf den Rechtscharakter der E-Mail zu.
>
> _Important Notice:_The above information is automatically added to this e-mail.
> This addition does not constitute a representation that the content of this
> e-mail is legally relevant and/or intended to be legally binding upon Carmeq GmbH.
>
>
>
> Diese E-Mail und etwaige Anlagen können Geschäftsgeheimnisse oder sonstige
> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
> erhalten haben, ist Ihnen dieser Umstand hiermit bekannt. Bitte benachrichtigen
> Sie in diesem Fall umgehend den Absender und löschen Sie diese E-Mail
> einschließlich etwaiger Anlagen auf irreversible Art und Weise von Ihrem System.
> Diese E-Mail und etwaige Anlagen dürfen im Fall der irrtümlichen Adressierung
> auch nicht kopiert, an Dritte weitergegeben oder anderweitig missbräuchlich
> verwendet werden. Vielen Dank!
>
>
>
> This email could contain confidential or privileged material. Therefore, the
> information transmitted by this email is intended only for specific persons or
> entities. If you received this email as a result of an error, please contact the
> sender immediately and delete the email from your system irreversibly. In this
> case, any copying, dissemination, retransmission, review, or other use of this
> email is strictly prohibited. Thank you very much!
>
>
>
> *Von:* agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx> *Im Auftrag von *kurokawa
> *Gesendet:* Donnerstag, 5. Dezember 2019 11:41
> *An:* agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> *Betreff:* Re: [agl-dev-community] AGL HH on H3 + KF
>
>
>
> Hi Joel
>
>
>
>>H3 Starter Kit RTP0RC77951SKBX010SA03 (LPDDR4: DDR 8GiB(Samsung 2GB x4), eMMC
> 32GB(SanDisk))
>
> Regarding this ID, you should use “r8a7795-h3ulcb-4x2g-kf.dtb. for Kingfisher.
>
> DO NOT use another *-kf.dtb file. (especially, es1-h3ulcb-kf is for old revision SK.
>
> Addition, if you set “r8a7795-h3ulcb-4x2g.dtb”, it will boot only Starter Kit,
> (stand alone),
>
>
>
> https://elinux.org/R-Car/Boards/H3SK#Booting_Linux
>
>
>
>
>
>>Using the r8a7795-h3ulcb-4x2g-kf.dtb, the kernel does not even start.
>
> One idea, please disconnect any device if you insert ? (USB, HDMI, M.2, etc).
>
>
>
> Best regards,
>
> Kurokawa.
>
>
>
> *From:*agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>
> <agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>> *On Behalf Of *Joel Catala
> via Lists.Automotivelinux.Org
> *Sent:* Thursday, December 5, 2019 7:10 PM
> *To:* agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx>
> *Subject:* [agl-dev-community] AGL HH on H3 + KF
>
>
>
> Hi all.
>
>
>
> Could someone please advise if there is a profile to automatically build HH for
> the H3 + Kingfisher? Using aglsetup.sh -hI cannot see any.
>
>
>
> Building the h3ulcbsucceeds and it boots correctly with the H3 connected to the
> KF (using the r8a7795-es1-h3ulcb-kf.dtbfile) , however some “peripherals” (e.g.
> NVMe SSD on the m.2 slot) do not get detected)
>
> Using the r8a7795-es1-h3ulcb-kf.dtb, booting the kernel was working, however the
> sd card mmcblk device is not present so it hangs waiting for root device.
>
> Using the r8a7795-h3ulcb-4x2g-kf.dtb, the kernel does not even start.
>
>
>
> Environment details:
>
> H3 Starter Kit RTP0RC77951SKBX010SA03 (LPDDR4: DDR 8GiB(Samsung 2GB x4), eMMC
> 32GB(SanDisk))
>
> Kingfisher Advanced M04
>
>
>
> aglsetup.manifest
>
>
>
> # ----------------------------------------------
>
> # This fragment has been generated by aglsetup.sh at setup time
>
>
>
> # distro name
>
> DIST_DISTRO_NAME="AGL"
>
>
>
> # target machine as passed to aglsetup.sh
>
> DIST_MACHINE="h3ulcb"
>
>
>
> # features as resolved by aglsetup.sh
>
> DIST_FEATURES="agl-appfw-smack agl-demo agl-devel agl-hmi-framework agl-pipewire
> agl-profile-graphical agl-profile-graphical-qt5 agl-speech-framework "
>
> DIST_FEATURES_MD5="1fc52838eac52fecb708b86f510e86c3"
>
>
>
> # build host information deduced from os-release
>
> DIST_BUILD_HOST="joel@xxxxxxxxxxxxxxxxxxxxxx <mailto:joel@xxxxxxxxxxxxxxxxxxxxxx>"
>
> DIST_BUILD_OS="Debian GNU/Linux 9 (stretch)"
>
>
>
> # meta directory
>
> DIST_METADIR="/opt/workdir2/agl/hh-h3"
>
>
>
> # timestamp
>
> DIST_SETUP_TS="20191204_113959_UTC"
>
>
>
> # topic
>
> DIST_SETUP_TOPIC=""
>
>
>
> # ------------ end of aglsetup.sh fragment --------
>
>
>
> Build Configuration:
>
> BB_VERSION = "1.40.0"
>
> BUILD_SYS = "x86_64-linux"
>
> NATIVELSBSTRING = "universal"
>
> TARGET_SYS = "aarch64-agl-linux"
>
> MACHINE = "h3ulcb"
>
> DISTRO = "poky-agl"
>
> DISTRO_VERSION = "8.0.3+snapshot-20191205"
>
> TUNE_FEATURES = "aarch64"
>
> TARGET_FPU = ""
>
> SOC_FAMILY = "rcar-gen3:r8a7795"
>
> meta-rcar-gen3 = "HEAD:eaa14f800190abdfd644cedc0945fbbf63d0776d"
>
> meta-rcar-gen3-adas = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta-qt5 = "HEAD:1520d5b2b2beec5e1c3209d3178219e93ef08bca"
>
> meta-agl-profile-graphical-qt5
>
> meta-agl-profile-graphical = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta-speech-framework
>
> meta-pipewire = "HEAD:b11689975e94c57b7a3f835fd9cf34320015e20c"
>
> meta-agl-demo = "HEAD:b18b813c543556544e54c41c541fd121fb002378"
>
> meta-oe
>
> meta-multimedia
>
> meta-networking
>
> meta-python
>
> meta-filesystems = "HEAD:446bd615fd7cb9bc7a159fe5c2019ed08d1a7a93"
>
> meta-agl-profile-core
>
> meta-agl-distro
>
> meta-agl-bsp = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta-security = "HEAD:31dc4e7532fa7a82060e0b50e5eb8d0414aa7e93"
>
> meta-perl = "HEAD:446bd615fd7cb9bc7a159fe5c2019ed08d1a7a93"
>
> meta-security
>
> meta-app-framework = "HEAD:5bc68d6ef8dd67d0690688400dc37f896e58ab7f"
>
> meta
>
> meta-poky = "HEAD:51f6145f8f99a02df1dad937684f014b0172e72a"
>
>
>
>
>
> Does anyone have an idea what the problem could be?
>
>
>
> Best regards,
>
> *Joel Catala*
>
> Director, Engineering
>
> Tuxera
>
>
>
>
_._,_._,_
Links:
You receive all messages sent to this group.
View/Reply Online (#7886) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
_._,_._,_
