Could anyone know how access yaffs2 fs from usb-slave ?
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <davinci-linux-open-source@linux.davincidsp.com>
Sent: Sunday, October 19, 2008 1:00 AM
Subject: Davinci-linux-open-source Digest, Vol 34, Issue 80
> Send Davinci-linux-open-source mailing list submissions to
> davinci-linux-open-source@linux.davincidsp.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
> or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
> You can reach the person managing the list at
> [EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Davinci-linux-open-source digest..."
>
>
> Today's Topics:
>
> 1. AW: Uboot large UImage (DISTEC Kiermaier Dieter)
> 2. Help on accessing CS2/3/4 address spaces on DM6446 (Nitin Joshi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 18 Oct 2008 11:07:07 +0200
> From: "DISTEC Kiermaier Dieter" <[EMAIL PROTECTED]>
> Subject: AW: Uboot large UImage
> To: "Joshua Hintze" <[EMAIL PROTECTED]>, "Stephen Berry"
> <[EMAIL PROTECTED]>, <davinci-linux-open-source@linux.davincidsp.com>
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello together,
>
> AFAIK u-boot is smart enough to handle bad blocks if you use
> nand erase.jffs2 / read.jffs2 commands instead of plain
> nand write / erase / read. Sorry, but I don't know the correct
> syntax of the commands because I don't have a board here right now.
> But a nand help at the u-boot prompt should point out the correct syntax.
>
> Best regards,
> Dieter
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] im Auftrag von Joshua Hintze
> Gesendet: Sa 18.10.2008 04:10
> An: 'Stephen Berry'; davinci-linux-open-source@linux.davincidsp.com
> Betreff: RE: Uboot large UImage
>
> Thank you Steve.
>
>
>
> When I performed the erase it did not indicated any bad blocks. Is there a
> way to test for bad blocks? I don't think it is bad blocks however since
> both of our Davinci boards do this.
>
>
>
> Josh
>
>
>
> From: Stephen Berry [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 17, 2008 6:57 PM
> To: Joshua Hintze; davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: Uboot large UImage
>
>
>
> Did you have any bad blocks during the erase? U-boot isn't smart enough to
> deal with bad blocks ... I have a board that has one in the middle of the
> kernel image. I moved it away from the bad block and changed the nboot
> address to match.
>
> Steve
>
> Joshua Hintze wrote:
>
> Hello,
>
>
>
> I am having trouble boot from NAND flash larger images. Previously my kernel
> uImage was around 1.4 megs. I just recently enabled some other options and
> it grew in size to 1.6 megs.
>
>
>
> Our nand flash layout is like this.
>
>
>
> 0x00000000-0x00018000 : "UBL image"
>
> 0x00018000-0x00044000 : "U-boot image"
>
> 0x00044000-0x00208000 : "Kernel image"
>
> 0x00208000-0x003ffc000 : "JFFS2"
>
>
>
> So we have more than enough space. I load the uImage into ram using tftpboot
> and then nand erase/nand write it out making sure I write all of it and
> erase enough space.
>
>
>
> However when I go to boot it I get the following:
>
>
>
> Loading from device 0: <NULL> at 0x2000000 (offset 0x44000)
>
> Image Name: Linux-2.6.10_mvl401-davinci_evm
>
> Image Type: ARM Linux Kernel Image (uncompressed)
>
> Data Size: 1646412 Bytes = 1.6 MB
>
> Load Address: 80008000
>
> Entry Point: 80008000
>
> ## Booting image at 80700000 ...
>
> Image Name: Linux-2.6.10_mvl401-davinci_evm
>
> Image Type: ARM Linux Kernel Image (uncompressed)
>
> Data Size: 1646412 Bytes = 1.6 MB
>
> Load Address: 80008000
>
> Entry Point: 80008000
>
> Verifying Checksum ... Bad Data CRC
>
>
>
>
>
> However, if I just bootm after I loaded it with tftpboot it works just fine.
> So there is some problem in the reading/writing to the NAND flash.
>
>
>
> Any thoughts?
>
>
>
> Thanks,
>
>
>
> Josh
>
>
>
>
>
> _____
>
>
>
>
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081018/29a85062/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Sat, 18 Oct 2008 18:11:27 +0530
> From: Nitin Joshi <[EMAIL PROTECTED]>
> Subject: Help on accessing CS2/3/4 address spaces on DM6446
> To: "davinci-linux-open-source@linux.davincidsp.com"
> <davinci-linux-open-source@linux.davincidsp.com>
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> I am working on DV EVM - DM6446 and I have to access external memory region
> connected
> to processor through AEMIF interface.
>
> To tell you the exact details,
> In our custom target board which we will receive next week, there are 2 FPGA
> connected to 2 AEMIF
> interfaces of the DM6446, and I need to configure FPGA registers from Linux
> user space.
>
> But presently I have the DVEVM-DM6446 and I am trying to access DDR memory
> connected
> to processor through another EMIF, hoping that the same way I can access the
> FPGA registers!!
>
> I tried following 2 methods and both are working fine!
> Method 1)
> U32 *virt_addr;
> //Get the virtual address
> virt_addr = (U32 *)phys_to_virt(Physical address);
> //Write data
> *(virt_addr + offset) = (U32) 0x12345678;
> And if I print both virt and phy addresses, Virt = 0xc0000000:: Phy =
> 0x80000000 and offset 0xf00
>
> Method 2)
> U32 *virt_addr;
> //Get the virtual address
> virt_addr = (U32 *)ioremap(Physical address, 4096);
> //Write data
> *(virt_addr + offset) = (U32) 0x12345678;
> And if I print both virt and phy addresses, Virt = 0xc8164f00:: Phy =
> 0x80000000 and offset 0xf00
>
> I would like to know which one is the preferred/correct way to work with
> mapped memories?
>
> Appreciate your help !!
>
> Thanks and Regards,
> Nitin Joshi
>
>
> ________________________________
> This message (including attachment if any) is confidential and may be
> privileged. If you have received this message by mistake please notify the
> sender by return e-mail and delete this message from your system. Any
> unauthorized use or dissemination of this message in whole or in part is
> strictly prohibited. E-mail may contain viruses. Before opening attachments
> please check them for viruses and defects. While MindTree Limited (MindTree)
> has put in place checks to minimize the risks, MindTree will not be
> responsible for any viruses or defects or any forwarded attachments emanating
> either from within MindTree or outside.
>
> Please note that e-mails are susceptible to change and MindTree shall not be
> liable for any improper, untimely or incomplete transmission.
>
> MindTree reserves the right to monitor and review the content of all messages
> sent to or from MindTree e-mail address. Messages sent to or from this e-mail
> address may be stored on the MindTree e-mail system or else where.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081018/3dc85115/attachment-0001.htm
>
> ------------------------------
>
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
>
> End of Davinci-linux-open-source Digest, Vol 34, Issue 80
> *********************************************************
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
