FASTBOOT NOT WORKING IN i.MX8MP Phyboard Pollux

[venu_mos]

NEED HELP IN FASTBOOT.

Hi NXP Community,

Iam currently working on fastboot for imx8mp board phyboard pollux board, but whenever i try to unlock the bootloader it return an error message i will attach screen shots below to better describe my problem here,

whenever i try booting from u-boot i get some other error messages like "usb init failed -19"

please find the attached images to better understand the problem

my goal is to flash images to the board in fastboot mode

@AldoG  IMX8MPLUS #fastboot

#uboot #IMX8 #phytech

[AldoG]

Hello,

I don't really have experience with that board, I would suggest to contact phytec as well regarding your issue.

Fastboot google utility should be downloaded from Android official site first. Before using the fastboot the target board should boot up to bootloader fastboot mode.

To unlock the device.
Boot up the device.
Choose Settings -> Developer Options -> OEM Unlocking to enable OEM unlocking.

Execute the following command on the target side to make the board enter fastboot mode:
$ reboot bootloader

Unlock the device. Execute the following command on the host side:
$ fastboot oem unlock

Wait until the unlock process is complete and reboot your board.

Please try it and let us know if it works.

Best regards,
Aldo.

[venu_mos]

I tried to unlock using that command but it says "Unable to open fastboot HAL"

[AldoG]

Hello!

I cannot see the last image you have shared, it is difficult to see the actual message.

Also, for the error Unable to open fastboot HAL, did the device enter fastboot mode correctly with the steps I have shared previously?
Did you downloaded Fastboot utility from Android oficial site?

Best regards,
Aldo.

[venu_mos]

I have entered into uboot shell prompt where i have entered fastboot command, but it says no USB devices found USB init -19.

how to solve this ?

[AldoG]

Hello,
 
Errno -19 ENODEV means that it couldn't find the USB port specified, I would strongly suggest to contact Phytec regarding this "issue", I believe that it may be some kind of configuration for their hardware that we are missing,

Best regards,
Aldo.