Open ramprakashb opened 3 years ago
can you try latest uuu? 1.3.154 is old one.
it is strange. all _file should replace by followed argument.
Hi @nxpfrankli ,
Thanks for the reply.
I did try with the latest version. But again for the latest demo images I get the following error:
I also ran dmesg during the same time and I can see that every time I run the UUU command the USB type C port connected to the J11 port of the NXP board disconnects and then reconnects.
are you C0 chip or B0 chip?
Hi @nxpfrankli ,
I am using a C0 chip.
Thanks and Regards, Ramprakash
you should use c0 file
imx-boot-imx8qxpc0mek-fspi.bin-flash_spl_flexspi
Hi @nxpfrankli ,
Thank you the demo boot image imx-boot-imx8qxpc0mek-fspi.bin-flash_spl_flexspi worked and the board is booted with u-boot.
But when I try to use UUU for the custom image built using mkimage tool. I still get the same error. Is there any changes that are required for building the images for C0 board.
Added Make SOC=iMX8QXP REV=C0 flash
This command is for imx_mkimage, not build scfw.
Imx_mkimage package SECO firmware contrainer, uboot, scfw together and build one image, which rom can recognize.
From: Ramprakash notifications@github.com Sent: Monday, February 8, 2021 5:27 PM To: NXPmicro/mfgtools mfgtools@noreply.github.com Cc: Frank Li frank.li@nxp.com; Mention mention@noreply.github.com Subject: [EXT] Re: [NXPmicro/mfgtools] Not able to flash iMX8QX MEK using UUU (#250)
Caution: EXT Email
I tried the command "make SOC=iMX8QXP REV=C0 " but I face error like the below.
I copied the files from the location "cp -r platform/board/mx8qx_val platform/board/mx8qx_myboard" before executing the make command. [Screen Shot 2021-02-08 at 3 22 59 PM]https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F41544795%2F107294323-0e859580-6a22-11eb-9101-4c7320883456.png&data=04%7C01%7Cfrank.li%40nxp.com%7C8be68a41a1da41c7458508d8cc890d5f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484236297380265%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=a64FYyzG1enuG2tT0VwVlrxgL%2FduImcCJ3Eq%2FlD%2BfTo%3D&reserved=0
- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNXPmicro%2Fmfgtools%2Fissues%2F250%23issuecomment-775532218&data=04%7C01%7Cfrank.li%40nxp.com%7C8be68a41a1da41c7458508d8cc890d5f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484236297380265%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8cKi1aRmxZvh8Abdxx47d24p0VSFWhKyOkXnIsOAt%2FE%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAETGIO2LY2EXI6UWMXDUQKTS6BXMVANCNFSM4XDI4H5A&data=04%7C01%7Cfrank.li%40nxp.com%7C8be68a41a1da41c7458508d8cc890d5f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484236297380265%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=F8PBD3oVDxhS0nqbKYntAM7P7npuB9inuVxyIWnoogc%3D&reserved=0.
Hi @nxpfrankli , Thanks for the reply.
I did try the REV=C0 with mkimage tool. But when I use the REV = C0 the command which gets executed still shows B0. And the image fails to flash SPI memory.
But when I try to hardcode the REV=C0 into the soc.mak file under iMX8QX folder I get a error that the Rev = C0 is not known. Do you have any idea how to fix this?
Did your mkimage too old
From: Ramprakash notifications@github.com Sent: Monday, February 8, 2021 7:47 PM To: NXPmicro/mfgtools mfgtools@noreply.github.com Cc: Frank Li frank.li@nxp.com; Mention mention@noreply.github.com Subject: [EXT] Re: [NXPmicro/mfgtools] Not able to flash iMX8QX MEK using UUU (#250)
Caution: EXT Email
I did try the REV=C0 with mkimage tool. But when I use the REV = C0 the command which gets executed still shows B0. And the image fails to flash SPI memory.
But when I try to hardcode the REV=C0 into the soc.mak file under iMX8QX folder I get a error that the Rev = C0 is not known. Do you have any idea how to fix this? [Screen Shot 2021-02-08 at 5 42 54 PM]https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F41544795%2F107304275-9d4fdd80-6a35-11eb-9a51-e25255176746.png&data=04%7C01%7Cfrank.li%40nxp.com%7Cdb4aed7fdc0d499c47b508d8cc9c9a9c%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484320262066949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ecJBkrTQIgoxcmdimixc5kCnTDQWVzYmH60ZGZN3BW0%3D&reserved=0 [Screen Shot 2021-02-08 at 5 44 21 PM]https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F41544795%2F107304278-9de87400-6a35-11eb-8530-1081a647bde8.png&data=04%7C01%7Cfrank.li%40nxp.com%7Cdb4aed7fdc0d499c47b508d8cc9c9a9c%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484320262066949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=03qbShGJaN4R2EusJo5MifjD2bD%2Bw6c9%2FWNIeKNBiHM%3D&reserved=0
- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNXPmicro%2Fmfgtools%2Fissues%2F250%23issuecomment-775592496&data=04%7C01%7Cfrank.li%40nxp.com%7Cdb4aed7fdc0d499c47b508d8cc9c9a9c%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484320262066949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4HCLI66AES6nyiMq23K8Oxyh6N1o5OwxiWWOVsdAULA%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAETGIOYXAE4QV7R3TXCQNIDS6CHZRANCNFSM4XDI4H5A&data=04%7C01%7Cfrank.li%40nxp.com%7Cdb4aed7fdc0d499c47b508d8cc9c9a9c%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637484320262076902%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oqcx60KeInPxCd1l7cbyVsXdlX2ei4k9UFNpAAMl630%3D&reserved=0.
Hi @nxpfrankli ,
Thanks for the reply.
I now got the latest mkimage from the NXP website and the when I try to use uuu for the flash_flexspi image which I built, the output reaches 100% and then gets suck there. It does not moves past it. I did not face this issue while flashing demo image. Is the command execution correct or do I need to add any other file together with this?
your image have not boot in customer board. Please check your image.
Hi @nxpfrankli ,
For imx8 C0 version of the board apart from SECO is there any changed required in the build process.
I have generated the image using the following components: SCU -
SECO:
U-Boot:
ATF:
Mkimage:
Is there anything missing in the above steps?
Hi All,
I am trying to boot QSPI flash memory in iMX8QX MEK evaluation board using latest UUU. I have used both custom built image for QSPI and also the pre built image "imx-boot-imx8qxpmek-fspi.bin-flash_flexspi" from the NXP website. But whenever I use the command "sudo uuu -b qspi flash_uboot.bin flash_scfw.bin " I get the following error. How to fix this issue?
nikola@NikolaTesla:iMX8QX$ sudo uuu -v -b qspi flash_uboot.bin flash_scfw.bin uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.3.154-0-g47ddef5
Build in config: Pctl Chip Vid Pid BcdVersion
Run built-in script:
uuu_version 1.2.39
@_flexspi.bin | bootloader
@_image [_flexspi.bin] | image burn to flexspi, default is the same as bootloader
This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ
SDP: boot -f _flexspi.bin
This command will be run when ROM support stream mode
i.MX8QXP, i.MX8QM, skip QSPI header
SDPS: boot -f _flexspi.bin -skipfhdr
These commands will be run when use SPL and will be skipped if no spl
SDPU will be deprecated. please use SDPV instead of SDPU
{
SDPU: delay 1000 SDPU: write -f _flexspi.bin -offset 0x10000 -skipfhdr SDPU: jump
}
These commands will be run when use SPL and will be skipped if no spl
if (SPL support SDPV)
{
SDPV: delay 1000 SDPV: write -f _flexspi.bin -skipspl -skipfhdr SDPV: jump
}
FB: ucmd setenv fastboot_buffer ${loadaddr} FB: download -f _image
Check Image if include flexspi header
FB: ucmd if qspihdr dump ${fastboot_buffer}; then setenv qspihdr_exist yes; else setenv qspihdr_exist no; fi;
FB[-t 60000]: ucmd if test ${qspihdr_exist} = yes; then qspihdr init ${fastboot_buffer} ${fastboot_bytes} safe; else true; fi;
if uboot can't support qspihdr command, use uboot image to write qspi image, which require image include qspi flash header
FB: ucmd if test ${qspihdr_exist} = no; then sf probe; else true; fi; FB[-t 40000]: ucmd if test ${qspihdr_exist} = no; then sf erase 0 +${fastboot_bytes}; else true; fi; FB[-t 20000]: ucmd if test ${qspihdr_exist} = no; then sf write ${fastboot_buffer} 0 ${fastboot_bytes}; else true; fi; FB: done
Wait for Known USB Device Appear...
Error: fail open file: >_flexspi.bin
nikola@NikolaTesla:iMX8QX$
Thanks and Regards, Ramprakash