I wonder if anyone has the similar issue as my in SSP1.2.0 with e2studio 5.3.1
I want to change TIMER_TICK_PER_SECOND for the ThreadX so I add ThreadX source and set properties Timer Ticks Per Second to 1000. After the compilation, there are a few hundreds of warming messages about "TIMER_TICKS_PER_SECOND redefined". By searching through the source files, it appears that the tx_user.h, where this customized TIMER_TICKS_PER_SECOND is defined, is inserted into the wrong location in tx_port.h. As shown below, the line 93 should be added before line 82. Though I made the change in tx_port.h and made this file Read Only for now to get rid of the warning messages, I'd like to know if there is a better way.
You should not edit the source files to make this change. The proper way to do this is to add the source using the Synergy Configurator and then Edit the properties for the ThreadX module. The property that you want to change is below:
In reply to garyj:
In reply to abe:
In reply to Renesas Karol:
yes shure ... but if you see the source of hal touch driver (on SSP1.2) there is a tx_thread_sleep(2) inside i2c functions ...
I try to change ThreadX tick settings and this sleep will change and may become relevant
In reply to Jimmy:
If you modify the tx_src_user.h file in the synergy_cfg /framework/el folder in your project and add the following highlighted code:
#define TX_TIMER_TICKS_PER_SECOND (1000)
Then make the file read-only and build.
This will eliminate the warning for the redefinition of the ticks but is not recommended because any property changes will not be updated in this file.
I still get 21 other warnings for unused parameters and type conversions... This is all in the protected express logic code.