a53_sys_scst_loadstore_test7

[nmansour]

Hello, 

we're using SCST_A53_S32G_RFP_2.0.2 library for A53 runtime tests. 

Currently we have an issue in running test: a53_sys_scst_loadstore_test7 and it returns Error Code: ERR_SCST_FAILED_A53_C3

in the user manual it's mentioned to have specific access rights by the MMU: 

Could you provide an example on how this mapping is expected by the test or in MMU configuration since the MMU only accepts "address ranges" not section names? Also Could you clarify why the test is failing currently?

Thanks in advance for your support.

[nmansour]

Hi @al thanks for the reply 

I've checked the provided Demo and i have a couple of questions hope you can clarify. 

- On the demo, it depends on the linker section allocation in the linker file. 
This option we cannot use because the runtime tests are compiled and linked in the PH application and linking is done by the QNX. 
So is there a workaround for this?

- in the file you mentioned to check A53_SYS_SCST_RAM_DATA_TARGET0_VADDR this one we currently don't have defined any my understanding is that we either use the virtual address macro or the linker section. Could this be a substitute? 
- in the user manual what does it mean exactly by proper MMU mapping, is it only the attributes or something else is missing? for EL1 mmu configuration, this is handled by QNX so we can't change it. 
 

[alejandro_e]

Hello @nmansour,

Please find my answers in the private message I sent you.

Regards

[alejandro_e]

Hello @nmansour,

Doing some more investigation on the SCST topic I was able to find this document QNX Integration Example of S32G A53 SCST Library. That should help you exactly with what you are looking for.

Specifically about your questions, support for QNX is outside the scope of the support we offer in this community, so I would recommend reaching out to the QNX vendor for support.

Let me know if I can help you with anything else.

[nmansour]

Thanks for the quick reply.
Could you also give some insights on using the VADDR instead of the linker section?
Where can i find this explained?
A53_SYS_SCST_RAM_DATA_TARGET0_VADDR

for these 2 points in particular:
- in the file you mentioned to check A53_SYS_SCST_RAM_DATA_TARGET0_VADDR this one we currently don't have defined any my understanding is that we either use the virtual address macro or the linker section. Could this be a substitute?
- in the user manual what does it mean exactly by proper MMU mapping, is it only the attributes or something else is missing?

[alejandro_e]

Hello @nmansour,

Thanks for reaching out to us. About your questions, we do have an example on how to configure MMU selections, it is called A53 SCST Linux Integration Demo, once you install it you can check function mmu_init() in C:\NXP\SCST_FW_A53_S32G_1.0\scst_fw\src\mmu_config.c, in that function you can see how to initialize memory ranges. As you will see it uses the names of the sections instead of the explicit values, however those names get resolved into values at compile time.

Regarding the possible reasons for the failing result, please check what is mentioned for the A53_SYS_SCST_RAM_DATA_TARGET0_VADDR definition, in C:\NXP\SCST_A53_S32G_RFP_2.0.2\SCST_SYS\src\h\a53_sys_scst_configuration.h.

You can downloading the demo I mentioned by following these steps:

- go to https://www.nxp.com/ and log into your account

- Go to "My NXP Account" and then on "Software Licensing and Support":

- Now click on "View accounts", this will take you to the FlexNet portal, where you should be able to see all your available products.

- Now got to: Automotive SW – S32G Reference Software and then Automotive SW - S32G A53 SCST Linux Integration Demo. Download de executable file and 

After executing said file you will be able to find the example I mentioned above.

 Let me know if you have more questions.