BEAGLEBN: Ethernet boot and flashing eMMC problems

Miguel S

Part Number: BEAGLEBN

Hi,

I have a BBB and I want to flash the eMMC from Ethernet.

I have modified the hardware, so the AM3358 is configured to boot from Eth. This hardware modification is ok, since the process of eth booting starts correctly.

I also have been following this guide:

My Processor SDK Linux is 05_01_00_11.

I have encountered the above link a little out of date, with respect with my SDK. So, first, I have the following questions:

"Creating and Gathering the Run-Time Files" section: I have not used the suggested patch: 0001-Change-finduuid-to-use-mmcdev.patch.gz, as I am getting some errors when applying it. It seems that it is an old patch and it may now not make sense. Am I right?
I get an error when compiling u-boot for 'am335x_boneblack_config'. I have used 'am335x_evm_defconfig' instead. Is this ok?
Preparing the flasher image --> Create a Network Bootable U-Boot Image: as I have just built u-boot for 'am335x_evm_defconfig' without the patch. I have used the previously generated 'u-boot.img' as 'u-boot-restore.img', and 'spl/u-boot-spl.bin' as 'spl/u-boot-spl-restore.bin'. Is this correct?

Finally, I am using CCS UniFlash 3.4.1.00012. The process of Ethernet booting starts but the eMMC is not flashed

I the serial port console:

I see 'missing environment variable: pxeuuid' How can I solve this?
Finally, the last message I see is 'EFI stub: Exiting boot services and installing virtual address map...'. Any clue about why it is not progressing?

I would really appreciate any help on this.

Here is the console output:

CCCCCCCC
U-Boot SPL 2018.01-00444-g96cdbefd5c (Nov 22 2018 - 12:37:04)
Trying to boot from eth device
** Bad device mmc 0 **
Using default environment

<ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Error: usb_ether address not set.

cpsw Waiting for PHY auto negotiation to complete... done
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.100.2 (5 ms)
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'u-boot-restore.img'.
Load address: 0x82000000
Loading: #################################################################
##############################################################
1.6 MiB/s
done
Bytes transferred = 646056 (9dba8 hex)

U-Boot 2018.01-00444-g96cdbefd5c (Nov 22 2018 - 12:37:04 +0100)

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
** Bad device mmc 0 **
Using default environment

<ethaddr> not set. Validating first E-fuse MAC
Net:   cpsw, usb_ether
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
** Invalid partition 2 **
## Error: "bootcmd_nand0" not defined
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.100.2 (4 ms)
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'zImage'.
Load address: 0x82000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###################
         3.4 MiB/s
done
Bytes transferred = 6951424 (6a1200 hex)
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-c8-df-84-d6-aa-0a
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/01-c8-df-84-d6-aa-0a'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (1)
Not retrying...
Retrieving file: pxelinux.cfg/C0A86402
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0A86402'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (1)
Not retrying...
Retrieving file: pxelinux.cfg/C0A8640
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0A8640'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (1)
Not retrying...
Retrieving file: pxelinux.cfg/C0A864
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0A864'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (1)
Not retrying...
Retrieving file: pxelinux.cfg/C0A86
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0A86'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0A8'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0A'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C0'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/C'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/default-arm-am33xx'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/default-arm'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.1; our IP address is 192.168.100.2
Filename 'pxelinux.cfg/default'.
Load address: 0x80100000
Loading: *
TFTP error: 'File not found or No Access' (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.100.2 (5 ms)
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'zImage'.
Load address: 0x80000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###################
         3.4 MiB/s
done
Bytes transferred = 6951424 (6a1200 hex)
## Executing script at 80000000
Wrong image format for "source" command
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.100.2 (9 ms)
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'zImage'.
Load address: 0x82000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###################
         3.1 MiB/s
done
Bytes transferred = 6951424 (6a1200 hex)
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.100.1; our IP address is 192.168.100.2
Filename 'dtb/am335x-boneblack.dtb'.
Load address: 0x88000000
Loading: ###
         1.3 MiB/s
done
Bytes transferred = 36793 (8fb9 hex)
## Starting EFI application at 82000000 ...
Scanning disks on usb...
Scanning disks on mmc...
MMC Device 2 not found
MMC Device 3 not found
Found 6 disks
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

over 5 years ago

0 Miguel S over 5 years ago

Intellectual 780 points

Any updates on this, please?

Best Regards,

Miguel

0 Bin Liu over 5 years ago in reply to Miguel S

TI__Guru*** 125446 points

Hi Miguel,

Sorry for the delay. The expert supporting the UniFlash tool is out of the office for about two weeks.

0 Miguel S over 5 years ago in reply to Bin Liu

Intellectual 780 points

Thanks for your reply.

I am not sure that the problem is with UniFlash, do you think so?

On the other hand, regarding my initial questions:

2. Looking into the '/board-support/u-boot.../configs' folder, I have seen a configuration called 'am335x_boneblack_defconfig'. So, I have used that one instead of 'am335x_boneblack_config'.

So, finally, I am using 'am335x_boneblack_defconfig' (without any patches) for the image to be flashed, and 'am335x_evm_defconfig' for the flasher image. Is this correct?

Regards,

Miguel

0 Bin Liu over 5 years ago in reply to Miguel S

TI__Guru*** 125446 points

Hi Miguel,

I am not an expert on the UniFlash tool, but I doubt the problem is with UniFlash itself, since the log you provided show files are downloaded to the am335x board in Uboot, so it is more likely to be a problem in Uboot image preparation related. But I am not familiar with the UniFlash process to give you more accurate comments.

0 Miguel S over 5 years ago in reply to Bin Liu

Intellectual 780 points

Ok, thanks for your reply.

I will keep waiting for the UniFlash expert answer :-)

Miguel

0 RonB over 5 years ago in reply to Miguel S

TI__Mastermind 30276 points

Hi Miguel,

Miguel S said:

So, finally, I am using 'am335x_boneblack_defconfig' (without any patches) for the image to be flashed, and 'am335x_evm_defconfig' for the flasher image. Is this correct?

Yes, that should be correct. Are you still seeing the same problems?

0 Miguel S over 5 years ago in reply to RonB

Intellectual 780 points

Hello,

Yes, I am having the same problem.

Regards,
Miguel

0 RonB over 5 years ago in reply to Miguel S

TI__Mastermind 30276 points

Hi MIguel,

Can you try stopping U-boot at the prompt and running these two commands:

run findfdt
run netboot

This should get you booted to your zImage. However the document also talks about a tiny filesystem to use as an initramfs in order to run your flasher routine. Do you have that?

Processors

Processors forum

BEAGLEBN: Ethernet boot and flashing eMMC problems