# Unable to connect to u-boot after serial connection using NXP's iMX /MScale DDR tool **URL:** \ **Category:** NXP i.MX8M Plus\ **Tags:** iMX8M-plus\ **Created:** [June 7, 2023, 10:03am UTC](https://community.solid-run.com/t/unable-to-connect-to-u-boot-after-serial-connection-using-nxps-imx-mscale-ddr-tool/660 "2023-06-07T10:03:13Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ithamar](https://avatars.discourse-cdn.com/v4/letter/i/4bbf92/32.png) [@ithamar](https://community.solid-run.com/u/ithamar)\ **Post date:** [June 7, 2023, 10:03am UTC](https://community.solid-run.com/t/unable-to-connect-to-u-boot-after-serial-connection-using-nxps-imx-mscale-ddr-tool/660/1 "2023-06-07T10:03:13Z")
I’m using reference Solid Run’s reference board based upon NXP’s i.MX8M Plus. The OS image is a debian image given by Solid Run along with the reference board. I moved the Boot Mode resistors to USB Serial download. I am using DDR/LPDDR calibrating testing and driver code generation tool, called iMX /MScale DDR tool, by NXP. Setup wouldn’t start even though checking all the ports and raching timeout because no environment variable bootfile is defined, even if I push into one of the USB ports on the board a USB stick with a ubuntu image (and the stick itself as a memory is identified). The input that I get is as the following: Device 0: Vendor: ASolid Rev: Prod: USB Type: Removable Hard Disk Capacity: 30200.0 MB = 29.4 GB (61849601 x 512) … is now current device Scanning usb 0:1… ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-d0-63-b4-04-c9-36 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-imx8m-imx8mp\_solidrun ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-imx8m ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110missing environment variable: bootfile Retrieving file: pxelinux.cfg/default ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110Config file not found ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110ethernet@30bf0000 Waiting for PHY auto negotiation to complete… TIMEOUT ! phy\_startup() failed: -110FAILED: -110u-boot=\> Does someone have an idea what am I missing? ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 7, 2023, 2:29pm UTC](https://community.solid-run.com/t/unable-to-connect-to-u-boot-after-serial-connection-using-nxps-imx-mscale-ddr-tool/660/2 "2023-06-07T14:29:06Z")
I am a bit unclear as to what you are trying to accomplish. We have already and calibrated our SOM’s with the existing DDR configurations we supply in our BSP. Regardless NXP’s ddr calibration and test tool does not use a full OS image, only the supplied calibration binaries. ---
**Author:** ![ithamar](https://avatars.discourse-cdn.com/v4/letter/i/4bbf92/32.png) [@ithamar](https://community.solid-run.com/u/ithamar)\ **Post date:** [June 7, 2023, 3:40pm UTC](https://community.solid-run.com/t/unable-to-connect-to-u-boot-after-serial-connection-using-nxps-imx-mscale-ddr-tool/660/3 "2023-06-07T15:40:32Z")
Hi Jon We are developing a system based upon iMX 8M-Plus even though our Micron LPDDR4 will be a of a different type. I wanted to make sure I am capable of calibrating, and testing the DDR over the hamming board so that the same procedure would be applied to the board that we develop. Is that possible? ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 8, 2023, 5:00am UTC](https://community.solid-run.com/t/unable-to-connect-to-u-boot-after-serial-connection-using-nxps-imx-mscale-ddr-tool/660/4 "2023-06-08T05:00:54Z")
Yes of course. You can use our documentation to get the memory SKU for your part and then download the data sheet for the memory. Between that and our SOM’s simplified schematic you should have all the documentation you need to fill out NXP’s excel spreadsheet to generate the DDR tool profile to run. The entire process is documented by NXP.