Hi2*
I’m trying to install Linux according to the instructions https://developer-archives.toradex.com/knowledge-base/linux-colibri-pxa-flashing , unpacked the wince2linux320v20.zip, but I can’t install U-boot. There is no exec file (update.exe) in the Windows directory on the device .
Can someone send update.exe or is it possible to install U-boot from the Eboot menu?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your question. It seems you’re trying to install U-Boot on your device but are encountering difficulties due to the absence of the update.exe file in the Windows directory. This file is typically used for updates in Windows CE environments.
Here are a few suggestions that might help you proceed:
Explore the Eboot Menu: Since the update.exe is missing, you might want to check the Eboot menu for any options related to bootloader installation or updates. Some devices allow you to update the bootloader directly from this menu. You can usually access the Eboot menu by interrupting the boot process, often by pressing a specific key during startup.
Access the U-Boot Console: If U-Boot is already installed but not configured, you can try accessing its console via a serial connection. This involves connecting to the primary UART (often UART_A) using a serial terminal program like PuTTY or Minicom. This access can help you troubleshoot or configure the boot process.
Consider Alternative Methods: If the above options are not feasible, you might need to explore other methods specific to your hardware. This could include using a different bootloader or recovery mode, if available.
Please note that these suggestions are based on general practices and may not fully apply to your specific device model and configuration. I hope this helps you move forward with your project.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
https://community.nxp.com/t5/i-MX-Processors/Boot-splash-screen-image-i-MX28/td-p/202386
I have Eboot menu:
[0] IP address: 192.168.50.2
[1] Subnet Mask: 255.255.255.0
[2] Boot delay: 3 seconds
[3] DHCP: (Disabled)
[5] Auto Download image at startup(Enable)
[8] Initialize Download RAM
[L] Launch existing flash resident image now
[C] Read current RTC time
[S] Set BSP Configuration
[F] Format User Partition(Enabled)
[M] Download image with SDMMC Card
[D] Download nk.bin or eboot.bin (using Platform Builder)
[O] Download eboot.bin (using TFTP Client) ← Is my choice?
i must rename u-boot-update-2010.09-colibri_pxa320v20_TBin.bin to eboot.bin and flash it, is it right?
[R] Download nk.bin (using TFTP Client)
[W] Download mobm_bc.nb0 (using TFTP Client)
Download eboot.nb0 (using TFTP Client)
[Y] Download logo.bmp (using TFTP Client)
[Z] Download nk.nb0 (using TFTP Client)
[9] M3 T Information
[T] Test Menu
[B] Download image (using USB serial)
[J] Download and Jump to SDRAM(RNDIS)
[N] NAND tools
What is the difference between eboot.nb0 and eboot.bin?
eboot.nb0: This is a raw binary image of the bootloader, containing no headers or metadata.
eboot.bin: This file includes additional headers and metadata, conforming to specific formatting standards. It’s commonly utilized with higher-level flashing tools like the Update Tool, which interpret these headers to manage the flashing process appropriately.
Could you please specify the exact Colibri module you’re using, including its hardware (HW) revision?
