EVM C6424

Are you running an example or code made for C6424? You have to make sure that your command file (.cmd) matches the memory map of the specif DSP you are using.  The code might not have been made for your specific processor (6424). Please check the file link.cmd and make sure the memory map (page 19) matches the datasheet for the specific processor:

http://www.ti.com/lit/gpn/tms320c6424

hello;

yes im running a code tht is made for C6424 and da link.cmd matches da memory map for Evm C6424.

When i run da same code on my other evm board there are no errors and code runs just fine.

i should tell u tht the code tht im runing is the Nor Flash test , i did changes to it nd the code didnt executed as i hoped so i changed it back

but then this error came .... n da code doesnt run

Does do original project work for both boards? I mean, before the changes...

Does the code with changes run in the first board?

Do you have a backup of the original project?

hello;

the original code worked on both of boards .

Once my first board stop working running properly when i loaded da modified code ... i didnt test it on my other board fearing it might damage it as well.

yes i do hve a backup of the original code and tried running it on my (let say damage) board it did give da ryt results.

i fear my software changes might hve damaged the hardware circuitry of my board :( is tht possible ??? 

in the SRAM test code .. the value FFFFFFFF has to written to the memory but wht it writes is 7FFF7FFF ...

its only they EMIF test codes tht r failing ... i tried other test codes ( of emac and spi ) they work just fine.

waiting for reply.

What did you change? PLL, EMIF CLK configurations? Knowing a bit more about that might help to figure out if there could be a problem affecting the hardware. I would say that is very rare for the software to cause damage in the hardware, but it might happen.

It could just a coincidence that the board got damaged (by ESD or similar) when you changed the program, but I can’t tell much right now.

You can set the dip switches such that you can change the boot mode.  Instead of doing "NOR boot" you can do "emulation boot" which doesn't execute any code at power on.  That way if your flashed code is doing something "bad" then it won't affect things.  It's SW1 that controls the boot pins (it's a set of 8 switches).  You need to set switches 1-4 to "off" for emulation mode.  Once you've recovered your flash then you can set the switches back to their current setting (switch 3 "on" for NOR boot).

Brad

hello;

i was working in emif mode ... n wanted to catch signals on expansion connectors ... the read n write signals .. so i made a code which read from da same memory location over and over again .. so i verify da signals on xpansion connector ... i was studying this behaviour so i can interface my daughtercard properly  ...  other than tht i slowed down da emif clock 2 ... for da ease of monitoring da signals .... n then da error came ... 

hello brad ;

i was working in the emif fast boot mode , i'll change it to emulation boot to check .

thank u

Amna