A F&S Development Machine with preinstalled armstonemx8mp-Y2024.07.1 Release can be found here
Posts by fs-support_PG
-
-
F&S Development Machine with Fedora 36 V1.7 (11.09.2024)
There is a new Virtual Machine with Fedora36 in your download section available
My F&S / Tools-Linux /VirtualMachines/Fedora36/64-bit (i.MX8)/ F_S_Development_Machine-Fedora_36_V1.7.ova
The structure of the virtual machine is listed below.
Content:
- fsimx8mm-Y2023.10 (/home/developer/fsimx8mm-Y2023.10)
- fsimx8mm-B2023.11 (/home/developer/fsimx8mm-B2023.11)
- fsimx8mn-Y2024.02 (/home/developer/fsimx8mn-B2024.02)
- fsimx8mp-Y2024.07 (/home/developer/fsimx8mp-Y2024.07)
New Content:
- armstonemx8mp-Y2024.07.1 (/home/developer/armstonemx8mp-Y2024.07.1)
Removed Content:
Your F&S Support Team
-
F&S armStoneMX8MP Yocto Release 2024.07.1 (armstonemx8mp-Y2024.07.1)
Please see the file
doc/FSiMX8MP_FirstSteps_eng.pdf
for a description of how everything is installed and used. This doc sub-directory also contains other documentation, for example about the hardware of the boards and the starter kits.
This is a maintenance release for armStoneMX8MP.
Please note that Yocto releases use a 'Y' for the version number. The version counting is independent form other releases.
The release consists of the following files and directories:
- README.txt Release notes (this text)
- setup-yocto Script to download and install the Yocto release
- fs-release-manifest.xml Release Manifest, containing the used versions
- as git hashes
- binaries/ Precompiled images (full names)
- sdcard/ Precompiled images (names as expected by
- install script)
- doc/ Hardware and software manuals, schematics
Here are some highlights of this release.
1. Add support for armStoneMX8MP revision 1.10
It feature an optional RS485 transceiver, an EEPROM, a new audio codec and several smaller bug fixes and improvements.
The following list shows the most noticeable changes in this release in more detail since our last release for this platform. Please note that the source code is also used for other platforms. This is why you will also find references to other CPU types and F&S boards here in the change log.
u-boot-2021.04-fsimx8mp-2024.07.1 ()
-----------------------------------------------
Supported boards: armStonemx8MP
- Add support for armStoneMX8MP Rev 110
- Support output of checksum in fsimage
- Improve boottime for fastboot
linux-5.15.160-fsimx8mp-2024.07.1 ()
-----------------------------------------------
Supported boards: armStonemx8MP
- Add support for armStoneMX8MP Rev 110
- Disable SD UHS support by default for
armstonemx8mp
meta-fus-fsimx8mp-2024.07 ()
-----------------------------------------------
(no changes)
atf-5.15.71-fsimx8mp-2024.07 ()
-----------------------------------------
(no changes)
firmware-imx-8.10.1 ddr synopsys ()
-------------------------------------------
(no changes)
linux-examples-fus-fs1
-------------------------------------------
(no changes)
Documentation
-------------
- Update to version 1.7 of FSiMX8MP_FirstSteps_eng.pdf
- Update to version 0.19 of LinuxOnFSBoards_eng.pdf
Please download the hardware documentation directly from our website.
Then you always have the newest version.
-
Hello,
we have tested this board with this release and it seems to work.
Some questions:
- So only the upper connector is failing? The lower one works?
- Is the error Baseboard or SOM specific? Does the failing SOM work with an different Baseboard?
- Did you try different USB sticks?
- Did you test the Uboot from the new release fsimx8mp-Y2024.07?
Your F&S Support Team
-
Hello,
the reason, why this message is not displayed with mainline kernel 6.11 should be, that the warning does not exist in the imx-sdma driver code there:
linux mainline 6.11-rc4:
https://github.com/torvalds/li…ivers/dma/imx-sdma.c#L873
linux-imx 5.15.y
https://github.com/nxp-imx/lin…ivers/dma/imx-sdma.c#L988
It was introduced in kernel 5.10, however, it also disappeared in newer imx-kernel versions:
linux-imx 6.1.y
https://github.com/nxp-imx/lin…vers/dma/imx-sdma.c#L1024
I cannot find any commit, that removed this warning so it seems that it just was not merged into the newer kernel versions.
This is the commit, which introduced the warning:
[1] https://github.com/nxp-imx/lin…ce86c47c8cb10c3567a37bad0
We did not see these kind of messages yet, however we did not do any intense sdma testing so far of the imx6sx.
The commit message indicates, that is has something to do with high CPU loads. As the imx6sx is a Solo CPU, this might in fact be a problem.
The fact, that the warnings where added in kernel 5.10 explain, why you did not see them so far.
Is your CPU load very high, when these warnings occur?
Could you try to apply the changes from [1] to the mainline kernel and see if they still not occur?
Your F&S Support Team
-
Hello,
this comes from the pca9632 GPIO-Expander on the ADP-AStone2EDT2-LCD Display adapter.
https://github.com/FSEmbedded/…s/armstonea9qdl.dtsi#L897
If you are not using this, you should be ok to set
status = "disabled";
However, you will also have to disable the nodes that reference it
https://github.com/FSEmbedded/…s/armstonea9qdl.dtsi#L226
https://github.com/FSEmbedded/…s/armstonea9qdl.dtsi#L517
It should also be OK to ignore it, but it would be cleaner to just disable these unused nodes.
Your F&S Support Team
-
Hello,
good to hear that it works with your baseboard.
There might be an supply issue on our baseboard that may cause a sporadic trigger on the boot select line when doing a soft reset under certain conditions.
We will investigate that further.
Your F&S Support Team
-
Hello,
like already mentioned, i did get the same sdma errors with the fsimx6_min_defconfig as you described and was able to fix it by adding the IMX specific buildroot packages.
Code- # speaker-test
- speaker-test 1.2.8
- Playback device is default
- Stream parameters are 48000Hz, S16_LE, 1 channels
- Using 16 octaves of pink noise
- Rate set to 48000Hz (requested 48000Hz)
- Buffer size range from 256 to 32768
- Period size range8<--- cut here ---
- from 128 to 16384
- UsUinnagb lme to handle kernel NULL pointer dereference at virtual address 00000003
- 68bpugfdf e=r 1s5i9z5e2 b31297
- [eriods = 4
- 0w0a0s0 0s0e0t3 *pgd=00000000
- period_size = 8192
- was set buffInternal error: Oops: 805 [#1] PREEMPT SMP ARM
- r_size = 32768
- 0 - Front Left
- Modules linked in: mxc_v4l2_capture ipu_bg_overlay_sdc ipu_still v4l2_int_device ipu_prp_enc ipu_csi_enc ipu_fg_overlay_sdc imx_sdma virt_dma
- CPU: 1 PID: 266 Comm: speaker-test Not tainted 5.15.148-F+S #2
- Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
- PC is at sdma_transfer_init+0x184/0x214 [imx_sdma]
- LR is at 0x0
- pc : [<7f008920>] lr : [<00000000>] psr: 80030093
- sp : 8326fd18 ip : a0833280 fp : 8352c040
- r10: 20030093 r9 : 8352eca0 r8 : 00000000
- r7 : 00000003 r6 : a0833200 r5 : 83762d00 r4 : 8352c41c
- r3 : 8352e040 r2 : 00000001 r1 : 00000000 r0 : a0833200
- Flags: Nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment none
- Control: 10c5387d Table: 131b004a DAC: 00000051
- Register r0 information: 0-page vmalloc region starting at 0xa0820000 allocated at __devm_ioremap+0x9c/0xa8
- Register r1 information: NULL pointer
- Register r2 information: non-paged memory
- Register r3 information: non-slab/vmalloc memory
- Register r4 information: non-slab/vmalloc memory
- Register r5 information: slab kmalloc-128 start 83762d00 pointer offset 0 size 128
- Register r6 information: 0-page vmalloc region starting at 0xa0820000 allocated at __devm_ioremap+0x9c/0xa8
- Register r7 information: non-paged memory
- Register r8 information: NULL pointer
- Register r9 information: non-slab/vmalloc memory
- Register r10 information: non-paged memory
- Register r11 information: non-slab/vmalloc memory
- Register r12 information: 0-page vmalloc region starting at 0xa0820000 allocated at __devm_ioremap+0x9c/0xa8
- Process speaker-test (pid: 266, stack limit = 0x415c7eb4)
- Stack: (0x8326fd18 to 0x83270000)
- fd00: 00000000 00000000
- fd20: 00000003 8352e040 728d5139 8352c41c 00000001 00000000 00004000 00000004
- fd40: 00010000 00000003 8352c040 7f008b1c 81b24128 802f7f18 00000003 1c080000
- fd60: 81b24128 00000000 832f8940 82ac5b00 7f008aa0 00000003 00000002 82b0361c
- fd80: 8326e000 807c5244 00000001 00000003 82ac5a0c 82ac5b00 00000001 82ac5a0c
- fda0: 82b03040 807d0220 00000000 807d10c8 83539040 00000001 00000000 82ac5b00
- fdc0: 80bab3a4 82b03040 00002000 835460f4 8326e000 807d1adc 00000000 82ac5b00
- fde0: 00000003 80bab3a4 00000000 807baa60 80bab3a4 82ac5b00 00000000 00000003
- fe00: 00000000 807bca5c 83546000 82ac5b00 00000000 00000000 00000000 807c3114
- fe20: 00004000 807c03d0 807c03d0 00000000 00002000 807c0074 00000000 00006000
- fe40: 008f0010 00006000 00000000 fff39913 8326fea8 00000051 83525240 3eefd9dd
- fe60: 0000000c ffffe000 82ac5b00 7ef39908 00000051 83525240 832f8a40 00000036
- fe80: 00000000 807bee9c 00000000 8326fe90 00000000 00000000 008e8c0c 008e8c10
- fea0: 00000000 00000000 00000000 008f0010 00002000 835153cc 008f3000 80113738
- fec0: 00000000 801e544c 00000000 00000000 00000000 00000000 80524578 3eefd9dd
- fee0: 00000000 00000000 00000000 00000000 832e9960 3eefd9dd 000008f3 835aa200
- ff00: 83525240 7ef39908 400c4150 00000004 83525240 00000036 00000000 802204ac
- ff20: 835aa200 80220dd4 00000000 8326ffb0 008f3000 832e9960 00000817 00000255
- ff40: 83292640 8015fdf4 8326ffb0 80110dd0 00000000 00000000 00000017 3eefd9dd
- ff60: 8351f240 00000817 008f3000 ffffffff 8326ffb0 8110f1cc 00000807 3eefd9dd
- ff80: 00000000 008e8a78 008e8a20 76f7a378 00000036 801002c4 8326e000 00000036
- ffa0: 00000000 80100060 008e8a78 008e8a20 00000004 400c4150 7ef39908 7ef398f8
- ffc0: 008e8a78 008e8a20 76f7a378 00000036 004b6040 004b5e98 00000000 00000000
- ffe0: 76f7a878 7ef398e8 76ee7f88 76d81bb0 20030010 00000004 00000000 00000000
- [<7f008920>] (sdma_transfer_init [imx_sdma]) from [<7f008b1c>] (sdma_prep_dma_cyclic+0x7c/0x178 [imx_sdma])
- [<7f008b1c>] (sdma_prep_dma_cyclic [imx_sdma]) from [<807c5244>] (snd_dmaengine_pcm_trigger+0xc0/0x150)
- [<807c5244>] (snd_dmaengine_pcm_trigger) from [<807d0220>] (soc_component_trigger+0x20/0x38)
- [<807d0220>] (soc_component_trigger) from [<807d10c8>] (snd_soc_pcm_component_trigger+0x80/0xe8)
- [<807d10c8>] (snd_soc_pcm_component_trigger) from [<807d1adc>] (soc_pcm_trigger+0x48/0x15c)
- [<807d1adc>] (soc_pcm_trigger) from [<807baa60>] (snd_pcm_action_single+0x38/0x64)
- [<807baa60>] (snd_pcm_action_single) from [<807bca5c>] (snd_pcm_action+0x5c/0x60)
- [<807bca5c>] (snd_pcm_action) from [<807c3114>] (__snd_pcm_lib_xfer+0x5fc/0x648)
- [<807c3114>] (__snd_pcm_lib_xfer) from [<807bee9c>] (snd_pcm_ioctl+0x3a8/0x1270)
- [<807bee9c>] (snd_pcm_ioctl) from [<802204ac>] (vfs_ioctl+0x20/0x38)
- [<802204ac>] (vfs_ioctl) from [<80220dd4>] (sys_ioctl+0xc0/0x944)
And you mentioned, that you do not get these errors with the wayland_defconig.
I also wonder, why you don't get the sdma logs in your boot messages
So my guess is that there are some missing packages in your rootfs or kernel.
Could you send us your kernel and buildroot defconfig via mail?
Your F&S Support Team
-
Hello,
I was able to reproduce your issue by adding the following lines to the fsimx6_min_defconfig
and runnign speaker-test
By additionally adding these lines to fsimx6_min_defconfig the error did not accrue anymore and speaker-test worked as intended
The imx-sdma driver was build as a module.
Could you try to add these lines to your buildroot defconfig as well?
Your F&S Support Team
-
Hello,
could you provide some additional information on the reboot issue?
Is this happening regularly or just some times?
If you connect the board to your PC via UBS-Device, does the board get recognized by your PC after the issue occures?
This would hint to a problem with the Bootselect pin.
Your F&S Support Team
-
Hello,
we definitely successfully tested speaker-test with the fsimx6_wayland_defconfig.
However, it might be true that the fsimx6_min_defconfig is not working, because of the missing sdma firmware.
ALSA device list:No soundcards found. with imx-smda as module is expected, as the driver is getting loaded after the rootfs.
Could you provide a full bootlog with this error?
Your F&S Support Team
-
Hello,
please excuse the late answer.
Could you post the exact gpiod command, you are using?
Did you make sure, that the pins, you are trying to use, are routed to GPIO in device tree?
You might have to to thisis additionally, because not all pins are routed to GPIO by default.
For example for for muxing the SD_B DATA pads to GPIO with a 100k internal pullup you would have to add the following node to your DTS
CodeYou can find the pin muxing macros at
https://github.com/FSEmbedded/…/boot/dts/imx6q-pinfunc.h
For information on the pad settings, please see
https://github.com/FSEmbedded/…l/fsl%2Cimx6q-pinctrl.txt
Your F&S Support Team
-
A F&S Development Machine with preinstalled fsimx8mp-Y2024.07 Release can be found here
-
F&S Development Machine with Fedora 36 V1.6 (02.08.2024)
There is a new Virtual Machine with Fedora36 in your download section available
My F&S / Tools-Linux /VirtualMachines/Fedora36/64-bit (i.MX8)/ F_S_Development_Machine-Fedora_36_V1.6.ova
The structure of the virtual machine is listed below.
Content:
- fsimx8mm-Y2023.10 (/home/developer/fsimx8mm-Y2023.10)
- fsimx8mm-B2023.11 (/home/developer/fsimx8mm-B2023.11)
- fsimx8mn-Y2024.02 (/home/developer/fsimx8mn-B2024.02)
New Content:
- fsimx8mp-Y2024.07 (/home/developer/fsimx8mp-Y2024.07)
Removed Content:
- fsimx8mp-Y2023.09 (/home/developer/fsimx8mp-Y2023.09)
Your F&S Support Team
-
F&S i.MX8M-Plus Yocto Release 2024.07 (fsimx8mp-Y2024.07)
Please see the file
doc/FSiMX8MP_FirstSteps_eng.pdf
for a description of how everything is installed and used. This doc sub-directory also contains other documentation, for example about the hardware of the boards and the starter kits.
This is a maintenance release for all F&S boards and modules based on the i.MX8M-Plus CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MP(r2), armStoneMX8MP, efusmx8mp or SMARCMX8MP (FSSMMX8MP). More boards may be added to this family in the future.
All these boards can work with software that is created from this release package.
Please note that Yocto releases use a 'Y' for the version number. The version counting is independent form other releases.
The release consists of the following files and directories:
- README.txt Release notes (this text)
- setup-yocto Script to download and install the Yocto release
- fs-release-manifest.xml Release Manifest, containing the used versions as git hashes
- binaries/ Precompiled images (full names)
- sdcard/ Precompiled images (names as expected by install script)
- doc/ Hardware and software manuals, schematics
Here are some highlights of this release.
1. Update Linux Kernel to patch level 5.15.160
This fixes several smaller bugs and CVEs.
For more information please see
https://cdn.kernel.org/pub/lin…el/v5.x/ChangeLog-5.15.72
to
https://cdn.kernel.org/pub/lin…l/v5.x/ChangeLog-5.15.160
Also adds support for the new F&S LVDS Displays and improves the Cortex-M support in Linux and adds SPI-NOR flash support to the efusmx8mp.
2. Improved boot loader U-Boot 2021.04
Several bug fixes and improvements, like the Resource Domain Control support in U-Boot device tree and an improved xhci USB driver.
3. Tested with Yocto poky layer version 4.0.20
This fixes several smaller bugs and CVEs, like CVE-2024-6387 OpenSSH signal handler race condition.
For more information, please see
https://docs.yoctoproject.org/…release-notes-4.0.19.html
to
https://docs.yoctoproject.org/…release-notes-4.0.20.html
The following list shows the most noticeable changes in this release in more detail since our last release for this platform. Please note that the source code is also used for other platforms. This is why you will also find references to other CPU types and F&S boards here in the change log.
u-boot-2021.04-fsimx8mp-2024.07 ()
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Check for crc32 and xxd before using them during build
- Add command fsimage boot
- Add support for FSSMMX8MP
- Add loading of secondary partition Images to fsimx8mp
- Add support for boards with DRAM over 3GB
- Improve sub xhci driver
- Add RDC Configuration for M7 usage
- Add board-cfg information to linux bdinfo
linux-5.15.160-fsimx8mp-2024.07 ()
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Update to patch level 5.15.160
- Improve imx8mp LVDS clock to support more displays
- Add support for fsimx8mp BT070L1060CS0I1ADA display
- Add support for fsimx8mp EE1010B1T display
- Add support for FSSMMX8MP
- Fix RPMSG failure on boot
- Improve Cortex-M7 Support
- Add efusmx8mp spi nand support
- Fix fsimx8mp DSP dram reservation
- Fix imx uart dma watermark level
- Fix fsimx8mp sgtl5000 mclock issue
- Fix number of chip-selects property in all F&S DTS
meta-fus-fsimx8mp-2024.07 ()
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Add support for FSSMMX8MP
- Add F&S psplash Logo
- Remove fbida from fus-image-std
- Tested with Yocto poky layer version 4.0.20
atf-5.15.71-fsimx8mp-2024.07 ()
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Fix poweroff command and ON/OFF button in imx_system_off()
- Fix debug build console for fsimx8mp
firmware-imx-8.10.1 ddr synopsys ()
(no changes)
linux-examples-fus-fs1
(no changes)
Documentation
- Update to version 1.6 of FSiMX8MP_FirstSteps_eng.pdf
- Update to version 0.19 of LinuxOnFSBoards_eng.pdf
Please download the hardware documentation directly from our website.
Then you always have the newest version.
-
Hello,
this is an English forum so I will answer in English.
You wan to use a status led in U-Boot, but GPIO3_IO23 is not woring.
Did you configure the correct pin mux and pad-settings for GPIO3_IO23 ?
Currently, device tree is not used for F&S i.MX6 boards in U-Boot so you will have to set this in the board file
board/F+S/fsimx6ul/fsimx6ul.c
You can have a look here, how to do so
https://github.com/FSEmbedded/…/fsimx6ul/fsimx6ul.c#L320
https://github.com/FSEmbedded/…/fsimx6ul/fsimx6ul.c#L343
You will have to set the following pin muxes for GPIO3_IO23
https://github.com/FSEmbedded/…dts/imx6ul-pinfunc.h#L636
You should also do this for GPIO3_IO22 , because this is currently ony muxed to gpio because of our default LCD settings
https://github.com/FSEmbedded/…/fsimx6ul/fsimx6ul.c#L924
I hope this helps.
Your F&S support Team
-
-
Yes it seems that way.
Your F&S Support Team
-
Hello,
the eMMC boot partitions are always mounted read only by default.
We would recommend to keep it that way and only mount read/write if you have to write the environment.
This is, because the bootloader is also saved to these partitions, and should be protected
After that, you should mount it read only again.
Your F&S Support Team
-
Hello,
if you have added additional QT libraries, you should use also install a new QT image, so the libraries installed on the board match the one from the toolchain.
If not you can just use the fus-image-qt6 example image.
Your F&S Support Team