TMS320F28335: Use STL for IEC60730

All those "creating output section" warnings mean that they haven't updated their cmd file to add the sections required by the library. They should use the .cmd file from the simple demo application in the STL as a guide. There should be additional description in the library User's Guide as well.

InitSciaGpio is in the normal DSP2833x_Sci.c. I believe the simple demo application only uses this function to configure the SCI to send test results to the PC via UART, so it's not something required to be integrated into the customer application.

I can't find anything called TEST_testSafeRam in the library--there's a STL_CRC_TEST_testSafeRam and a STL_MARCH_TEST_testSafeRam though. I'm guessing they have a copy and paste error somewhere in the code that cut off the first part of the function name.

Whitney

Thanks Whitney. We solve most of the issues with your remind.

We still have a error message, could you please help?

Thank you.

Hi Jenny,

It looks like for some reason your project is trying to use the EABI version of the RTS library even though I can see your project is using --abi=coffabi. Do you see in your project where the rts2800_ml_eabi.lib file is being selected instead of the COFF one? Usually in your project linker options you can just use -l libc.a and let the compiler select an appropriate RTS library version for you.

Whitney

Thanks much Whitney, this issue is solved.

We will start the DSP firmware UL1998 certificate with TI IEC60730 library.

The 3rd party lab request us to do some tests related to TI IEC60730 library we announce our FW have.

We have no examples on such test experience, we don't know how to make DSP register mulfunction, PC abnormal, Invariable Memory, Internal Data Path, etc.

Could you provide some test templates or examples?

Thank you.

Jenny

Are you trying to figure out how to introduce errors to show that the application is able to properly detect them? Some of the tests to have built-in #ifs to turn on/off error injection. You can take a look at the "Fail Case Tests" chapter for a list of some of them.

Whitney

Yes, Whitney. We want to find out how to introduce errors to show the application can work properly.

We can't find #ifs to turn on/off error injection instruction, and can't find "Fail Case Tests" chapter in IEC60730_F2833x_STL_User_Manual.pdf, please give instructions or provide document on them.

Thank you.

Jenny

It's section D.1.3. I'll paste the text here though:

The simple demo application example and the safety test library ,where possible, provide a provision for introducing error to test the safety test library. This is done in addition to the test during code development. The fail case test can be enabled by setting the macros LIB_TEST_ISR_ERROR, LIB_TEST_MARCH_ERROR_ASC, LIB_TEST_MARCH_ERROR_DSC, LIB_TEST_FPU_TEST_ERROR, LIB_TEST_CPU_TEST_ERROR, LIB_TEST_EPWM_TEST_ERROR defined in STL_system_config.h in Safety test library , LIB_TEST_ECAP_APWM_MODE_ERROR, LIB_TEST_OSCILLATOR_ERROR, LIB_TEST_SPI_ERROR, LIB_TEST_SCI_ERROR, LIB_TEST_I2C_ERROR, LIB_TEST_CAN_ERROR, LIB_TEST_WATCHDOG_ERROR, LIB_TEST_TIMERS_0_1_ERROR, LIB_TEST_TIMER_2_ERROR in STL_test_report.h in simple demo application and the variable gErrorTestFlag declared in main.h in the simple demo application. Note: These macros and the variable gErrorTestFlag should be set for test purpose only.

As it says, they are enabled in STL_system_config.h.

Whitney

Thanks, Whitney.

One more question, we used STL_OSCILLATOR_TEST_testExtOscUsingSf0 to check internal oscillator.

We can't build successfully for subroutine SFO_MepDis_V5.

STL_oscillator_test.c include SF0_V5.h.

There is no SFO_V5.h in the IEC60730_STL_Library_v4_00_01_00, we download SFO_V5.h in TI web. Is it possible SFO_V5.h not correct?

Attached SFO_V5.h here. Thank you.

Jenny

SFO_V5.h

The SFO library is part of controlSUITE. Are you linking the .lib in your project? You can find it in controlSUITE under C:\ti\controlSUITE\device_support\f2833x\v142\DSP2833x_common\lib

Whitney