uboot write by uniflash ( beaglebone black )

Please see this wiki: http://processors.wiki.ti.com/index.php/Sitara_Linux_AM335x_Flash_Programming_Linux_Development

The wiki states that a template for flasher.sh is provided with Uniflash.

I do not know what that means. Anything sample flasher.sh?

Have you done these steps:http://processors.wiki.ti.com/index.php/Sitara_Linux_Program_the_eMMC_on_Beaglebone_Black#Flash_the_Beaglebone_Black ? Please post console output.

Do not see any console output. If so, h/w is the problem?

I had to change the boot sequence. ( SYSBOOT[4:0] : 11100b -> 01100b )

Below are additional changes made to me.

uboot restore image create :

  make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=flasher_usb am335x_evm_usbspl_config all

  cp u-boot.img /tftpboot/u-boot-restore.img

  cp spl/u-boot-spl.bin /tftpboot/u-boot-spl-restore.bin

flasher.sh modify :

  #DRIVE="/dev/mmcblk0"
  DRIVE="/dev/mmcblk1"

cp flasher.sh debrick.sh

I have asked the SW team to help on this.

Hi,

ahn said:

I had to change the boot sequence. ( SYSBOOT[4:0] : 11100b -> 01100b )

Beaglebone black is configured by default to boot from EMMC and has NO sysboot switches, holding the boot switch S2 should be enough.  Moreover the sysboot settings you're using (according to Table 26-7. SYSBOOT Configuration Pins of AM335x TRM) configure AM335x to boot from USB0, NAND or XIP, and BBB has eMMC which is connected to MMC1, so you set your sysboot[4:0] to boot from MMC1 (emmc boot should be the default for BBB).

Also I thing you should not modify the flasher.sh script, but use it as is: https://gforge.ti.com/gf/download/frsrelease/1215/7493/flasher.tar.gz  

ahn said:

Do not see any console output. If so, h/w is the problem?

Is there a way for you to boot from SDCard, if yes try and see if you get any console output, this will show you if there is a hw problem with your board. 

Best Regards, 
Yordan

I can't decompress the flasher.tar.gz

# tar xf flasher.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

# tar zxf flasher.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

anyway,

spi (uboot) + nand (kernel, rootfs) is planning to design a circuit.

How did the usb boot in this case?

Find the file attached:

flasher.tar.gz

Best Regards,

Yordan

Ahn,

It appears that the PC running Uniflash is not seeing the BOOTP messages from the board. So, either they are not coming across the USB/RNDIS interface or the server inside Uniflash is not configured correctly to respond to the messages. Wireshark should be very useful to help determine if the packets are being seen on the PC.

Do you see the ethernet interface for RNDIS get created on the PC? If not, the RNDIS driver is not configured correctly on the PC side. if the interface does show up, is it configured to have the correct static IP address?

Since it appears you were able to transfer SPL correctly, I'm wondering if you've configured the second USB/RNDIS driver correctly. The interface has to be configured twice (once for the boot ROM, and again for U-Boot).