I'm finding that when I want to perform static analysis on my code with TraceX support enabled, I'm hitting an encrypted header file (synergy/ssp/src/framework/el/tx/tx_src/tx_thread.h) that causes my static analysis tool (in this case Polyspace) to fail to be able to analyze the file. Are there any recommendations for how to handle this? As an initial reaction, it makes extremely little sense to encrypt header files, which by definition are supposed to only declare things so other files know they exist (exactly why static analysis would need to read this file).
Otherwise, the obvious option is to set up a project configuration that does not include TraceX support, but we'd like to not maintain a separate project configuration specifically for this case. I think I could get around this if I can disable the flag TX_ENABLE_EVENT_TRACE, which is defined in tx_src_user.h, just for the Polyspace analysis if that leads anywhere.
Hi Elene, I downloaded source code from Git hub and ported it to Work with renesas Sysnergy. It is libaray project and you can navigate to source code. If you want you can add more define in tx_port.h file. I make this library to work with 120Mhz clock speed. You can change Clock frequency inside tx_initialize_low_level_sample.S file and rebuild the project. SYSTEM_CLOCK = 120000000 SYSTICK_CYCLES = ((SYSTEM_CLOCK / 100) -1) // Running at 100Hz (if you want can change it to 1000Hz) I hope this will help you with TraceX. Please find attached complete source code project