RTD v5.0.0 ADC configuration error when exporting to DaVinci

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

RTD v5.0.0 ADC configuration error when exporting to DaVinci

Jump to solution
853 Views
strofald
Contributor III

Hello,

 

I am using S32K3 RTD v5.0.0 Adc module.

I configured an AdcGroup to be triggered by SW, with all the related channels.

However, when I export my configuration in .arxml and import it in the DaVinci Configurator, the tool complains about the parameter: AdcGroupHwTriggerSource which cannot be empty.
However, the description of the parameter says:

Vendor specific: Select the HW trigger signal for triggering the conversion group. Configurable only when HW trigger source is selected for the group.

Since I configured the group to be triggered by SW, I don't expect this parameter to be configurable at all.
I can also add that when configuring the module in EB Tresos no such error occurs, but I get a warning saying: 

The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Adc/ELEMENTS/Adc/AdcConfigSet/AdcHwUnit/AdcHwUnit_ADC0/AdcGroup/ADC0_Adc..." with value "" does not refer to nodes.

How can I proceed to get rid of this error? Please note that the parameter is Vendor-Specific (from NXP) and not defined by AUTOSAR, and is also reported in .ARXML files to have lower multiplicity = upper multiplicity = 1, so it seems to be mandatory, while the description says otherwise.

Tags (4)
0 Kudos
Reply
1 Solution
644 Views
DanNguyenDuy
NXP Employee
NXP Employee

Hi @strofald,

The RTD team confirmed this issue is a bug of the RTD driver and will be fixed in the next releases. At the moment, I haven't had any information about the specific release plan.

Best regards,

Dan

View solution in original post

0 Kudos
Reply
7 Replies
850 Views
strofald
Contributor III

EDIT: correct warning message in EB Tresos is: 
The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Adc/ELEMENTS/Adc/AdcConfigSet/AdcHwUnit/AdcHwUnit_ADC0/AdcGroup/ADC0_AdcGroup_0/AdcGroupHwTriggerSource" with value "" does not refer to nodes.

0 Kudos
Reply
801 Views
DanNguyenDuy
NXP Employee
NXP Employee

Hello @strofald,

I raised a bug ticket (ARTD-177241) with the RTD team for this issue. When they analyze this issue completely, I will notify you.

Best regards,

Dan

0 Kudos
Reply
790 Views
strofald
Contributor III

Hello Dan,

thanks for the reply. I also posted a new support ticket about this issue with ID : #00695543.
I don't know if it can be useful for your internal reference.

Thank you very much.

 

0 Kudos
Reply
788 Views
strofald
Contributor III

I can also add, as I reported in the support ticket, that in my opinion the issue lies in the .epd file of the Adc module, which is the file that is used by external tools like DaVinci to correctly import the module data.
From this file in fact you can see that the AdcGroupHwTriggerSource parameter has upper multiplicity = lower multiplicity = 1. Based on that, the DaVinci tool will generate a .arxml file with that specified multiplicity, forcing you to configure the parameter.

0 Kudos
Reply
767 Views
DanNguyenDuy
NXP Employee
NXP Employee

Hi @strofald,

I suppose that the warning is also related to "upper multiplicity" and "lower multiplicity" in the .arxml file. When the RTD team fixes this issue on .xdm files, they will also generate .epd and .arxml files again. I will inform you asap.

Best regards,

Dan

0 Kudos
Reply
645 Views
DanNguyenDuy
NXP Employee
NXP Employee

Hi @strofald,

The RTD team confirmed this issue is a bug of the RTD driver and will be fixed in the next releases. At the moment, I haven't had any information about the specific release plan.

Best regards,

Dan

0 Kudos
Reply
611 Views
strofald
Contributor III
Thank you for the update.
0 Kudos
Reply