S32G中的主题 Re: Issues while building HSE demo application in S32DS

Issues while building HSE demo application in S32DS

Lee0202 — Fri, 16 Aug 2024 09:22:08 GMT

Hi all,

1)i am trying to build demo application of HSE version 0_1_0_5 which is mentioned in multicore enablemnt guide . I am not getting these packages which i found in Readme.pdf present in demo application. Below provided contains what are the package i installed till now in S32DS and also proving the required packages versions they provided in that document.

2)i don't know one thing

required is :S32 RTD AUTOSAR 4.4 version 2.0.0 Hot Fix 04;

but in my software account i have only this higher version file: SW32G_RTD_4.4_4.0.2_HF02_D2311_DS_updatesite.zip

Lee0202_0-1723799751220.png

i am getting error that it is asking S32DS 3.5.3 dependencies in that error log last line

3)no clarity why these are encountering because in that readme.pdf document of HSE DEMO application they mentioned S32DS 3.4 .....

4)Provide generic document because that README.pdf contains two methods using S32DS and GREEN hills tool .......

Re: Issues while building HSE demo application in S32DS

Celeste_Liu — Tue, 20 Aug 2024 09:06:11 GMT

Hi,

Below will be some comments on regards of your questions:

1)i am trying to build demo application of HSE version 0_1_0_5 which is mentioned in multicore enablement guide . I am not getting these packages which i found in Readme.pdf present in demo application. Below provided contains what are the package i installed till now in S32DS and also proving the required packages versions they provided in that document.

[A]From your screenshots I can see that most of the extensions you downloaded are correct. For the S32R45 development package version 3.4.1, if you actually use the S32R45 in the development, you can get it through the screenshot 1. For S32 RTD AUTOSAR 4.4 version 2.0.0 Hot Fix 04, the version you downloaded is wrong, please Uninstall it first.

2)i don't know one thing .required is :S32 RTD AUTOSAR 4.4 version 2.0.0 Hot Fix 04; but in my software account i have only this higher version file: SW32G_RTD_4.4_4.0.2_HF02_D2311_DS_updatesite.zip

[A]As mentioned in the Readme documentation, "NOTE: The S32 Design Studio projects depend on the above-mentioned versions and packages in order to work as described in this document. Without all these packages having these specific versions some of the features might not be supported.". The SW32G_RTD_4.4_4.0.2_HF02_D2311_DS_updatesite you downloaded is not compatible with S32DS3.4.3, so an error log will appear. Since S32 RTD AUTOSAR 4.4 Version 2.0.0 HotFix 04 is not officially released, it is recommended that you download S32G Real-Time Drivers Version 3.0.2 HotFix 01. You can download it and have a try. Please feel free to ask any new questions.

3)no clarity why these are encountering because in that readme.pdf document of HSE DEMO application they mentioned S32DS 3.4 .....

[A]Seems to be answered under point 2.

4)Provide generic document because that README.pdf contains two methods using S32DS and GREEN hills tool .......

[A]I'm sorry we don't have a generic document here. Apologize for the inconvenience. In addition, there is indeed a method other than S32DS mentioned in the documentation. For questions related to Greenhills Tool, please contact them for support.

Best Regards,
Celeste

Re: Issues while building HSE demo application in S32DS

Lee0202 — Mon, 19 Aug 2024 11:29:07 GMT

Iam using for S32G274Ardb2 board

Re: Issues while building HSE demo application in S32DS

Lee0202 — Mon, 19 Aug 2024 11:32:47 GMT

Do I need open . Mex file in the project or can I built directly. Because as mentioned they didn't say of . Mex file. Moreover after building they are doing ivt configuration for that.

Re: Issues while building HSE demo application in S32DS

Lee0202 — Mon, 19 Aug 2024 11:37:00 GMT

All these things I am doing because one nxp support team asked to build HSE demo application. Because iam not getting any logs after following "multi-core enablement guide". I did all steps as per guide. but I don't know where I did mistake.

Re: Issues while building HSE demo application in S32DS

Lee0202 — Mon, 19 Aug 2024 11:38:15 GMT

Help me how to debug. Give some suggestions one by one I will check and solve the issue

Re: Issues while building HSE demo application in S32DS

Celeste_Liu — Tue, 20 Aug 2024 03:09:55 GMT

Ok, now I know you are using the S32G274Ardb2 board. You do not need to open the.mex file, follow the instructions in the readme file. IVT configuration and blob image generation are required, and can be implemented by S32DS or python tools. Please download the correct version to try and let me know if there are any new specific problems.

Re: Issues while building HSE demo application in S32DS

Lee0202 — Thu, 22 Aug 2024 05:54:10 GMT

I will explain the main issue . i am using NXP s32G VNP RDB 2 board . I followed AN13750(muticore enablement guide).As per guide i downloaded all packages . Iam facing some issues 1)Iam not getting any logs out after completion of AN13750 NOTE:- i kept all address values same as like given like xerox because both are same boards 2)But one thing i observed is when I turn ON of SW4-7 and pressing Reboot button. I saw booting logs of A53 but as per AN13750 it should be in OFF position 3)I faced some issues while I am building bootloader in CMD.exe (.bat file executing) like missing xrdc_Ip header files missing. for that i deleted older OUTPUT folder in EB tresos directory and genetrated project in EB tresos .FINALLY bootloader.bin built successfully.

my main query is why iam not getting any logs?

what are the things do i need to check for this problem?

i provided all files

Re: Issues while building HSE demo application in S32DS

Celeste_Liu — Fri, 23 Aug 2024 11:16:28 GMT

Hello @Lee0202 ,

Thank you very much for presenting your issues in such detail. I understand what you mean is that there is no message printed on the serial port of M core. After SW4-7 is opened, the startup log of SD card's A53 core is displayed.

I think you need to understand the case of AN13750 again. The final result of this case does not mean that both core A and core M should have log information printed. The core of this case is to test IPCF to test whether IPC communication is normal (as shown below).

Celesteliu_0-1724411371614.png

So in this case, if you want to confirm whether the M kernel is up, you can refer to page 22 of AN13750.The driver on the Linux side sends an IPC message to the M core, and the M core returns the same message to Linux. The details are as follows:

Celesteliu_1-1724411559455.png

Please let us know if this information answers your questions.

Best regards,

Celeste