• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 605 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Froyo Dev Kit v2.2 Burn to NAND Failure

Sean Ulrich
Prodigy 125 points

Other Parts Discussed in Thread: AM3517

Hello,

I am cross posting this from the ARM forum of E2E in hopes that someone here can help.

I have compiled a small footprint version of Rowboat Android and want to have the entire system running from NAND.  I have burned u-boot and uImage successfully but am having issues creating the YAFFS2 filesystem and burning it to the NAND on the am3517evm.  Does anyone have experience doing this and can provide some guidance for how I go about creating the image, and then burning it from the mmc?

For now, I have reverted to using the TI Froyo Dev Kit v2.2 PREBUILT xloader, uboot, uImage, and rootfs to make an SD card (with the flash_eraseall and  prebuilt rootfs.tar.bz2 also stored on the card) then booting the card.  After that I am trying to executed the instructions given here:

http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide#NAND_Booting

However, it fails to mount the filesystem as yaffs2.  Here is my command line output:

# cat /proc/mtd 
dev:    size   erasesize  name 
mtd0: 00080000 00020000 "xloader-nand" 
mtd1: 001c0000 00020000 "uboot-nand" 
mtd2: 00040000 00020000 "params-nand" 
mtd3: 00500000 00020000 "linux-nand" 
mtd4: 0f880000 00020000 "jffs2-nand" 

After using flash_eraseall to erase mtd4, here is where the issue is 
occuring: 

# mkdir /tempd 
# mount -t yaffs2 /dev/block/mtdblock4 /tempd 
mount: No such device 
# ls /dev/block/mtd* 
/dev/block/mtdblock0 
/dev/block/mtdblock1 
/dev/block/mtdblock2 
/dev/block/mtdblock3 
/dev/block/mtdblock4 

As you can see, even though /dev/block/mtdblock4 and tempd exist, the mount command fails.  If I try "mount -t jffs2 /dev/block/mtdblock4 /tempd" it succeeds.  To me, this points to an issue that the default build of the TI Froyo Dev Kit v2.2 does not support YAFFS2.  Can someone advise to the changes I need to make to the kernel?  Or maybe even a different process I might follow to make this succeed? 

Thanks, 
Sean

  • 0
    Intellectual 325 points

    Kindly send the complete boot log right from x-loader and u-boot loading. That will help in getting the board revision you are working on. The board which I have tested today has 512MB NAND. You seem to be working on a different revision of board which has 256MB NAND. I will try to get my hands on the board revision which you are using and try to reproduce this bug. As of now the procedure is working fine on my revision of the AM3517 EVM board.

    Meanwhile can you also give the YAFFS2 flashing procedure a try from a non-Android rootfs e.g. Arago or Angstrom?
     
    Regards,
    Amit Pundir

  • 0
    Prodigy 125 points

    Just closing the loop on this issue.  Short story is I switched to one of "known good" SD cards from the wiki, and then had install busybox.  Full explanation of the solution can be found on my post at the Rowboat forum.

     

    Thanks,

    Sean