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.

Linux/AM3352: Kernel booting problem

Part Number: AM3352


Tool/software: Linux

Hi,

We are working on our first custom board with AM3352. It is based on Beagle Bone Black and added some other peripherals. I hard code EERPOM values, rebuild U-boot and download u-boot successfully to the board from UART. But the board hangs after "Starting Kernel...". SD on the board is not working. All code is running in SDRAM. I use the latest SDK 4.0.0.04 from TI website. I changed device tree several time but no luck. Later I delete everything in the device tree but only keep UART0, Ethernet 0 and I2C0. It is still the same.

CCCCC

U-Boot SPL 2017.01-00319-g7752743-dirty (Aug 09 2017 - 18:12:32)

name tag: A335BONE

eeprom name: A335BNLT

name tag: A335BONE

eeprom name: A335BNLT

Timed out in wait_for_event: status=0000

Check if pads/pull-ups of bus are properly configured

Trying to boot from UART

CCm - CRC mode, 4981(SOH)/0(STX)/0(CAN) packets, 5 retries

Loaded 637068 bytes

boot_from_devices: return 0

U-Boot 2017.01-00319-g7752743-dirty (Aug 09 2017 - 18:12:32 -0500)

CPU : AM335X-GP rev 2.1

Model: TI AM335x BeagleBone Black

DRAM: 512 MiB

NAND: 0 MiB

MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1

Card did not respond to voltage select!

** Bad device mmc 0 **

Using default environment

<ethaddr> not set. Validating first E-fuse MAC

Net: name tag: A335BONE

eeprom name: A335BNLT

cpsw, usb_ether

Hit any key to stop autoboot: 0

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

## Error: "bootcmd_nand0" not defined

starting USB...

USB0: Port not available.

link up on port 0, speed 100, full duplex

BOOTP broadcast 1

BOOTP broadcast 2

BOOTP broadcast 3

DHCP client bound to address 192.168.2.2 (1065 ms)

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'zImage'.

Load address: 0x82000000

Loading: #################################################################

#################################################################

#################################################################

############################

2.7 MiB/s

done

Bytes transferred = 3269680 (31e430 hex)

missing environment variable: pxeuuid

Retrieving file: pxelinux.cfg/01-e8-eb-11-2c-7e-cf

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/01-e8-eb-11-2c-7e-cf'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0A80202

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0A80202'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0A8020

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0A8020'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0A802

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0A802'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0A80

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0A80'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0A8

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0A8'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0A

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0A'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C0

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C0'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/C

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/C'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/default-arm-am33xx

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/default-arm-am33xx'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/default-arm

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/default-arm'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Retrieving file: pxelinux.cfg/default

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'pxelinux.cfg/default'.

Load address: 0x80100000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Config file not found

starting USB...

USB0: Port not available.

link up on port 0, speed 100, full duplex

BOOTP broadcast 1

DHCP client bound to address 192.168.2.2 (4 ms)

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'boot.scr.uimg'.

Load address: 0x80000000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

link up on port 0, speed 100, full duplex

BOOTP broadcast 1

DHCP client bound to address 192.168.2.2 (5 ms)

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'boot.scr.uimg'.

Load address: 0x82000000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

=>

=> tftp 0x88000000 am335x-boneblack.dtb

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'am335x-boneblack.dtb'.

Load address: 0x88000000

Loading: ##

1.2 MiB/s

done

Bytes transferred = 27984 (6d50 hex)

=> tftp 0x82000000 zImage

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 192.168.2.1; our IP address is 192.168.2.2

Filename 'zImage'.

Load address: 0x82000000

Loading: #################################################################

#################################################################

#################################################################

############################

2.7 MiB/s

done

Bytes transferred = 3269680 (31e430 hex)

=> bootz 0x82000000 - 0x88000000

## Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000

Loading Device Tree to 8fff6000, end 8ffffd4f ... OK

Starting kernel ...

Thanks,

Mingshu