Sign in

username:

password:



Not a member?

Search Comp.Arch.Embedded



Search tips

embedded by Keywords

68HC11 | 68HC12 | 8051 | 8052 | ARM | ARM7 | Asic | AT91 | AT91RM9200 | Atmel | AVR | AVRStudio | Bootloader | CFP | CompactFlash | Cygnal | Cypress | Dataflash | DSP | eCos | EEPROM | Embedded Linux | Emulator | Endian | Ethernet | Firewire | FPGA | Freescale | GCC | GNUARM | GSM | H8 | HDLC | I2C | Infineon | Interrupts | Java | JTAG | LCD | LED | LPC2000 | MCU | Microchip | MMC | MPLAB | MSP430 | PC104 | PCB | PCI | PCMCIA | PowerPC | Rabbit | RS232 | RS485 | RTOS | SBC | SDRAM | Sensor | SPI | STK500 | UART | UML | USART | USB | Verilog | VHDL | VxWorks | Xilinx

Discussion Groups

There are 6 messages in this thread.

You are currently looking at messages 0 to 6.

U-Boot - kongs - 14:38 30-07-05



Hi,

Does anybody tell me how can I delete completly an atmel dataflash wit
U-Boot. I try this first: 1. I unprotect the areas of the dataflash. 2
then i want to erase but i become follow messages: start and/or end adres
not on sector boundary. I look at the atmel site datasheet of th
dataflash, but i can't find there anything else sector boundaries. 
Thanks for your answers.


 


		
This message was sent using the comp.arch.embedded web interface o
www.EmbeddedRelated.com

Re: U-Boot - Chuck Gales - 21:42 30-07-05

On Sat, 30 Jul 2005 13:38:01 -0500, kongs wrote:

> Hi,
> 
> Does anybody tell me how can I delete completly an atmel dataflash with
> U-Boot. I try this first: 1. I unprotect the areas of the dataflash. 2.
> then i want to erase but i become follow messages: start and/or end adress
> not on sector boundary. I look at the atmel site datasheet of the
> dataflash, but i can't find there anything else sector boundaries. 
> Thanks for your answers.
> 
There are several unknowns which you will need to provide to answer your
question:

- Which ATMEL part number? This will tell you what sector size(s) the chip
has.
- Is the chip is 8-bit or 16-bit mode?  Different chips support one or
both modes.
- What is the flash configuration on the board? x1, x2 or x4, creating an
8-bit, 16-bit or 32-bit interface to the CPU?

When you have the answers to these questions, you can then calculate the
sector boundaries for your implementation.

Chuck


Re: U-Boot - Dan Henry - 23:37 30-07-05

Chuck Gales <c...@gmail.com> wrote:

>On Sat, 30 Jul 2005 13:38:01 -0500, kongs wrote:
>
>> Hi,
>> 
>> Does anybody tell me how can I delete completly an atmel dataflash with
>> U-Boot. I try this first: 1. I unprotect the areas of the dataflash. 2.
>> then i want to erase but i become follow messages: start and/or end adress
>> not on sector boundary. I look at the atmel site datasheet of the
>> dataflash, but i can't find there anything else sector boundaries. 
>> Thanks for your answers.
>> 
>There are several unknowns which you will need to provide to answer your
>question:
>
>- Which ATMEL part number? This will tell you what sector size(s) the chip
>has.
>- Is the chip is 8-bit or 16-bit mode?  Different chips support one or
>both modes.
>- What is the flash configuration on the board? x1, x2 or x4, creating an
>8-bit, 16-bit or 32-bit interface to the CPU?

Other questions and issues aside, I'll pick nits here by saying that
DataFlash uses SPI, a serial interface.  So that would be (for all
intents and purposes) a 1-bit interface to the CPU.

That said, the source code for U-Boot is readily available and could
be reviewed to determine how it deals with sector boundaries for
DataFlash devices.  Trying to get answers here is a reasonable
approach, but one does have access to the code itself as an alternate
source of information.

--
Dan Henry

Re: U-Boot - Dan Henry - 23:58 30-07-05

Dan Henry <u...@danlhenry.com> wrote:

>Chuck Gales <c...@gmail.com> wrote:
>
>>On Sat, 30 Jul 2005 13:38:01 -0500, kongs wrote:
>>
>>> Hi,
>>> 
>>> Does anybody tell me how can I delete completly an atmel dataflash with
>>> U-Boot. I try this first: 1. I unprotect the areas of the dataflash. 2.
>>> then i want to erase but i become follow messages: start and/or end adress
>>> not on sector boundary. I look at the atmel site datasheet of the
>>> dataflash, but i can't find there anything else sector boundaries. 
>>> Thanks for your answers.
>>> 
>>There are several unknowns which you will need to provide to answer your
>>question:
>>
>>- Which ATMEL part number? This will tell you what sector size(s) the chip
>>has.
>>- Is the chip is 8-bit or 16-bit mode?  Different chips support one or
>>both modes.
>>- What is the flash configuration on the board? x1, x2 or x4, creating an
>>8-bit, 16-bit or 32-bit interface to the CPU?
>
>Other questions and issues aside, I'll pick nits here by saying that
>DataFlash uses SPI, a serial interface.  So that would be (for all
>intents and purposes) a 1-bit interface to the CPU.
>
>That said, the source code for U-Boot is readily available and could
>be reviewed to determine how it deals with sector boundaries for
>DataFlash devices.  Trying to get answers here is a reasonable
>approach, but one does have access to the code itself as an alternate
>source of information.

