Home › Forums › MOCHAbin Forum › Hardware discussions › Better WIKI documentation?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #50334
    Anonymous
    Inactive

    Seems the WIKI was put together in a hurry and lacks a lot of common/simple details.

    For example based on this page it lacks simple common details for users to figure out how to boot of different devices.
    https://espressobin.net/mochabin_wiki/tiki-index.php?page=Jumpers+Setup

    None state how to boot from USB thumbnail.

    Please put effort into proper and detailed documentation that is understandable. The device is pretty much a paperweight without good documentation!

    #50513
    dhliu
    Keymaster

    The 88F7040 CPU supports multiple interface boot modes, but depending on the hardware configuration, Mochabin only supports 2 boot modes.

    1. SPI FLASH boot-up
    Currently using SPI FLASH for booting up

    2. UART boot-up
    This method is only applicable to recovery in case the boot image has been damaged and won’t boot up anyhow.
    Use this method to boot up from UART then load the bootloader image from PC and re-burn the bootloader image into SPI FLASH in Mochabin.
    Please use the script below to do the recovery.

    https://github.com/globalscaletechnologies/u-boot-marvell/blob/u-boot-2018.03-armada-18.12-gti/tools/mrvl_uart.sh

    ex. mrvl_uart.sh /dev/ttyUSB0 flash-image.bin

    Although Mochabin cannot boot up from USB drive but it can load root-fs image from USB after boot up, the description will be put here later.

    #50514
    dhliu
    Keymaster

    How to Load root-fs image from USB after boot-up with ubuntu OS

    1. Make an ext4 partition in usbdisk
    2. Extract GTI official Ubuntu rootfs directly to ext4 partition
    3. Modify u-boot bootcmd

    env default -a

    setenv image_name boot/Image
    setenv fdt_name boot/armada-7040-mochabin.dtb
    setenv bootcmd ‘usb reset; part uuid usb 0:1 partuuid; load usb 0:1 $kernel_addr_r $image_name; load usb 0:1 $fdt_addr_r $fdt_name; setenv bootargs $console root=PARTUUID=$partuuid rw rootwait net.ifnames=0 biosdevname=0 $extra_params; booti $kernel_addr_r – $fdt_addr_r’

    saveenv
    boot

    4. More to say,

    The above “load USB 0:1” represents USB device 0, partition 1. If ext4 partition is not in partition 1, it needs to be corrected accordingly
    In addition, when U-boot captures USB disks, sometimes it doesn’t capture USB storage somehow, so you need to perform USB reset to retrieve it again

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.
Signup to our newsletter

Technical specification tables can not be displayed on mobile. Please view on desktop