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.

AM335X ZCZ Base Board + Linux SDK

Hi,

Need help for booting EVM. Please let me know if any other information is required.

While trying to boot the AM335X ZCZ Base Board, Rev 1.4A with the following prebuilt:
Ø u-boot-2013.01.01-psp06.00.00.00/u-boot.img
Ø uImage-am335x-evm.bin
I'm getting the following in the console:
U-Boot SPL 2013.01.01 (Jun 25 2013 - 16:42:52)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.01.01 (Apr 10 2014 - 19:02:03)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   cpsw, usb_ether
Hit any key to stop autoboot:  3 ___ 0
U-Boot#
U-Boot#
U-Boot#
U-Boot#
U-Boot#
U-Boot#
U-Boot# print fboot
fboot=echo Booting from network ...; setenv autoload no; dhcp; tftp ${loadaddr} ${bootfile};run mmcargs; bootm ${loadaddr} - -;
U-Boot# print bootfile
bootfile=tftp/prebuilt_uImage
U-Boot# print mmcargs
mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot} rootfstype=${mmcrootfstype}
U-Boot# print console
console=ttyS0,115200n8
U-Boot# print mmcroot
mmcroot=/dev/mmcblk0p2 ro
U-Boot# run fboot
Booting from network ...
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 10.100.1.71
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 10.100.1.135; our IP address is 10.100.1.71
Filename 'tftp/prebuilt_uImage'.
Load address: 0x80400000
Loading: *_#################################################################
      #################################################################
      #################################################################
      #######################
      380.9 KiB/s
done
Bytes transferred = 3194336 (30bde0 hex)
## Booting kernel from Legacy Image at 80400000 ...
   Image Name:   Linux-3.2.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3194272 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK

  • Are you trying to boot only the EVM baseboard? What exactly is the problem? You have posted only a log file. Please explain.

  • We are using the GPEVM base board and the daughter board (1.2a ). The issue is that, while trying to boot Linux from U-boot after the "Verifying Checksum ... OK" message, the system is hang. No more messages coming up on the serial port. 

  • What are your dipswitch settings (SW3 and SW4 for boot mode, SW8 on daughterboard for EVM profile)?

  • Hi Sankar,

    Which version of the SDK are you using and where did you get the uImage file you are loading?

    Please do a hexdump of the first 100 bytes of this file and post it here:

    hexdump -C -n100 uImage

    Best regards,
    Miroslav

  • Hi Miroslav,

    Here is the output. Please let me know if you need any other information.

    SDK version used: ti-sdk-am335x-evm-06.00.00.00

    :~/ti-sdk-am335x-evm-06.00.00.00/board-support/prebuilt-images$ hexdump -C -n200 uImage-am335x-evm.bin
    00000000  27 05 19 56 e9 a0 91 54  51 ca 0e 66 00 30 bd a0  |'..V...TQ..f.0..|
    00000010  80 00 80 00 80 00 80 00  0f 50 d6 3a 05 02 02 00  |.........P.:....|
    00000020  4c 69 6e 75 78 2d 33 2e  32 2e 30 00 00 00 00 00  |Linux-3.2.0.....|
    00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    00000040  00 00 a0 e1 00 00 a0 e1  00 00 a0 e1 00 00 a0 e1  |................|
    *
    00000060  02 00 00 ea 18 28 6f 01  00 00 00 00 a0 bd 30 00  |.....(o.......0.|
    00000070  01 70 a0 e1 02 80 a0 e1  00 20 0f e1 03 00 12 e3  |.p....... ......|
    00000080  01 00 00 1a 17 00 a0 e3  56 34 12 ef 00 20 0f e1  |........V4... ..|
    00000090  c0 20 82 e3 02 f0 21 e1  00 00 00 00 00 00 00 00  |. ....!.........|
    000000a0  84 47 9f e5 55 00 00 eb  4a 0f 8f e2 4e 1c 90 e8  |.G..U...J...N...|
    000000b0  1c d0 90 e5 01 00 40 e0  00 60 86 e0 00 a0 8a e0  |......@..`......|
    000000c0  00 90 da e5 01 e0 da e5                           |........|
    000000c8

  • Sankar, the uImage header is correct.

    I can see that you have re-built the U-Boot and you are not using the pre-built U-Boot image from the SDK package. Have you done any modifications? Please try this using the pre-built U-Boot from the SDK package.

    Best regards,
    Miroslav

  • Hi Miroslav,

    We didn't do any modifications on the U-Boot. We just built it. If we use the pre-built image it doesn't give any serial port messages, that is the reason we tried to built.
    Looking forward to resolve this issue asap.

  • Which UART port are you using for the serial console?

    Which make target did you use to build U-Boot? I can verify that the pre-built U-Boot image file works absolutely correct with the AM335x GP EVM when using UART0 for the serial console.

    You can also try rebuilding the kernel with CONFIG_DEBUG_LL option enabled and see if any useful debug messages appear.

    Best regards,
    Miroslav

  • We are using UART0. Our interpretation is that it not yet transferred the control to Kernel, and it hangs in U-Boot itself. Because, we should get a message "Loading kernel" which is not coming.

    Both the pre-built image and the image that we built using the command "make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf - am335x_evm"