Todos: Paz mundial
Hector Almeida
Hola,
Acabo de firmar la petición de "Todos: Paz mundial" y me encantaría que me ayudaras sumando tu firma. Nuestro objetivo es llegar a 100 firmas y necesitamos más apoyo. Para obtener más información y firmar la petición puedes abrir el siguiente link: http://chng.it/WNzDXSnxMd ¡Gracias! Héctor
|
||||||||||||||
|
||||||||||||||
AM/FM Tuner module interface with imx8m-mini
Malay Dhrangadhria
Hello, I am a little bit new to yocto, I am looking for some help/reference link for simple-card driver integration for FM tuner chip to get audio data to the iMX8m-mini board through the I2S interface. I searched for some references through the internet but no success there. Please help me with the same. Waiting for your positive response. -- Regards, Malay Dhrangadhria Senior Software Engineer | +91 784 306 7258 Great Software Laboratory | www.gslab.com Confidentiality Notice and Disclaimer: This email (including any attachments) contains information that may be confidential, privileged and/or copyrighted. If you are not the intended recipient, please notify the sender immediately and destroy this email. Any unauthorized use of the contents of this email in any manner whatsoever, is strictly prohibited. If improper activity is suspected, all available information may be used by the sender for possible disciplinary action, prosecution, civil claim or any remedy or lawful purpose. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, lost, arrive late, or contain viruses. The sender is not liable whatsoever for damage resulting from the opening of this message and/or the use of the information contained in this message and/or attachments. Expressions in this email cannot be treated as opined by the sender company management – they are solely expressed by the sender unless authorized.
|
||||||||||||||
|
||||||||||||||
Does OE / Yocto support dts file remove device node /delete-node/?
JH
Hi,
I have a following statement to remove a node in a DTS file: &gpmi { /delete-node/ fsl,use-minimum-ecc; }; I can build it correctly in OpenWRT build, but I cannot built it correctly in OE / Yocto (Zeus), it did not remove the node fsl,use-minimum-ecc. The u-boot is appended from meta-freescale u-boot-imx_2018.03.bb. Any workarounds to fix that problem? Thank you. Kind regards, - jh -- "A man can fail many times, but he isn't a failure until he begins to blame somebody else." -- John Burroughs
|
||||||||||||||
|
||||||||||||||
Re: [EXT] [meta-freescale] ls1043a without optee
Ting Liu
Hello,
Please refer to LSDK document – Chapter 5 bootloader which include some detailed information about TF-A and u-boot.
You can also submit question to NXP community.
-Ting
From: meta-freescale@... <meta-freescale@...>
On Behalf Of Stevenvb via lists.yoctoproject.org
Sent: Wednesday, May 20, 2020 4:09 PM To: meta-freescale@... Subject: [EXT] [meta-freescale] ls1043a without optee
Caution: EXT Email hello all,
I am trying to boot ls1043a without optee. I managed to compile and run atf until it jumps to uboot. There i do not get any serial output anymore.
INFO: Loading image id=5 at address 0x82000000
My question is, what do i need to change in uboot config? And what are possible causes for this?
If this is the wrong mailing list for this question, is there another more correct one or a irc channel?
|
||||||||||||||
|
||||||||||||||
ls1043a without optee
Stevenvb
hello all, I am trying to boot ls1043a without optee. I managed to compile and run atf until it jumps to uboot. There i do not get any serial output anymore. INFO: Loading image id=5 at address 0x82000000 INFO: sd-mmc read done. INFO: Image id=5 loaded: 0x82000000 - 0x820afbc3 NOTICE: BL2: Booting BL31 INFO: Entry point address = 0xbbe00000 NOTICE: BL31: v1.5(release):devtool-patched-dirty NOTICE: BL31: Built : 08:19:07, May 13 2020 NOTICE: Welcome to ls1043ardb BL31 Phase INFO: ARM GICv2 driver initialized INFO: BL31: Initializing runtime services INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x82000000 INFO: SPSR = 0x3c9 My question is, what do i need to change in uboot config? And what are possible causes for this? If this is the wrong mailing list for this question, is there another more correct one or a irc channel?
|
||||||||||||||
|
||||||||||||||
Re: linux-imx-headers missing in SDK
Otavio Salvador
On Mon, May 18, 2020 at 5:49 AM Carlos Rafael Giani <crg7475@mailbox.org> wrote:
when I generate a SDK (for example by running MACHINE=imx8mmevk bitbakeIt is not. Please open a issue. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
|
||||||||||||||
|
||||||||||||||
linux-imx-headers missing in SDK
Carlos Rafael Giani
Hi,
when I generate a SDK (for example by running MACHINE=imx8mmevk bitbake -c populate_sdk core-image-weston), I notice that the headers from linux-imx-headers are missing even though linux-imx-headers is a dependency of various included packages. Is this a known issue?
|
||||||||||||||
|
||||||||||||||
i.MX28 custom board ethernet link toggling up and down
Pavithra R
Hi Team, We are using a Custom imx28-evk based board with the latest iMX yocto images (Zeus) ported into it. Linux version 5.4.20-fslc+g18d5e274c780. The problem is when the board boots up we keep on getting prints from Ethernet driver like this:- Configuring network interfaces... [ 15.759903] SMSC LAN8710/LAN8720 800f0000.ethernet-1:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=800f0000.ethernet-1:00, irq=POLL) udhcpc: started, v1.31.0 udhcpc: sending discover [ 17.871399] fec 800f0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 18.940173] fec 800f0000.ethernet eth0: Link is Down udhcpc: sending discover [ 19.949639] fec 800f0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 21.019241] fec 800f0000.ethernet eth0: Link is Down [ 22.029599] fec 800f0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off udhcpc: sending discover [ 23.099242] fec 800f0000.ethernet eth0: Link is Down [ 24.109620] fec 800f0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 25.180685] fec 800f0000.ethernet eth0: Link is Down Board never gets assigned any IP. This prints goes on forever. Ethernet works fine in bootloader. We are able to do TFTP from u-boot. Also in the kernel everything works fine with static ip configuration with a PC. There are no errors in packet reception. output of ifconfig eth0 Link encap:Ethernet HWaddr 00:04:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:66 (66.0 B) TX bytes:5130 (5.0 KiB) We have seen that exact issue listed in a forum https://patchwork.ozlabs.org/project/netdev/patch/20151127120919.66f2bfda@.../ But this was a five year old post and seems like the mentioned patch is not relevant at all. Our device tree contents are <arch/arm/boot/dts/imx28.dtsi> mac0: ethernet@800f0000 { compatible = "fsl,imx28-fec"; reg = <0x800f0000 0x4000>; interrupts = <101>; clocks = <&clks 57>, <&clks 57>, <&clks 64>; clock-names = "ipg", "ahb", "enet_out"; status = "disabled"; }; <arch/arm/boot/dts/imx28-evk.dts> mac0: ethernet@800f0000 { phy-mode = "rmii"; pinctrl-names = "default"; pinctrl-0 = <&mac0_pins_a>; phy-supply = <®_fec_3v3>; phy-reset-gpios = <&gpio1 11 GPIO_ACTIVE_LOW>; phy-reset-duration = <1000>; status = "okay"; }; Note: when we manually set the link speed to 10mbps using ethtool, Ethernet works fine.This issue occurs with 100mbps speed and it seems to have some issue with autonegotiation. Please consider this issue in priority and help to resolve this issue at the earliest. Regards,
|
||||||||||||||
|
||||||||||||||
Opal 5 (i.MX53) SD card boot fail
Bill Randle <bill.randle@...>
I have an Opal 5 SOM and DevKit which is based on the i.MX53 ARD reference design, and am trying to get it to boot via the SD card. I'm using Yocto 3.1 (Dunfell) and meta-freescale (current). My custom machine file is a copy of the imx53ard.conf with WiFi support deleted and some other tools added in. After running 'bitbake core-image-sato' I have:
core-image-sato-imx53rover-20200503193936.rootfs.wic.gz core-image-sato-imx53rover-20200503193936.rootfs.wic.bmap I uncompressed the gz file and wrote it to the SD card with bmaptool. The system does not boot and there are no messages on the debug console USB serial port (which means U-boot didn't load). The hardware is good as it will boot the Windows CE image in NAND flash. Yes, I did change the boot config switches to select boot from SD. My questions are: 1. The last embedded project I did several years ago needed a SPL loaded on the SD card. I noticed some imx u-boot configs use the imx-uboot-spl-bootpart.wks.in, but the imx53* ones use the default imx-uboot-bootpart.wks.in script. Will the internal i.MX53 firmware load U-boot directly without the need for the SPL? 2. Does anyone who has used the i.MX53 have any suggestions on how to debug this, being as I see nothing on the console? If saw something/anything from u-boot, I would have a starting point and would know how to proceed. This is obviously an old board, as nobody makes i.MX53 dev kits anymore (at least ones that support NAND flash). The board vendor had contracted with a third party (TrygTech) to provide Linux support. I did try to contact them via both email and phone, but have received no response to date. -Bill
|
||||||||||||||
|
||||||||||||||
Which recipe u-boot-fslc-fw-utils or u-boot-fw-utils to install u-boot-fw-utils package for iMX6ULL?
JH
Hi,
I want to use fw_printenv/setenv utilities on iMX6ULL Linux, the u-boot version is different between meta-freescale and oe-core, meta-freescale uses u-boot-imx_2018.03.bb and u-boot-fslc-fw-utils_2019.07.bb, the oe-core uses u-boot_2019.07.bb and u-boot-fw-utils_2019.07.bb. I think I need to use meta-freescale not oe-core, but if I add u-boot-fslc-fw-utils to my package build, it got many errors, is it a right recipe name for the u-boot-fw-utils package? Thank you. Kind regards, Jupiter -- "A man can fail many times, but he isn't a failure until he begins to blame somebody else." -- John Burroughs
|
||||||||||||||
|
||||||||||||||
Re: a bug of perf
leimaohui
OK, thank you for your reply.
toggle quoted messageShow quoted text
Best regards Lei
-----Original Message-----
|
||||||||||||||
|
||||||||||||||
Re: a bug of perf
Zhenhua Luo
Sure, it would be helpful if you can submit the patch.
toggle quoted messageShow quoted text
Best Regards, Zhenhua
-----Original Message-----
|
||||||||||||||
|
||||||||||||||
Re: a bug of perf
leimaohui
Hi,
toggle quoted messageShow quoted text
So, may I backport this patch to linux-qoriq_5.4.bb and send a PR? Best regards Lei Maohui
-----Original Message-----
|
||||||||||||||
|
||||||||||||||
Re: a bug of perf
Otavio Salvador
Zhenhua,
toggle quoted messageShow quoted text
June is too late; you need to send the fix soon or we should drop dunfell release for QorIQ.
On Mon, Apr 27, 2020 at 9:55 AM Zhenhua Luo <zhenhua.luo@nxp.com> wrote:
The new QorIQ SDK based on Zeus is being prepared and plan to be available in June, we will port the perf patch in this release. --
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
|
||||||||||||||
|
||||||||||||||
Re: a bug of perf
Zhenhua Luo
The new QorIQ SDK based on Zeus is being prepared and plan to be available in June, we will port the perf patch in this release.
toggle quoted messageShow quoted text
Best Regards, Zhenhua
-----Original Message-----
|
||||||||||||||
|
||||||||||||||
Re: a bug of perf
Andrey Zhizhikin
On Mon, Apr 27, 2020 at 8:54 AM leimaohui <leimaohui@cn.fujitsu.com> wrote:
I have this patch ported to linux-imx kernel [1], probably you should do the same for linux-qoriq. Try to add it into the recipe and if it would work out - send a PR. [1]: https://github.com/Freescale/meta-freescale/blob/master/recipes-kernel/linux/linux-imx-5.4.3/0001-perf-Make-perf-able-to-build-with-latest-libbfd.patch -- Regards, Andrey.
|
||||||||||||||
|
||||||||||||||
a bug of perf
leimaohui
Hi,
I met perf bug by meta-freescale as following: --------------------------------------------------------------------- tmp/work/armv8-linux/perf/1.0-r9/perf-1.0/perf-in.o: in function `find_address_in_section': | /usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/util/srcline.c:200: undefined reference to `bfd_get_section_flags' perf/1.0-r9/recipe-sysroot-native/usr/bin/aarch64-linux/../../libexec/aarch64-linux/gcc/aarch64-linux/9.3.0/ld: /usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/util/srcline.c:204: undefined reference to `bfd_get_section_vma' I found that this bug has been fixed in upstream: --------------------------------------------------------------------- commit f4d7dbafb103e4f782323017c239c548871c1567 Author: Changbin Du <changbin.du@gmail.com> Date: Tue Jan 28 23:29:38 2020 +0800 perf: Make perf able to build with latest libbfd libbfd has changed the bfd_section_* macros to inline functions bfd_section_<field> since 2019-09-18. See below two commits: o http://www.sourceware.org/ml/gdb-cvs/2019-09/msg00064.html o https://www.sourceware.org/ml/gdb-cvs/2019-09/msg00072.html This fix make perf able to build with both old and new libbfd. Signed-off-by: Changbin Du <changbin.du@gmail.com> Acked-by: Jiri Olsa <jolsa@redhat.com> Cc: Peter Zijlstra <peterz@infradead.org> Link: http://lore.kernel.org/lkml/20200128152938.31413-1-changbin.du@gmail.com Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> tools/perf/util/srcline.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) I want to know when linux-qoriq will be updated next time? Best regards Lei Maohui
|
||||||||||||||
|
||||||||||||||
Re: nitrogen6x machine config and imxpxp problems
Gary Bisson
Hi Carlos,
On Fri, Apr 24, 2020 at 09:41:26AM +0200, Carlos Rafael Giani wrote: Two problems actually.Sure, that has been acceptable to us as as most customer don't use PxP on i.MX6 but prefer GPU2D/3D features. Second, libimxdmabuffer's PxP allocator is enabled. This allocator is thenHow did that work on GStreamer-imx before? Because this issue has been there all along. Was there a runtime check to enable/disable features? (I don't recall) I could change libimxdmabuffer's test-alloc to report success if at leastI know the "build" has to be deterministic but is there "runtime" recommendations from Yocto? Regards, Gary
|
||||||||||||||
|
||||||||||||||
Re: nitrogen6x machine config and imxpxp problems
Carlos Rafael Giani
Two problems actually.
toggle quoted messageShow quoted text
First, gstreamer1.0-plugins-imx has its PxP plugin enabled. Second, libimxdmabuffer's PxP allocator is enabled. This allocator is then tested for in the test-alloc program. This program is what's used by libimxdmabuffer's ptest. test-alloc then detects a failure while trying to use the PxP allocator (of course, since PxP is not actually present), causing test-alloc to report a failure. I could change libimxdmabuffer's test-alloc to report success if at least one tested allocator works, but I'm not sure if this is really the right way to go. This would pave the way for run-time checks that enable/disable features. From what I know, this kind of thing isn't considered good practice in Yocto, since it tends to make builds less deterministic. Carlos
On 24.04.20 09:29, Gary Bisson wrote:
Hi Carlos,
|
||||||||||||||
|
||||||||||||||
Re: nitrogen6x machine config and imxpxp problems
Gary Bisson
Hi Carlos,
On Fri, Apr 24, 2020 at 08:59:34AM +0200, Carlos Rafael Giani wrote: The nitrogen6x machine config also supports other machines according to theWell the board itself (Nitrogen6x) is the same, only the CPU populated changed (pin-to-pin compatible) so it made sense not to separate the machine. Then as the commit from Eric explained [1], the main reason was for the firmware-imx vpu files, without "mx6dl" it wouldn't install the matching firmware. This isn't ideal but has worked for the past 6 years, so I'm not sure what is the ptest packages error, can you copy it here? I now wonder what to do here. Split nitrogen6x.conf into multiple individualAt this stage of the product (entering legacy) we do not plan on splitting its machine. Also want to point out that even NXP SABRE SD machine does the same thing [2] so I doubt the solution is splitting it or removing an override. Regards, Gary [1] https://github.com/Freescale/meta-freescale-3rdparty/commit/9d34fea1 [2] https://github.com/Freescale/meta-freescale/blob/zeus/conf/machine/imx6qdlsabresd.conf
|
||||||||||||||
|