• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 631 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM5728: Android filesystem eMMC flashing script

AM5728: how to flash Android image on emmc ?

liqf sky
Intellectual 470 points
Part Number: AM5728
Other Parts Discussed in Thread: BEAGLEBOARD-X15,

I have a AM5728 custom board.

The SDK version: ti-processor-sdk-android-am57xx-evm-06.03.00.106-Linux-x86-Install.bin

system : Ubuntu 18.04


I follow http://software-dl.ti.com/processor-sdk-android/esd/docs/latest/android/Overview_Getting_Started_Guide.html#run-setup-scripts  Run Setup Scripts

......................................................................................................................

skyliqf@skyliqf-System-Product-Name:~/workhome/ti-processor-sdk-android-am57xx-evm-06.03.00.106$ ./setup.sh
Just a simple wrapper over the fastboot.sh to set the appropriate paths.

--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development


For boards that contain a USB-to-Serial converter on the board such as:
* BeagleBone
* Beaglebone Black
* AM335x EVM-SK
* AM57xx EVM
* K2H, K2L, and K2E EVMs

the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.

For other boards, the serial will defualt to /dev/ttyS0. Please update based
on your setup.

--------------------------------------------------------------------------------


NOTE: If your using any of the above boards simply hit enter
and the correct port will be determined automatically at a
later step. For all other boards select the serial port
that the board is connected to.
Which serial port do you want to use with minicom?
[ /dev/ttyUSB0 ]

Copied existing /home/skyliqf/.minirc.dfl to /home/skyliqf/.minirc.dfl.old

Configuration saved to /home/skyliqf/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Would you like to create a minicom script to configure the board (y/n)?
[ y ]

Successfully wrote /home/skyliqf/workhome/ti-processor-sdk-android-am57xx-evm-06.03.00.106/bin/setupBoard.minicom

Board could not be detected. Please connect the board to the PC.
Press any key to try checking again.

Board could not be detected. Please connect the board to the PC.

Press any key to try checking again.

.................................................................................................


I use uart3 to connect to pc. I can recognize the serial device.

.....................................................................................................

skyliqf@skyliqf-System-Product-Name:~$ ls /dev/ttyUSB*
/dev/ttyUSB0
skyliqf@skyliqf-System-Product-Name:~$

....................................................................................................

Enter  $ sudo minicom  in the terminal to connect to the board.

Why does it prompt "Board could not be detected. Please connect the board to the PC" when running setup.sh?

  • 0
    Intellectual 470 points

    After performing steps 5 and 6, the micro USB device cannot be checked on the pc.

    Now running setup.sh can't recognize the micro USB device, is there any other way for ti to flash Android image on emmc ?

  • 0 in reply to liqf sky
    TI__Expert 6256 points

    1. can you try copying MLO and u-boot.img from the prebuilt images into a FAT partition in SDcard and see if the device boots atleast to bootloader prompt?

    2. if it boots , do lsusb and see if USBport is detected ( Note: FTDI to usb for serial log and microusb beside sd card slot is the one to usb for fastboot).

    3. if you see USB port detected, do "sudo ./fastboot devices" from host machine (you can find the prebuilt fastboot binary in the prebuilt images ) . this command should show some serial id and say fastboot detected.

    4. run the steps documented in release notes on how to flash images in emmc ( the commands which show : format with partition table and running the script https://git.ti.com/cgit/android/device-ti-beagle-x15/tree/fastboot.sh?h=d-pie-core-release )

  • 0 in reply to Praneeth Bajjuri
    Intellectual 470 points

    I copied MLO and u-boot.img from the prebuilt images to SD card.

    Boot from the SD card.When doing lsusb, the USB port is not detected.

    The following is the print log.

    ..................................................................................................................................

    U-Boot SPL 2019.01-g333c3e72d3 (Apr 19 2020 - 06:06:00 +0000)
    DRA752-GP ES2.0
    ** Unable to read file dra7-ipu1-fw.xem4 **
    Firmware loading failed
    Trying to boot from MMC1
    Loading Environment from FAT... OK


    U-Boot 2019.01-g333c3e72d3 (Apr 19 2020 - 06:06:00 +0000)

    CPU : DRA752-GP ES2.0
    Model: TI AM5728 BeagleBoard-X15
    Board: UNKNOWN(BeagleBoard X15?) REV UNKNOWN
    DRAM: 2 GiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    Loading Environment from FAT... OK
    Warning: fastboot.board_rev: unknown board revision
    am57x_idk_lcd_detect: Failed to get I2C device 0/56 (ret 1)
    Net: 
    Warning: ethernet@48484000 using MAC address from ROM
    eth0: ethernet@48484000
    Hit any key to stop autoboot: 0 
    switch to partitions #0, OK
    mmc0 is current device
    SD/MMC found on device 0
    ** Unable to read file boot.scr **
    1394 bytes read in 3 ms (453.1 KiB/s)
    Loaded env from uEnv.txt
    Importing environment from mmc0 ...
    Running uenvcmd ...
    1 bytes read in 2 ms (0 Bytes/s)
    Already setup.
    switch to partitions #0, OK
    mmc0 is current device
    SD/MMC found on device 0
    ** Unable to read file /zImage **
    Trying to boot Linux from eMMC ...
    switch to partitions #0, OK
    mmc1(part 0) is current device
    SD/MMC found on device 1
    ** File not found /zImage **
    Trying to boot Android from eMMC ...
    switch to partitions #0, OK
    mmc1(part 0) is current device
    mmc - MMC sub system

    Usage:
    mmc info - display info of the current MMC device
    mmc read addr blk# cnt
    mmc write addr blk# cnt
    mmc erase blk# cnt
    mmc rescan
    mmc part - lists available partition on current mmc device
    mmc dev [dev] [part] - show or set current mmc device [partition]
    mmc list - lists available devices
    mmc hwpartition [args...] - does hardware partitioning
    arguments (sizes in 512-byte blocks):
    [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes
    [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition
    [check|set|complete] - mode, complete set partitioning completed
    WARNING: Partitioning is a write-once setting once it is set to complete.
    Power cycling is required to initialize partitions after set to complete.
    mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode
    - Set the BOOT_BUS_WIDTH field of the specified device
    mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB>
    - Change sizes of boot and RPMB partitions of specified device
    mmc partconf dev [boot_ack boot_partition partition_access]
    - Show or change the bits of the PARTITION_CONFIG field of the specified device
    mmc rst-function dev value
    - Change the RST_n_FUNCTION field of the specified device
    WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values.
    mmc setdsr <value> - set DSR register value

    Wrong Image Format for bootm command
    ERROR: can't get kernel image!
    => 
    =>

    ...................................................................................................................................................................

    This is my schematic diagram.

    R321 is disconnected. When I connect the USB, VBUS_DET is 3.3V.

    DJ-AM57X-USB.pdf

    lsusb cannot detect USBPOST, is there a problem with my hardware?