Sign in

username:

password:



Not a member?

Search c6x



Search tips

Subscribe to c6x



c6x by Keywords

AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560

Sponsor

NEW! TMS320C6474: 3x the performance. 1/3 the cost. Three 1 GHz cores on 1 chip.

Discussion Groups

Discussion Groups | TMS320C6x | a problem in writing to flash in dsk6713

Technical discussions about the TI C6000 DSPs (including the c62x, c64x and c67x DSPs).

  

Post a new Thread

a problem in writing to flash in dsk6713 - z_11...@yahoo.com - Aug 4 9:44:06 2008



hi

I work with dsk6713, when programming flash, data copy to address 2 times in EMIF boot from 8
bit flash (default).
For example data is 80 and in address 0x90000000 copied as 8080.
Therefore space of flash product with 1/2.
after reset cpu data in 0x90000000 is 80
For details:
Data in:address:	data before reset data after reset
0x0080	0x90000000	c2c28080	  2000c280
0x00c2	0x90000004	20200000
0x0000
0x0020 

Is it true??
If it is a problem please support me
Regards
zahra

------------------------------------

OMAP35x EVM jump-starts low-power apps
------------------------------------
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building
applications based on the OMAP35x architecture:http://www.DSPRelated.com/omap35x



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Re: a problem in writing to flash in dsk6713 - Michael Dunn - Aug 4 10:14:33 2008

zahra,

On Mon, Aug 4, 2008 at 8:42 AM,  <z...@yahoo.com> wrote:
> hi
>
> I work with dsk6713, when programming flash, data copy to address 2 times in
> EMIF boot from 8 bit flash (default).
> For example data is 80 and in address 0x90000000 copied as 8080.
> Therefore space of flash product with 1/2.
> after reset cpu data in 0x90000000 is 80

<mld>
The 6713DSK has a 16 bit flash and it is programmed as an 8 bit flash
by default [wasting 1/2 of the locations - I have no idea why it was
created this way].

> For details:
> Data in:address: data before reset data after reset
> 0x0080 0x90000000 c2c28080 2000c280
> 0x00c2 0x90000004 20200000
> 0x0000
> 0x0020
>
> Is it true??

<mld>
To properly view the original flash contents, you must set your EMIF
to view CE1 [0x9xxxxxxx] in 8 bit mode.  You can do this manually or
by adding a menu to the GEL file to select 8 bit mode.  Once you do
this, you can open the disassembly window and set the address to
0x90000000.  The contents of the first 0x400  locations will match the
contents of memory 0-0x3FF after a CPU->Reset.

mikedunn
> If it is a problem please support me
> Regards
> zahra

-- 
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php

------------------------------------

OMAP35x EVM jump-starts low-power apps
------------------------------------
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building
applications based on the OMAP35x architecture:http://www.DSPRelated.com/omap35x



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Re: a problem in writing to flash in dsk6713 - Richard Williams - Aug 10 10:58:19 2008

z_1151,

Isn't 9000000 in EMIF address space 1?

Usually, the external device at that address space is SDRAM.

However, if your project has a FLASH attached at that address space...

It cannot be read/written until the EMIF1 interface has been initialized, so
anything read right after reset is trash.

Also, if I understand your email correctly, all the software is doing to set the
flash is writing to the address twice.
I would be very interested in any flash part that ONLY took two writes to an
address to program the flash.

R. Williams
---------- Original Message -----------
From: z...@yahoo.com
To: c...@yahoogroups.com
Sent: Mon, 04 Aug 2008 09:42:11 -0400
Subject: [c6x] a problem in writing to flash in dsk6713

> hi
> 
> I work with dsk6713, when programming flash, data copy to address 2 
> times in EMIF boot from 8 bit flash (default). For example data is 80 
> and in address 0x90000000 copied as 8080. Therefore space of flash 
> product with 1/2. after reset cpu data in 0x90000000 is 80 For 
> details: Data in:address:	data before reset data after reset 0x0080	
> 0x90000000	c2c28080	  2000c280 0x00c2	0x90000004	20200000 0x0000 0x0020
> 
> Is it true??
> If it is a problem please support me
> Regards
> zahra
------- End of Original Message -------
------------------------------------

OMAP35x EVM jump-starts low-power apps
------------------------------------
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building
applications based on the OMAP35x architecture:http://www.DSPRelated.com/omap35x



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Re: a problem in writing to flash in dsk6713 - William C Bonner - Sep 12 22:17:20 2008

I know that my 6713 based board has SRAM (SBSRAM or SDRAM depending on 
the particular revision) starting at address 0x80000000 and my flash is 
at 0x90000000. The first sector of flash gets read correctly, and that 
boots the rest of the system, which initializes the EMIF correctly for 
whichever board I'm running on.

I've got a bios function that I use to make sure that the writing of 
flash is correct, but I do most of my reading of flash directly. I've 
got two 512K pages that I have to make sure I'm on the correct page, but 
at least as far as reading the data from the flash, it reads exactly 
like it was RAM.

Richard Williams wrote:
> z_1151,
>
> Isn't 9000000 in EMIF address space 1?
>
> Usually, the external device at that address space is SDRAM.
>
> However, if your project has a FLASH attached at that address space...
>
> It cannot be read/written until the EMIF1 interface has been 
> initialized, so
> anything read right after reset is trash.
>
> Also, if I understand your email correctly, all the software is doing 
> to set the
> flash is writing to the address twice.
> I would be very interested in any flash part that ONLY took two writes 
> to an
> address to program the flash.
>
> R. Williams
>
> ---------- Original Message -----------
> From: z_1151@yahoo. com <mailto:z_1151%40yahoo.com>
> To: c6x@yahoogroups. com <mailto:c6x%40yahoogroups.com>
> Sent: Mon, 04 Aug 2008 09:42:11 -0400
> Subject: [c6x] a problem in writing to flash in dsk6713
>
> > hi
> >
> > I work with dsk6713, when programming flash, data copy to address 2
> > times in EMIF boot from 8 bit flash (default). For example data is 80
> > and in address 0x90000000 copied as 8080. Therefore space of flash
> > product with 1/2. after reset cpu data in 0x90000000 is 80 For
> > details: Data in:address: data before reset data after reset 0x0080
> > 0x90000000 c2c28080 2000c280 0x00c2 0x90000004 20200000 0x0000 0x0020
> >
> > Is it true??
> > If it is a problem please support me
> > Regards
> > zahra
> ------- End of Original Message -------
>

------------------------------------

OMAP35x EVM jump-starts low-power apps
------------------------------------
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building
applications based on the OMAP35x architecture:http://www.DSPRelated.com/omap35x



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )