Can't reprogram u-boot on sabre SDP

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Can't reprogram u-boot on sabre SDP

2,122 Views
jfsimon
Contributor III

Hi

My goal is to install android on the eMMC on the sabre SDP. Here is what I did:

-Boot the Sabre SDP under NFS

-partition the eMMC with this command:

       # mksdcard-android.sh /dev/mmcblk0

-Used the "dd" command to program u-boot, boot.img, system.img and recovery.img to eMMC

BUT I am unable to overwrite an older u-boot that is already on /dev/mmcblk0 with this command:

# dd if=<new u-boot.bin> of=/dev/mmcblk0 bs=1K skip=1 seek=1; sync

(the reason I need to replace the older u-boot is because it doesn't have the "booti" command.)

I also tried erasing it from u-boot but it doesn't work:

MX6SDL SABRESD U-Boot > mmc dev

Card did not respond to voltage select!

mmc0(part 0) is current device

MMC erase: dev # 0, block # 0, count 256 ... Card did not respond to voltage select!

raise: Signal # 8 caught

raise: Signal # 8 caught

mmc erase failed

0 blocks erase: ERROR

Any ideas?

Thanks a lot

-jf simon

0 Kudos
7 Replies

720 Views
LeonardoSandova
Specialist I

the dd command you have used should have erased any previous data you have starting at bs*seek. Also,One way to also 'erase' is to put zeros, meaning:

dd if=/dev/zero of=/dev/mmcblk0 seek=1 count=N

where N is the number of blocks you want to erase. By default blocks are 512 bytes.

Leo

0 Kudos

720 Views
jfsimon
Contributor III

Leo,

I agree it should, but it doesn't. No matter what I do 9and i have tried the dd if=/dev/zero...thing) I can't erase the following u-boot:

U-Boot 2009.08 (Jan 29 2013 - 11:33:44)

CPU: Freescale i.MX6 family TO1.1 at 792 MHz

raise: Signal # 8 caught

Temperature:   can't get valid data!

mx6q pll1: 792MHz

mx6q pll2: 528MHz

mx6q pll3: 480MHz

mx6q pll8: 50MHz

ipg clock     : 66000000Hz

ipg per clock : 66000000Hz

uart clock    : 80000000Hz

cspi clock    : 60000000Hz

ahb clock     : 132000000Hz

axi clock   : 198000000Hz

emi_slow clock: 22000000Hz

ddr clock     : 396000000Hz

usdhc1 clock  : 198000000Hz

usdhc2 clock  : 198000000Hz

usdhc3 clock  : 198000000Hz

usdhc4 clock  : 198000000Hz

nfc clock     : 24000000Hz

Board: i.MX6DL/Solo-SABRESD: unknown-board Board: 0x61011 [POR ]

Boot Device: MMC

I2C:   ready

DRAM:   1 GB

MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3

In:    serial

Out:   serial

Err:   serial

Found PFUZE100! deviceid=10,revid=11

Net:   got MAC address from IIM: 00:04:9f:02:68:10

FEC0 [PRIME]

Hit any key to stop autoboot:  0

MX6SDL SABRESD U-Boot >

Plus when I try to erase the MMC from u-boot it fails as follows:

MX6SDL SABRESD U-Boot > mmc rescan    

Card did not respond to voltage select!

MX6SDL SABRESD U-Boot > mmc bootpart

Card did not respond to voltage select!

Device 1: boot partition 0 is for boot

MX6SDL SABRESD U-Boot > mmc erase 0 100

MMC erase: dev # 1, block # 0, count 256 ... Card did not respond to voltage select!

raise: Signal # 8 caught

raise: Signal # 8 caught

mmc erase failed

0 blocks erase: ERROR

0 Kudos

720 Views
LeonardoSandova
Specialist I

You may be booting from the eMMC. in MX6Q, do you have the correct DIP switches to boot from SD? switches 2 and 7 ON and the rest OFF for SD3?

Leo

0 Kudos

720 Views
jfsimon
Contributor III

I usually set SW6 to boot from the SD. Then I boot linux over NFS. Then I try to program u-boot to the eMMC with dd. to make sure I am writing to the right device, I remove the SD card.

But even if I boot from eMMC like above, I should be able to use u-boot "mmc" commands to erase the eMMC right?

0 Kudos

720 Views
chenzhiwei
Contributor I

Hi jf..

I melt with the same problem... how you resolve these issues?

0 Kudos

720 Views
YixingKong
Senior Contributor IV

Jf

This discussion is closed since no activity. If you still need help, please feel free to reply with an update to this

discussion, or create another discussion.
Thanks,
Yixing

0 Kudos

720 Views
YixingKong
Senior Contributor IV

Jf

Had your issue got resolved? If yes, we are going to close the discussion in 3 days. If you still need help please feel

free to contact Freescale.

Thanks,
Yixing

0 Kudos