The original has been in the S32DS3.5 + RTD5..0.0 development, between the new demand to develop gPTP-related functions, so to rebuild a new development environment:
S32DS_3.6.2_RFP_win32.x86_64.exe
SW32K3_S32M27x_RTD_R21-11_6.0.0_D2506_DesignStudio_updatesite.zip
SW32K3_FreeRTOS_11.1.0_6.0.0_CD1_D2506_DesignStudio_updatesite.zip
SW32K3xx_M7_gPTP_1.0.0_D2507_DesignStudio_updatesite.zip
SW32K3_TCPIP_STACK_3.0.0_D2507_DesignStudio_updatesite.zip
After the build is complete, create the S32K388_gptp_free_rtos_ds project and update the code to compile directly to find the following error:
Is my understanding that the environment build process is not missing plugin installation?
The actual same situation lwip_FreeRTOS_s32k388 occurs:
But the corresponding plugins I have installed, attached is S32K388_gptp_free_rtos_ds export routine, just started to build please point me in the right direction, thank you!
Hello, actually I'm not too concerned about this error, these errors can certainly be revised, the main again S32DS3.5 + RTD5.0.0 directly into the standard routines provided by the IDE did not appear to compile error problems, but in the S32DS3.6.2 + RTD6.0.0 the same operation occurs the phenomenon, is not the plug-in installation mismatch caused by the most worried about it:
Involved in the source code file are provided by the SDK, basically will not modify, that is, modify is also configured through the IDE interface to modify the back with the increase in functionality, will continue to update the Code, has been modified to cover the file again, each time you need to modify one side, so it is not too convenient!
Hi @Ryan_xjl
I was able to replicate the issue. The following changes were required to build the project without errors:
FreeRTOSConfig.h
Add the following definition:
#define configKERNEL_PROVIDED_STATIC_MEMORY 1port.c
Add the declaration:
void xPortSysTickHandler( void ) __attribute__( ( naked ) );
Vector_Table.s
Change .globl vPortSVCHandler
to .globl SVC_Handler
Change .long vPortSVCHandler
to .long SVC_Handler+1BR, VaneB
Hi @Ryan_xjl
Regarding software compatibility, the current versions you are working with should operate without issues, as they all depend on RTD version 6.0.0.
Concerning the migration from RTD 5.0.0 to RTD 6.0.0, and from S32DS 3.5 to S32DS 3.6.2, several changes have been introduced in both the software and the IDE. Therefore, full backward compatibility cannot be guaranteed, although the overall functionality remains largely similar.
Finally, regarding the loss of modifications in generated files, this is expected behavior when using ConfigTools. Each time a new configuration is applied, the tool regenerates the files and restores them to their default state. Any manual changes made directly in these files are not preserved. Therefore, it is important to manage custom modifications carefully when working with generated code.
Hi @Ryan_xjl
No worries, the language difference can sometimes cause misunderstandings, and I really appreciate that you shared a video showing the issue.
The window displayed when opening ConfigTools is simply a warning indicating that the project was created using an older version of the tool than the one you are currently using. This only becomes relevant if you try to open the .mex file again with the original (older) version. In your case, it should not cause any problem. Also, when creating a project from scratch, this warning does not appear.
Finally, the build error you encountered when compiling the example can be resolved by applying the changes I mentioned in my first reply.
I hope this helps clarify your questions.
Thank you very much for being so patient to help me solve my confusion, maybe I didn't express myself clearly enough, or I'm just starting to learn, it's convenient to express my meaning clearly, I provided a video of the whole operation process, which can express my claim better, thanks again for being so patient to help me!
PS: There is a phenomenon in the process, I don't know if that situation is the cause of the
Attached is a video of the procedure
