• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 2634 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: BOOTP broadcast crash in U-boot

newuser
Intellectual 630 points
Part Number: AM3352

Tool/software: Linux

I am using my customer board based on AM3352, DP83867 and for SDK  I am using evm-04.03.00.05 which has u-boot 2017.01

when I start DHCP, uboot is crashing with following error.

cpsw Waiting for PHY auto negotiation to complete......... done
link up on port 0, speed 1000, full duplex
BOOTP broadcast 1
data abort
pc : [<8ff9ba22>]          lr : [<00001a22>]
reloc pc : [<8082ea22>]    lr : [<f0894a22>]
sp : 8df4c940  ip : 00000000     fp : 8ffed188
r10: 8ffeccd0  r9 : 8df4ced8     r8 : 0000000e
r7 : 8ffef014  r6 : 8ffef01c     r5 : 00000000  r4 : 8ffed1ce
r3 : 00060101  r2 : 00000008     r1 : 8ffed18e  r0 : 0000000e
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32
Resetting CPU ...

resetting ...

U-Boot SPL 2017.01-svn182 (Jul 01 2018 - 23:16:59)
Trying to boot from SPI


U-Boot 2017.01-svn182 (Jul 01 2018 - 23:16:59 -0700)

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  256 MiB
************** phy_init ***************
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected mx25l12805 with page size 256 Bytes, erase size 64 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

<ethaddr> not set. Validating first E-fuse MAC
Net:   ************** phy_init ***************
*********** phy_dev_name=cpsw
cpsw
Hit any key to stop autoboot:  0
WARNING: Could not determine device tree to use
** First descriptor is NOT a primary desc on 0:1 **
switch to partitions #0, OK
mmc0(part 0) is current device
** First descriptor is NOT a primary desc on 0:1 **
SD/MMC found on device 0
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** First descriptor is NOT a primary desc on 0:1 **
switch to partitions #0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
** First descriptor is NOT a primary desc on 0:1 **
switch to partitions #0, OK
mmc0(part 0) is current device
** First descriptor is NOT a primary desc on 0:1 **
SD/MMC found on device 0
** No partition table - mmc 0 **
Card did not respond to voltage select!
Card did not respond to voltage select!
** First descriptor is NOT a primary desc on 0:1 **
SD/MMC found on device 1
Card did not respond to voltage select!
Card did not respond to voltage select!
** Bad device mmc 1 **
## Error: "bootcmd_nand0" not defined
cpsw Waiting for PHY auto negotiation to complete........user interrupt!
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-2c-6b-7d-56-22-1a
cpsw Waiting for PHY auto negotiation to complete..user interrupt!
Retrieving file: pxelinux.cfg/00000000
cpsw Waiting for PHY auto negotiation to complete. done
link up on port 0, speed 1000, full duplex
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/0000000
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/000000
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/00000
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/0000
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/000
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/00
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/0
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/default-arm-am33xx
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/default-arm
*** ERROR: `ipaddr' not set
Retrieving file: pxelinux.cfg/default
*** ERROR: `ipaddr' not set
Config file not found

  • 0
    TI__Mastermind 39460 points
    Hi,

    Let's concentrate on the data abort as everything appears to get worse after that. Could you please describe the board that you are using? You mentioned customer board, is that a custom board that your company designed? What kind of memory verification tests were done on the board to verify that the memory is valid?

    Best Regards,
    Schuyler
  • 0 in reply to Schuyler Patton
    Intellectual 630 points

    sorry, there was typo. it was not customer board but custom board.

    I am using gcc linaro 7.3.0.

    After adding compiler option "-fno-store-merging" i was able to move forward and I don't see any crash now. from DHCP server my board get the IP address.

    I want u-boot to do dhcp only and give me u-boot prompt, but it goes and execute further and try to get pxelinux and try to boot from external server. how can i disable that?

    Thanks,

  • 0
    Intellectual 630 points

    Part Number: AM3352

    Tool/software: Linux

    I have my custom board based on AM3352, with DP83867 PHY., toolchain - gcc 7.3.1(2018.05) hard float, linaro. U-Boot 2017.01 from ti-sdk.

    I want u-boot to use DHCP and get IP address from router. I can see it is able to aquire IP address from router (30.30.30.27)  after that it tries to load pxelinux.cfg/default and it fails.

    I couldn't understand , why it does that and how to prevent that.

    I just want u-boot to get IP address and u-boot command shell prompt to there to accept next command from user.

    dhcp
    link up on port 0, speed 1000, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 30.30.30.27 (114 ms)
    Using cpsw device
    TFTP from server 30.30.30.100; our IP address is 30.30.30.27
    Filename 'pxelinux.cfg/default'.
    Load address: 0x82000000
    Loading: T T T T T T T T T T T T T T T T T T T T
    Retry count exceeded; starting again

  • 0 in reply to newuser
    TI__Mastermind 39460 points
    Hi,

    If I am following correctly to do the ip address portion of the dhcp process use this command, followed by the dhcp:

    setenv autoload no
    dhcp

    That should stop the download process.

    Best Regards,
    Schuyler