And there is the Atmel's at91.com site with many boards using U-Boot
and DataFlash.

BTW, what does U-Boot's 'flinfo' command report about the DataFlash
organization?

--
Dan Henry

Re: U-Boot - kongs - 06:44 03-08-05

>Dan Henry <u...@danlhenry.com> wrote:
>
>>Chuck Gales <c...@gmail.com> wrote:
>>
>>>On Sat, 30 Jul 2005 13:38:01 -0500, kongs wrote:
>>>
>>>> Hi,
>>>> 
>>>> Does anybody tell me how can I delete completly an atmel dataflas
with
>>>> U-Boot. I try this first: 1. I unprotect the areas of the dataflash
2.
>>>> then i want to erase but i become follow messages: start and/or en
adress
>>>> not on sector boundary. I look at the atmel site datasheet of the
>>>> dataflash, but i can't find there anything else sector boundaries. 
>>>> Thanks for your answers.
>>>> 
>>>There are several unknowns which you will need to provide to answe
your
>>>question:
>>>
>>>- Which ATMEL part number? This will tell you what sector size(s) th
chip
>>>has.
>>>- Is the chip is 8-bit or 16-bit mode?  Different chips support one or
>>>both modes.
>>>- What is the flash configuration on the board? x1, x2 or x4, creatin
an
>>>8-bit, 16-bit or 32-bit interface to the CPU?
>>
>>Other questions and issues aside, I'll pick nits here by saying that
>>DataFlash uses SPI, a serial interface.  So that would be (for all
>>intents and purposes) a 1-bit interface to the CPU.
>>
>>That said, the source code for U-Boot is readily available and could
>>be reviewed to determine how it deals with sector boundaries for
>>DataFlash devices.  Trying to get answers here is a reasonable
>>approach, but one does have access to the code itself as an alternate
>>source of information.
>
>And there is the Atmel's at91.com site with many boards using U-Boot
>and DataFlash.
>
>BTW, what does U-Boot's 'flinfo' command report about the DataFlash
>organization?
>
>--
>Dan Henry
>

I become this info:
DataFlash:AT45DB642
Nb pages:   8192
Page Size:   1056
Size= 8650752 bytes
Logical address: 0xC0000000
Area 0:	C0000000 to C0007FFF (RO)
Area 1:	C0008000 to C001FFFF (RO)
Area 2:	C0020000 to C0027FFF 
Area 3:	C0028000 to C083FFFF 

Bank # 1: Atmel: AT49BV6416 (64Mbit)
  Size: 8 MB in 135 Sectors
  Sector Start Addresses:
    10000000 (RO) 10002000 (RO) 10004000 (RO) 10006000      10008000     
    1000A000      1000C000      1000E000 (RO) 10010000 (RO) 10020000     
    10030000      10040000      10050000      10060000      10070000     
    10080000      10090000      100A0000      100B0000      100C0000     
    100D0000      100E0000      100F0000      10100000      10110000     
    10120000      10130000      10140000      10150000      10160000     
    10170000      10180000      10190000      101A0000      101B0000     
    101C0000      101D0000      101E0000      101F0000      10200000     
    10210000      10220000      10230000      10240000      10250000     
    10260000      10270000      10280000      10290000      102A0000     
    102B0000      102C0000      102D0000      102E0000      102F0000     
    10300000      10310000      10320000      10330000      10340000     
    10350000      10360000      10370000      10380000      10390000     
    103A0000      103B0000      103C0000      103D0000      103E0000     
    103F0000      10400000      10410000      10420000      10430000     
    10440000      10450000      10460000      10470000      10480000     
    10490000      104A0000      104B0000      104C0000      104D0000     
    104E0000      104F0000      10500000      10510000      10520000     
    10530000      10540000      10550000      10560000      10570000     
    10580000      10590000      105A0000      105B0000      105C0000     
    105D0000      105E0000      105F0000      10600000      10610000     
    10620000      10630000      10640000      10650000      10660000     
    10670000      10680000      10690000      106A0000      106B0000     
    106C0000      106D0000      106E0000      106F0000      10700000     
    10710000      10720000      10730000      10740000      10750000     
    10760000      10770000      10780000      10790000      107A0000     
    107B0000      107C0000      107D0000      107E0000      107F0000  

I have a 64 Mbit dataflash AT45DCB008 the At91RM9200-EK board. I need 
empty dataflash to write Atmel bootloader which boots about a SDcard.
 

		
This message was sent using the comp.arch.embedded web interface on
www.EmbeddedRelated.com

Re: U-Boot - A.P. Richelieu - 05:28 08-08-05

>
> I have a 64 Mbit dataflash AT45DCB008 the At91RM9200-EK board. I need a
> empty dataflash to write Atmel bootloader which boots about a SDcard.
>
>
>

No you don't.
Remove the Dataflashcard.
Set the jumper to "INT" position to force the CPU to run from the internal 
bootROM.
Powerup the system.
Since there is no dataflash connected, the CPU will not find a bootable 
image
and will try to download code over USB or UART.
Insert the dataflash card.

Download the Atmel dataflash loader (into internal SRAM) using 
Hyperterminal/Xmodem.
The CPU will jump to this once completed.

You will be presented a menu with three alternatives.
1 Program dataflash
2 List Dataflash
3 Jump to U-boot

Select (1) and send the dataflash loader again using Hyperterminal/Xmodem.
This time the loader will be programmed into the first sector of the 
dataflash.

Reset the system and you should be running from dataflash.

-- 
A. P. Richelieu