A linking error #A0329-D occurred when my Simulink model was built into C code and then linked to a dSpace MicroAutobox

Hi, everyone! I came across a problem when compiling my Simulink model and haven't found any clues on the Internet. Hope someone can share your thoughts to help me out. I really appreciate it very much.

The Matlab version I was using is 2017a and the dSPACE software is Release 2017-A, which is compatible with Matlab 2017a. dSPACE Real-Time Interface (RTI1401) is Version 7.8. Actually, the compilation was fine. When I ticked the option of Generate code only, it was successful. However, after compiling the model into c files, it threw a linking error as follows:

*LINKING APPLICATION ...

< lnkppc >

(E) #A0329-D Reserved memory overlapped from address 0x3000000 to 0x3000927

 Errors: 1, Warnings: 0

-- call "C:\Program Files\dSPACE RCPHIL 2017-A\Compiler\PPCTools\BIN\lnkppc.exe" -K0 -QmsA0314 -QmsA0407 -QmeA0307 -QmeA0329 -m..\HITL.map -o ..\HITL.ppc -c _tmp_HITL.lk LINKING FAILED (1)

MAKE PROCESS ABORTED*

I used fzero and interp1 in some of my blocks and both functions are supported for code generation. But when I examined every block, then found just these two functions caused the linking problem. They were able to be compiled into C for sure, but I don't know whey they caused something wrong with the reserved memory. I haven't found some useful information in the documents.

Many thanks for your help.

[Thomas Waters]

I am running Matlab 2015b with the exact same problem occurring during compilation.

Any help would be much appreciated. Thanks!

Answer 1

[Thomas Waters]

I contacted Dspace about the problem. Apparently source is that the generated application is too large for the storage on the Autobox. Unfortunately they can only detect this problem once the code has been generated.

Is it possible that you have parameters in embedded Matlab functions that are too large?

[Albert Liu]

Hi, Thomas, thank you very much for the answer. I got the reply from dSpace this morning. The application engineer suggested me checking the application size just like you said. Probably this is the reason. Anyway, I'll double check on it. If the problem is solved by optimising the application size, I'll let you know immediately. Many thanks.

Just share some links the engineer sent to me with you.

http://www.dspace.com/faq?269

http://www.dspace.com/faq?210

http://www.dspace.com/faq?211

Hope these are useful.

Cheers~