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


Discussion Groups

See Also

Embedded SystemsFPGAElectronics

Discussion Groups | TMS320C6x | Re: Doubts in JPEG project

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

  

Post a new Thread

Re: Doubts in JPEG project - Giovanni Parodi - Oct 23 7:24:17 2007

Hi
I'm sorry but I forgot to explain in detail the structure of my code.
In fact the internal memory is used by heap and 64 KB of L2 cache.
However in order to correctly allocate both the heaps I had to half the size of
cache. The application works, but  it could be useful to avoid such a change
since the MPEG4 performances suffer a bit from it and JPEG is a low priority
section of my code. Therefore I thought that since the heap is addressed through
standard routine (I think mem_alloc , mem_free etc) simply changing the section
labelled with heap_internal should solve the problem.
What am I missing? May be there is some DMA operation that could suffer from the
different timing constraints of internla and external memory?
Thanks again for your help.
Jeff Brower <j...@signalogic.com> ha scritto:                             
   Giovanni- 
Hi, thanks for your help. 
The problem is that in my project half of the L2 memory is used for MPEG4 codec
heap and half for JPEG and it is complex to move the data. 
I will try to perform some minot changes to the MPEG4 code allocated in internal
memory. Are you saying that your internal SRAM is completely used by heap and
data, and there is no remaining space for L2 cache? As you know (or should
know), internal SRAM can be subdivided between two (2) areas: 
  -reserved for L2 cache area 
  -accessible to DSP code 
You have to clarify your situation. 
-Jeff

Jeff Brower <j...@signalogic.com> ha scritto:  Giovanni- 
  first thanks for your help. 
The project works in the base revision (I had to install code generation tools
revision 5.1.11, with 5.1.0 the example doesn't work), but I'm not able to move
the heap that TI allocates in internal memory to an external memory section. 
Do you have any idea?   
My first thought is that you don't have L2 cache correctly configured, so
external memory data accesses are very slow.  My suggestion would be to try
moving some other data structure -- smaller and less important than the heap --
to ext mem.  If you see a slowdown (which I would expect) then spend time to
understand L2 cache and configure it exactly as needed.  Then you can go back to
making major mem allocation changes.-Jeff 
  Jeff Brower <j...@signalogic.com> ha scritto:  Giovanni-> I am using
Jpeg Encoder designed by Texas Instruments on DSP DM642, the 
> name of the project is netcam2 (spra937A). Because problems of internal 
> memory I moved the encoder jpeg on external memory (SDRAM). Every things 
> is okay but one. When I set the channel that execute the jpeg using the 
> CHAN_setup() function, I have to specify an internal (intHeap) and 
> external heap (extHeap). 
> 
> In this case if I use two different external heap(created in external 
> memory) the encoder jpeg doesn’t work, the output is not in jpeg format 
> ad also the size of the file, using same picture in input, is almost 
> eight time bigger. You know if there is a method to can use the jpeg 
> algorithm on external memory or to limit at maximum the use of internal 
> one?One thing I don't understand. If you built TI's netcam2 project exactly
as 
documented in spra937A, does it work? Did you have problems at that point? Or
only 
after you started making changes?-Jeff

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

---------------------------------
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail
______________________________
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.



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