by technosf » Fri Dec 15, 2017 12:55 am
Running ALARM from an SSD on my EXPRESSObin, I had to modify the install a tad as the image and instruction focus on using MMC as storage. The modifications effect:
$this->bbcode_list('1')
Changing references from 'mmc' to 'scsi'Reseting the scsi bus at boot to make the sata devices visibleNot overlay the firmware env values from the image file /boot/uEnv.txtSteps:
$this->bbcode_list('1')Exploded the Arch EXPRESSObin image per the install instruction onto the target SSD on a seperate machine, then plugged it into the EXPRESSObinHooked the EXPRESSObin console up to the local machine and using picocom (picocom -b 115200 -r -l /dev/ttyUSB0) Updating the flash environment from the Marvell>> prompt:
$this->bbcode_second_pass_code('', '
env set get_env 'if test -n ${uenvcmd}; then run uenvcmd; fi'
env set get_images 'ext4load scsi 0 $kernel_addr $image_name && ext4load scsi 0 $fdt_addr $fdt_name'
env set get_ramdisk 'ext4load scsi 0 $ramdisk_addr $ramdisk_name'
env set bootargs 'console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/sda1 rw rootwait'
env set bootcmd 'scsi reset; scsi dev 0; run get_env; if run get_images; then if run get_ramdisk; then booti $kernel_addr $ramdisk_addr $fdt_addr; else booti $kernel_addr - $fdt_addr; fi; fi'
') Save the environment and boot:
$this->bbcode_second_pass_code('', '
saveenv
boot
')Bingo!
[size=85] MochaBin 5G || NSA325 [/size]