...
Download the Ubuntu Desktop OS image from release page. The following steps apply to both Ubuntu Desktop and Ubuntu Server (WIP).
Extract the Ubuntu image first, and then extract the boot firmware into the same directory. On Ubuntu host PC this can be done with the following commands:
Code Block language bash tar -xvf Ubuntu-jammy-*.tar.xz tar --strip-components=1 -xvf {BOOT_FIRMWARE}.tar.gz -C {UBUNTU_IMAGE}/ cd Ubuntu-jammy-*
The resulting image directory should contain at least these files:
Code Block $ ls bl2.img bootassets.vfat fip.bin firmware.vfat lk.bin u-boot-initial-env ubuntu-seco.img writable-seco.img ubuntu.json
Check the following lines in the
u-boot-initial-env
file. They are responsible device tree overlays which will be applied. You can remove or add overlays from the list.Code Block conf ... list_dtbo= gpu-mali.dtbo video.dtbo apusys.dtbo
You can also set the MAC address at the boot time, which will be saved in the bootloader config. You can do so by adding a new line to
u-boot-initial-env
file:Code Block ethaddr=00:55:7b:b5:7d:f7
Connect the Baseboard with SOM-SMARC-Genio700 module to PC. Open a terminal application on your host PC and connect to the serial device (converter name). Make sure you set the following parameters on your terminal application:
baud rate: 921600
8-bit
Party bit: 1
No flow control
Launch a command line prompt on your host PC.
First change directory(cd
) to the image directory, and rungenio-flash
:Code Block cd {UBUNTU_IMAGE} genio-flash
The tool should have the following output:
Code Block genio-flash AIoT Tools: v1.3.4 Ubuntu Image: ... Looking for MediaTek SoC matching USB device 0e8d:0003 ...
The line
Looking for MediaTek SoC matching USB device 0e8d:0003
shows thatgenio-flash
tool is waiting for the board to be reset into download mode to start the flash programming procedure.Set the board into download mode
Describe the procedure hereFor REV A0 modules on B79 Baseboard:
Set the SW14 switch 2 to ON to enter the Serial Download mode
For later revisions on B79 Baseboard:
Set SW12 and SW13 to correct position. Please consult with B79 datasheet or the Embedded Controller page: https://secogroup.atlassian.net/wiki/spaces/SECONorthTech/pages/1618772032/STM32+MCU+-+WILK#Carrier-board-BOOT_SEL-configurationThe flash tool should continue with the following log output, which shows the progress of erasing the onboard storage and writing image content to the storage:
Code Block Erasing 'mmc0' (bootloader) request sz: 0xece000000, real erase len: 0x0 OKAY [ 1.432s] Finished. Total time: 7.869s erasing mmc0boot0 Erasing 'mmc0boot0' (bootloader) request sz: 0x400000, real erase len: 0x400000 OKAY [ 0.010s] Finished. Total time: 0.015s erasing mmc0boot1 Erasing 'mmc0boot1' (bootloader) request sz: 0x400000, real erase len: 0x400000 OKAY [ 0.007s] Finished. Total time: 0.013s flashing mmc0=ubuntu.img Sending sparse 'mmc0' 1/17 (261522 KB) OKAY [ 7.267s] Writing 'mmc0' OKAY [ 17.980s] Sending sparse 'mmc0' 2/17 (261674 KB) OKAY [ 7.123s] ...
If you are using a Windows host PC, and the tool stops at the output line < waiting for any device >
, please follow the steps in this trouble shooting page to solve an underlying Windows driver issue.
...