2 replies to this topic

[genaoueg]

I am starting using ImpulseC with CoDeveloper and I must say I appreciate it, tought I am always having trouble with the same thing :

When I do one of those mistakes in my code (I sometimes do some) for example :
- missing one parameter of the co_process_function
- openning a register as a INT_TYPE instead of a UINT_TYPE
(and other mistakes that a developer sometimes does...), I am able to build the project without any single warning, but when I launch the simulation executable, everything crashes and I can't have any block diagram, any cosim_logwindow_fwrite output or anything to help me know where my error comes from...

Is there anything I can do to solve this kind of error faster?

Sorry for the english
thanks for any help

[Impulse Support]

Crashes in the C code execution during desktop simulation can occur for many reasons, as they can with any C application under development. The errors you describe with co_process parameters and data types can also cause confusion and result in hard-to-debug crashes.

One technique we use ourselves is to try compiling the application for hardware (the Generate Hardware function). The hardware generator is more picky than gcc about correct use of types, and correct use of parameters to co_process_create, etc. If you suspect you have mismatches in types when opening or reading/writing streams, for example, the hardware compiler will tell if that's the case.

[genaoueg]

ok, thanks, that's what I did.