Differences
This shows you the differences between two versions of the page.
|
ass:labs-2025:01:tasks:03 [2025/08/04 12:34] florin.stancu |
ass:labs-2025:01:tasks:03 [2025/08/04 15:18] (current) florin.stancu |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| {{ :ass:labs-2025:01:imx93_boot_jumpers.jpg?500 |}} | {{ :ass:labs-2025:01:imx93_boot_jumpers.jpg?500 |}} | ||
| - | == Step 6. Download & compile the IMX Universal Update Utility == | + | == Step 3.1. Download & compile the IMX Universal Update Utility == |
| The Universal Update Utility (UUU) is an image deployment tool created by NXP for it's i.MX architecture. For more information about its usage, scripting interface and supported protocols, check out the [[https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/imx-processors/140261/1/UUU.pdf|documentation]]. | The Universal Update Utility (UUU) is an image deployment tool created by NXP for it's i.MX architecture. For more information about its usage, scripting interface and supported protocols, check out the [[https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/imx-processors/140261/1/UUU.pdf|documentation]]. | ||
| Line 39: | Line 39: | ||
| Note that nothing will be printed on the console yet, but you need to stay connected to receive the messages that will follow! | Note that nothing will be printed on the console yet, but you need to stay connected to receive the messages that will follow! | ||
| - | == Step 7: Upload the firmware image package (FIP)! == | + | == Step 3.2. Upload the firmware image package (FIP)! == |
| - | Ever since the USB-C cable was plugged in, **BL1** has been waiting for the FIP data over serial, thanks to our jumper configuration. Now we can finally provide this data using **uuu** and it's SDP implementation: | + | Ever since the USB-C cable was plugged in, **BL1** has been waiting for the FIP data over serial, thanks to our jumper configuration. Now we can finally provide this data using **uuu** and it's SDP implementation. |
| + | |||
| + | <note tip> | ||
| + | If you're using a remote VM, you must download the ''flash.bin'' file (reminder: it was generated inside ''imx-mkimage/iMX93/'' build subdirectory) to your local machine using ''scp'': | ||
| + | |||
| + | <code bash> | ||
| + | # basic syntax: scp <source> <destination> | ||
| + | # either source or destination MUST be a remote SSH with the form: | ||
| + | # username@host:/path/to/file | ||
| + | # Note: -P specifies the port (your VM index!) | ||
| + | # example (destination is "./" -- your current directory): | ||
| + | scp -P 220X your-user@arm2026.root.sx:path/to/flash.bin ./ | ||
| + | </code> | ||
| + | </note> | ||
| <code bash> | <code bash> | ||
| Line 56: | Line 69: | ||
| Finally, when everything is in working condition, you should see a ''Run fastboot ...'' message, press //Ctrl + C// and you should get the ''u-boot%%=>%%'' prompt. | Finally, when everything is in working condition, you should see a ''Run fastboot ...'' message, press //Ctrl + C// and you should get the ''u-boot%%=>%%'' prompt. | ||
| - | == Step 9. Time to play! == | + | == Step 3.3. Time to play! == |
| You might be wondering: but we don't have an OS installed yet... is this all we can do now? | You might be wondering: but we don't have an OS installed yet... is this all we can do now? | ||
| Line 72: | Line 85: | ||
| Finally, let's test the USB Mass Storage emulation of the eMMC using u-boot (which will allow us to access the board's internal flash memory direcrly from our ;laptops / PCs via USB-C). Try the ''ums'' command (use Google/LLMs for its arguments ;) ). | Finally, let's test the USB Mass Storage emulation of the eMMC using u-boot (which will allow us to access the board's internal flash memory direcrly from our ;laptops / PCs via USB-C). Try the ''ums'' command (use Google/LLMs for its arguments ;) ). | ||
| + | |||
