Flash and run code in SRAM with a corrupted DRAM

[mathiasparnaude]

Hi,

I am working on memory tests to check different DRAM memories on a T1040RDB board.So I need to have corrupted memories plugged in the socket to run and adjust my tests, identify the cause of errors, ...

The problem is I can't succeed in flashing the code from my CodeWarrior project. I always get this error:

I suspect it tries to use the DRAM but I can't understand why.

I selected the "SRAM" build configuration.

I also tried various settings without finding a good ones. What should be the init script? I tried T1040RDB_init_core.tcl and T1040RDB_init_sram.tcl.

I checked boxes Core Reset and Initialize Target. Is it ok?

In the "Memory" panel, should I choose a script? I tried with and without T1040RDB.mem.

Do I miss something? Is it possible?

If so, a description of the configuration to set would be very welcome!

Note that under U-Boot, even if some accesses to the DRAM cause errors, the initialization by the DDR controller is done successfully.

Regards,

Mathias

[yipingwang]

Hello Mathias Parnaudeau,

It's not target initialization problem, CCS fails at configuring JTAG chain(the first step).

Is there valid RCW on your target? Can u-boot run normally now?

Do you use CodeWarrior TAP(integrates both USB and Ethernet ports) or USB TAP(only USB port)?

Do you use Windows 7 or Linux OS?

It's better to send the CCS log to us to do more investigation, please refer to the following procedure.

Before connect to the target, please enable CCS log from "Run->Debug Configurations-><project>-core0_RAM_Connect(Download)->Edit...->Advanced->Advanced CCS setting->Enable logging", and connect to the target from "Run->Debug Configurations-><project>-core0_RAM_Connect(Download)->Debug”, the CCS log will be printed in the console panel in CodeWarrior IDE.

Note: Please open the console panel from Window->Show View->Console, and if nothing displayed, please choose the correct session on the right top icon in the panel. If the CCS log in the console is truncated, please enlarge the console buffer from Window->Preferences->Run/Debug->Console->uncheck "Limit console output".

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[mathiasparnaude]

Hi Adrian and Yiping

Thank you for your answers.

I use CW 10.4.0, on Linux (Red Hat Enterprise Linux Workstation release 6.6), with a CodeWarrior TAP on USB.

I created a clean project with Download SRAM launch connection. I previously missed this option and the RAM connection that I modified afterwards. But at the end,  after this manual configuration, I obtained settings that looked similar to the ones with this "Download SRAM launch" connection.

In a first time, that still failed but then, after a hardware / manual reset of the board, that worked! I've used it since one or two days (I wanted to be sure it was working before replying). And I only had few connection problems, that use to happen sometimes. This is why, Yiping, I think I will try what to describe to get and provide the CCS log.

Right now, I am able to run a program in SRAM (or flash U-Boot in NOR) even if the DRAM stick is corrupted / missing.

Weeks ago, I modified RCW to change the DDR bus frequency but had particular problem since (under U-Boot or Linux).

Thanks,

Mathias

[addiyi]

Hi Mathias,

What CW version are you using? You should try Download SRAM launch connection. This connection will use by default the SRAM init and aslo the SRAM lcf.

Adrian