HSE_DEMOAPP_S32G2 Problem

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

HSE_DEMOAPP_S32G2 Problem

1,529件の閲覧回数
chengpei
Contributor III

Hello, NXP

I am implementing HSE_DEMOAPP_S32G2_0_1_0_5 on S32G-VNP-RDB2.

I using S32DebugProbe in S32 Design Studio 3.4.3, RTD 3.0.2HF01 and development package 3.4.3.

Folllowed the steps in Readme to abtain the blob image, I can't get any message from the Serial Port when I run this image in the board.

When I debugged the elf, I found it stuck in the while loop below:

chengpei_0-1687934560008.png

And the MUB0_FSR is 0,

chengpei_1-1687934693970.png

Here is the blob image I made.

Could you share a blob image which works well on S32G-VNP-RDB2 with me?

Thank you.

タグ(3)
0 件の賞賛
返信
9 返答(返信)

1,511件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

For what you are showing, it seems HSE was not installed correctly.

The following information is provided under the HSE_DEMOAPP readme:

DanielAguirre_0-1687975940508.png

For which, RTD v2.0.0 is the package required for the project, not RTD v3.0.2 HF01. Can you help us verify if this behavior remains once the correct RTD version is used?

Please, let us know.

0 件の賞賛
返信

1,485件の閲覧回数
chengpei
Contributor III

Hello, Daniel

I checked my software account, there is no RTD2.0.0HF04 for me, 

chengpei_0-1688008619527.png

And I try RTD2.0.0HF02, it still not work.

After this, I installed an new environment with S32DS3.4.3+developmentpackage3.4.3, but I did not installed any RTD, the hse demo can still be built, so I thought maybe it doesn't rely on any RTD.

chengpei_1-1688009031893.png

Could you help me verify this in your environment? Thank you!

 

0 件の賞賛
返信

1,480件の閲覧回数
chengpei
Contributor III

Supplement,

I did not open the mex file to Update Code, because if I did this, the project can not be built:

chengpei_0-1688010867299.png

 

chengpei_1-1688010867304.png

 

It must be built directly without generating any code.

0 件の賞賛
返信

1,466件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your feedback. Seems odd, but the instructions do not explicitly talk about generating code, so the project should already have the required files.

As for any issues we are seeing, can you help us sharing the IVT structure that you are creating? The capture from Config Tools should be good, for us to understand if there is no problems with the IVT itself.

Please, let us know.

0 件の賞賛
返信

1,451件の閲覧回数
chengpei
Contributor III

Hi, 

Here is the IVT I am using:

IVT_Setting.png

Attachment is my blob image from this IVT.

Thank you. 

0 件の賞賛
返信

1,428件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for the information.

We are not seeing that much difference on your IVT structure, just the usage of a different DCD, which is also provided within the DEMOAPP. 

How are you flashing this blob into your board? Once it is flashed, do you change the boot mode to QSPI?

Please, let us know.

0 件の賞賛
返信

1,359件の閲覧回数
chengpei
Contributor III

Hi, Daniel

I changed the boot mode to Serial to flash this image, and changed to QSPI mode to start the program according to the manual.

For the DCD I tried both <dcd_init_sram.bin> and <dcd_set_gpio25_and_init_sram.bin>, but none of them works.

Could you share your image with me?

Thank you.

0 件の賞賛
返信

1,336件の閲覧回数
chengpei
Contributor III

I added 2 print commands in the main function, as this:

chengpei_0-1688381904783.png

rebuild the project and generate the blob image again,  

I got the first print in my port:

chengpei_1-1688381958594.png

so, the program was stucked in the while loop:

chengpei_2-1688382142763.png

 

0 件の賞賛
返信

1,319件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Thanks for your feedback.

It still seems that HSE was not installed correctly.

We are still verifying how to arrive to the behavior you are seeing.

As for sharing images, we don't normally share them through here. We can recommend either sending this same inquiry to your local NXP FAE or opening a ticket inside the NXP online services, to confirm if there is an available image that can be shared. We do apologize.

Please, let us know.

0 件の賞賛
返信