Hello to all NXP Community!
I think this is a silly question, but please, don't bother me...
I'm working with MBDT for S32K3xx, my target is the evaboard S32K44EVBQ172.
I successfully was able to configure the ADC and BCTU for doing a simple thing, just creating a PWM output with synchro ADC reading, and using that reading for generating the duty cycle.
Now, just for checking if all is as I was expecting, I would simply rise up a spy code when the ADC starts the conversion, and in order to do this I would like to use the "Trigger Notification" option in the BctuHwUnit, so I set a name for this field, in the S32 Configuration Tool, as you see in the following picture:
Now I was supposed to manage this callback inside Simulink, using an "Hardware Interrupt Callback" block, but I can't see my callback listed in.
I tried to add custom C code in the project, in order to create my own code for this callback, but I have a lot of issue in compiling because some dependencies can't be found by the compiler.
There is surely something that I missed or I didn't understand.
So, here is my question:
am I doing something wrong? Is there a better/simpliest way to turn on a monitoring output when the ADC conversion starts?
Thanks in advance for your help and kind support.
Regards
Hello @embedded_dan73
The option that you are referring to (controlling the edge of the hardware trigger signal) is applied by the drivers, in the code, only if the signal triggering the Adc conversion is not coming from BCTU - i.e. the Hardware Trigger used for this group has its source configured to be an external signal.
The BCTU inputs are active-high signals, hence a logic 1 asserts the trigger input which is subsequently routed to the Adc peripheral. The BCTU is configured to take its input source from an eMIOS channel, the Flag Generation of the eMIOS channel being the event that asserts the BCTU input. Thus, you might change the edge of triggering the BCTU from the Pwm component settings.
Since I am not aware of the Pwm signal configuration in your project, I will provide a brief explanation on this based on how the Pwm is configured inside the s32k344_pwm_trgmux_lcu_adc_ctu_ebt example that our toolbox delivers (you might find this application useful in terms of Adc, Bctu, Pwm, and other peripherals configurations as well). Inside this project, the eMIOS channel used as a trigger source for BCTU is configured in OPWMB mode, having a Polarity defined as PWM_HIGH, and the Flag Generation option set on Trailing_Edge. Based on the Reference Manual of the S32K3 (you can find it inside the Documentation section on the page), in OPWMB mode, the Flag Generation occurs according to the following table:
The value of the Cn[MODE] is set by the Flag Generation option inside the configuration project (Trailing_Edge is equivalent to the Flag generation occurring at a BS1 match).
AS1 and BS1 define the first and second edges of the generated Pwm signal, this generation being also influenced by the selection of the channel Polarity. If the Polarity is set to PWM_HIGH, a positive edge will occur when AS1 matches the selected counter bus, and a negative edge occurs when BS1 matches the selected counter bus. If the Polarity is set to PWM_LOW, a negative edge will occur at AS1 match, and a positive one at BS1 match. However, at a BS1 match, the Flag Generation event occurs as well, given the table above, hence asserting the BCTU trigger input.
In this particular case, changing the Polarity of the Pwm signal from HIGH to LOW could provide the behavior that you would like to achieve.
Considering these, could you please check the settings of the Pwm signal routed to BCTU and change them based on the information depicted above to see if this impacts the behavior you are currently encountering?
For more details on the eMIOS peripheral operating modes and settings, please check the, as it provides comprehensive information which you might find helpful for designing your application.
For the Adc and Bctu operating modes (Trigger vs. Control), besides the S32K3 Reference Manual, you could also check the Adc User Manual, provided by the drivers package that MBDT integrates (<toolbox_root>\S32K3_RTD\SW32K3_RTD_4.4_R21-11_3.0.0\eclipse\plugins\Adc_TS_T40D34M30I0R0\doc), while useful details could be also found in the following application note (you can find it inside the Documentation section on the page, under the Application Note category).
Hope this information will help,
Irina
Hi @Irina_Costachescu ,
your solution works perfectly! I can now see my callback function inside the hardware interrupt block mask, thanks a lot for your support.
Now I have another issue, probably it's not a real issue, but it's just for my understanding.
My intention was:
- turn on the code spy when the ADC is triggered
- turn off the code spy when the conversion is completed
So, in the group notifications array I set this option for ADC hardware triggering:
I'm expecting to see the code spy rising together with the PWM rising edge, and then going down when the conversion is complete.
But actually, what I see is this:
Yellow waveform is PWM, light blue waveform is my codespy.
It seems that the ADC is triggered with the falling edge...
The same happens if I set the "Adc Group Hardware Trigger Signal" to "ADC_HW_TRIG_FALLING_EDGE" or if I remove completely this field (because if I try to set "ADC_HW_TRIG_BOTH_EDGES" I receive an error message).
Am I doing something wrong?...
Thanks again for your kind support.
With Best Regards,
Daniel
Hello @embedded_dan73
The option that you are referring to (controlling the edge of the hardware trigger signal) is applied by the drivers, in the code, only if the signal triggering the Adc conversion is not coming from BCTU - i.e. the Hardware Trigger used for this group has its source configured to be an external signal.
The BCTU inputs are active-high signals, hence a logic 1 asserts the trigger input which is subsequently routed to the Adc peripheral. The BCTU is configured to take its input source from an eMIOS channel, the Flag Generation of the eMIOS channel being the event that asserts the BCTU input. Thus, you might change the edge of triggering the BCTU from the Pwm component settings.
Since I am not aware of the Pwm signal configuration in your project, I will provide a brief explanation on this based on how the Pwm is configured inside the s32k344_pwm_trgmux_lcu_adc_ctu_ebt example that our toolbox delivers (you might find this application useful in terms of Adc, Bctu, Pwm, and other peripherals configurations as well). Inside this project, the eMIOS channel used as a trigger source for BCTU is configured in OPWMB mode, having a Polarity defined as PWM_HIGH, and the Flag Generation option set on Trailing_Edge. Based on the Reference Manual of the S32K3 (you can find it inside the Documentation section on the page), in OPWMB mode, the Flag Generation occurs according to the following table:
The value of the Cn[MODE] is set by the Flag Generation option inside the configuration project (Trailing_Edge is equivalent to the Flag generation occurring at a BS1 match).
AS1 and BS1 define the first and second edges of the generated Pwm signal, this generation being also influenced by the selection of the channel Polarity. If the Polarity is set to PWM_HIGH, a positive edge will occur when AS1 matches the selected counter bus, and a negative edge occurs when BS1 matches the selected counter bus. If the Polarity is set to PWM_LOW, a negative edge will occur at AS1 match, and a positive one at BS1 match. However, at a BS1 match, the Flag Generation event occurs as well, given the table above, hence asserting the BCTU trigger input.
In this particular case, changing the Polarity of the Pwm signal from HIGH to LOW could provide the behavior that you would like to achieve.
Considering these, could you please check the settings of the Pwm signal routed to BCTU and change them based on the information depicted above to see if this impacts the behavior you are currently encountering?
For more details on the eMIOS peripheral operating modes and settings, please check the, as it provides comprehensive information which you might find helpful for designing your application.
For the Adc and Bctu operating modes (Trigger vs. Control), besides the S32K3 Reference Manual, you could also check the Adc User Manual, provided by the drivers package that MBDT integrates (<toolbox_root>\S32K3_RTD\SW32K3_RTD_4.4_R21-11_3.0.0\eclipse\plugins\Adc_TS_T40D34M30I0R0\doc), while useful details could be also found in the following application note (you can find it inside the Documentation section on the page, under the Application Note category).
Hope this information will help,
Irina
