S32DS installation DIAB compiler programming error problem

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32DS installation DIAB compiler programming error problem

1,081件の閲覧回数
lubo_NEW
Contributor III

The same project compiled with DEBUG and DEBUG RAM has different content

1111.png2222.png

0 件の賞賛
6 返答(返信)

1,070件の閲覧回数
jiri_kral
NXP Employee
NXP Employee

Hi, 

it looks, that in linker file script for RAM target are not defined symbols mentioned in linker errors. It is possible share your project? 

 

Jiri 

0 件の賞賛

1,057件の閲覧回数
lubo_NEW
Contributor III
スポイラ
 
0 件の賞賛

1,049件の閲覧回数
jiri_kral
NXP Employee
NXP Employee

Hi, 

it looks that you aren't using memory.dld linker script file for _RAM target. Unfortunately I don't have DIAB compiler on my machine and can't test it. Please check the differences in Project properties -> Linker settings for Debug and RAM target. The memory.dld is the clue. 

 

Jiri 

0 件の賞賛

1,031件の閲覧回数
lubo_NEW
Contributor III

Thank you for your reply. Could you please help me to see what the problem is with another mistake as shown in the picture11111.png

0 件の賞賛

1,012件の閲覧回数
stanish
NXP Employee
NXP Employee

Hi lubo,

The problem you observe with Debug RAM build is that there are sections in the Debug Configuration (Flash) that are not present in RAM build (typically reset vector section, ROM->RAM copy sections,...)

Since your Debug (Flash) build configuration project startup routines rely on custom linker symbols that contain e.g addresses or of these sections (OS_NONCACHE_BSS_START...) - these symbols are missing for RAM configuration.

You need to define these symbols in 57xx_ram.dld linker file and probably use conditional compilation to skip startup ROM->RAM copy-down routines for RAM project.

Hope it helps.

Stan

0 件の賞賛

1,080件の閲覧回数
lubo_NEW
Contributor III

Why does Debug compile not produce an error, while Debug RAM compile does

0 件の賞賛