Hello NXP Community,
I am trying to create the image of Android Q10.0.0_1.0.0 for IMX8M development kit.
I am new to this kind of stuff, but eager to learn.
Flashing the prebuilt image of Q10.0.0_1.0.0 works.
Following the steps mentioned in the Android User Guide, the source code was pulled
and built successfully, but when attempting to flash the iMX8M Mini, a error is thrown:
1:1 1/ 2 [Can find validate IVT header ] SDP: boot -f "./uuu_imx_a
I have to mention that, during the build, a warning was appearing frequently:
WARNING '/home/mihai-gisca/Projects/1370/sources/Q10.0.0_1.0.0/android_build/vendor/nxp-opensource/uboot-imx/lpddr4_pmu_train_1d_imem.bin' not found, resulting binary is not-functional
Extract from build log:
OS: Ubuntu 18.04.4 LTS x64 as guest OS
Appreciate your efforts.
Best regards,
Mihai Gîsca
已解决! 转到解答。
Hello everyone!
I must say that I found a strange behavior of the uuu utility in Linux.
This post here guided me into solving my problem.
I. How I got the error
So, as I mentioned in the main post, after successfully building the source code,
"when attempting to flash the iMX8M Mini, a error is thrown:
1:1 1/ 2 [Can find validate IVT header ] SDP: boot -f "./uuu_imx_a..."
I was doing this using the well known command
[assuming we:
- are located in the created android_build/out/target/product/evk_8mm build folder
and
- have the uuu utility here (do not forget to use the command chmod a+x uuu from within this directory before attempting anything)]:
sudo ./uuu ./uuu_imx_android_flash.sh -f imx8mm -e -u trusty -d mipi-panel
II. What is the solution
In the mentioned link is said that (the inspection of the uuu_imx_android_flash.sh confirms this), the .sh file is creating a script in the /tmp folder, named uuu.lst. I executed the command (from within the /tmp; the uuu is the same as mentioned above, just moved to other location, do not forget the same chmod a+x uuu if it is a fresh uuu):
sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
Auto-adding USB ports
If you are doing all this from within a virtual machine, you might get an error regarding some USB stuff.
You must pass board-specific USB ports to virtual machine automatically when these ports are detected.
When powering on the board (not just connecting the power supply, but also turning on the power switch), a specific USB port appears in the Devices - USB of the virtual machine window. For me it is called "NXP SemiConductors Inc SE Blank". Click Devices - USB - USB Settings... - USB-plus icon and select "NXP SemiConductors Inc SE Blank".
Execute the command again: sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
Received an error regarding USB stuff. After checking the Devices - USB, I found another port. For me it is called "FSL USB download gadget". Click Devices - USB - USB Settings... - USB-plus icon and select "FSL USB download gadget".
Execute the command again: sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
Received another error. After checking the Devices - USB, I found another port called the same "FSL USB download gadget". Click Devices - USB - USB Settings... - USB-plus icon and select the second "FSL USB download gadget".
This time, executing the command: sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
is successful.
This is my first time working with this kind of stuff and I have no knowledge about how it works.
Best regards,
Mihai Gîsca
P.S. If NXP employees have something to tell about this, error or not, please do reply to this post.
P.P.S. For people interested in and without knowledge of this kind of things, it is really hard to do something meaningful. Please, NXP, do consider making guides for beginners in all aspects of starting from scratch.
P.P.P.S. The bureaucracy of accepting posts and replies is really annoying (just my opinion, no offense :smileyhappy:)
Specs:
Windows 10 as host OS
VirtualBox 6.1.4 (installed on host OS)
VirtualBox Extension pack 6.1.4 (installed on host OS)
Ubuntu 18.04.4 LTS as guest OS (.iso image installed with VirtualBox)
VirtualBox Guest Additions 6.1.2 (6.1.4 was buggy at that moment, link here, installed on guest OS)
Hello everyone!
I must say that I found a strange behavior of the uuu utility in Linux.
This post here guided me into solving my problem.
I. How I got the error
So, as I mentioned in the main post, after successfully building the source code,
"when attempting to flash the iMX8M Mini, a error is thrown:
1:1 1/ 2 [Can find validate IVT header ] SDP: boot -f "./uuu_imx_a..."
I was doing this using the well known command
[assuming we:
- are located in the created android_build/out/target/product/evk_8mm build folder
and
- have the uuu utility here (do not forget to use the command chmod a+x uuu from within this directory before attempting anything)]:
sudo ./uuu ./uuu_imx_android_flash.sh -f imx8mm -e -u trusty -d mipi-panel
II. What is the solution
In the mentioned link is said that (the inspection of the uuu_imx_android_flash.sh confirms this), the .sh file is creating a script in the /tmp folder, named uuu.lst. I executed the command (from within the /tmp; the uuu is the same as mentioned above, just moved to other location, do not forget the same chmod a+x uuu if it is a fresh uuu):
sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
Auto-adding USB ports
If you are doing all this from within a virtual machine, you might get an error regarding some USB stuff.
You must pass board-specific USB ports to virtual machine automatically when these ports are detected.
When powering on the board (not just connecting the power supply, but also turning on the power switch), a specific USB port appears in the Devices - USB of the virtual machine window. For me it is called "NXP SemiConductors Inc SE Blank". Click Devices - USB - USB Settings... - USB-plus icon and select "NXP SemiConductors Inc SE Blank".
Execute the command again: sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
Received an error regarding USB stuff. After checking the Devices - USB, I found another port. For me it is called "FSL USB download gadget". Click Devices - USB - USB Settings... - USB-plus icon and select "FSL USB download gadget".
Execute the command again: sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
Received another error. After checking the Devices - USB, I found another port called the same "FSL USB download gadget". Click Devices - USB - USB Settings... - USB-plus icon and select the second "FSL USB download gadget".
This time, executing the command: sudo /home/mihai-gisca/uuu/1.3.134/uuu -v ./uuu.lst
is successful.
This is my first time working with this kind of stuff and I have no knowledge about how it works.
Best regards,
Mihai Gîsca
P.S. If NXP employees have something to tell about this, error or not, please do reply to this post.
P.P.S. For people interested in and without knowledge of this kind of things, it is really hard to do something meaningful. Please, NXP, do consider making guides for beginners in all aspects of starting from scratch.
P.P.P.S. The bureaucracy of accepting posts and replies is really annoying (just my opinion, no offense :smileyhappy:)
Specs:
Windows 10 as host OS
VirtualBox 6.1.4 (installed on host OS)
VirtualBox Extension pack 6.1.4 (installed on host OS)
Ubuntu 18.04.4 LTS as guest OS (.iso image installed with VirtualBox)
VirtualBox Guest Additions 6.1.2 (6.1.4 was buggy at that moment, link here, installed on guest OS)
Hi Mihai
lpddr4_pmu_train_1d_imem.bin can be found in
https://community.nxp.com/docs/DOC-340179
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello Mr. Padykov,
But isn't that lpddr4_pmu_train_1d_imem.bin the same one in
~/android_build/vendor/nxp-source/imx-mkimage/iMX8M ?
There are also the rest of the binary files.
Shouldn't the process of uboot build take those binaries?
If so, why it looks for them in
~/android_build/vendor/nxp-opensource/uboot-imx instead?
Should I copy them from
~/android_build/vendor/nxp-source/imx-mkimage/iMX8M
to
~/android_build/vendor/nxp-opensource/uboot-imx ?
Thank you for your time.
Best regards,
Mihai Gîsca
Hi Mihai
yes firmware may be different as described in sect.4.3 Building u-boot image
MSCALE_DDR_Tool_User_Guide.pdf included in
i.MX8 MSCALE SERIES DDR Tool Release (V3.10)
Best regards
igor
Hello, Mr. Padykov
Is it possible that below commands can make a wrong bootloader for imx8m mini board under Q10.0.0_0.0.0?
source build/envsetup.sh
lunch evk_8mm-usedebug
./imx-make.sh bootloader kernel -j4 2>&1 | tee build-log.txt
Thank you for your support!
Best regards,
Mihai Gîsca
P.S. Please, if possible, provide a step by step guide for beginners.
Hello,
Same errors on the iMX8M Plus eval board : "android_build/vendor/nxp-opensource/uboot-imx/lpddr4_pmu_train_1d_imem.bin' not found, resulting binary is not-functional"
While this file is present in android_build/vendor/nxp-opensource/uboot-imx.
Please, need help.
Thanks