[AmirF]

in reply to: Digital Output(Do) Feedback #18494

Hi Rushikeshkale,

Please see the guide on HSO feedback for details on how feedback channel works with HSO.

1) PTG2 configured as output and PTC10 as input, where both the pins are connected to the same VCU pin J1-L1, So we are expecting that if we set the PTG2 High and the J1_L1 get shorted to Ground then we should get zero in feedback which is read by PTC10. Instead on shorting(J1_L1) with ground the VCU get On-OFF.

You can set PTG2 as PWM output and PTC10 as ADC input. These two pins are not directly connected. SO, when J1-L1 gets shorted to GND, there will be a ~3V measured on PTC10.

Please make sure that VBATT stays above 9V in the event of a short circuit on HSO11 because a voltage drop on VBATT can cause a reset in the VCU.

Sincerely,
Amir

[AmirF]

in reply to: FCE2.1 PIN connection to QCA chip #18480

Hi Xuanlang,

The reset pin is not connected to the S32K344 and the only pins connected between PLC module and the MCU are 4 SPI pins, and 1 interrupt pin. Slod, no other GPO, or Eth pins are connected to MCU.

Thanks,
Amir

[AmirF]

in reply to: FLEXCASE E 2.1 SPI Communication CLOCK Problem #18478

Hi Xuanlang,

1. For MBDT1.3 you can find the SpiSamplePoint in the following path in the config tool:
Peripherals>Spi>SpiGeneral>SpiPhyUnit>SpiSamplePoint.

2. If changing the SpiSamplePoint didn’t help, please use the workaround. In this approach, you set up the SPI such that there is no CLK jitter, let the Spi Phy Unit control a dummy CS(like PTF19, as mentioned before), and control the actual CS pin as GPIO in the code. This way, you get to control the CS manually, and there will be no clock jitter.

Sincerely,
Amir

[AmirF]

in reply to: FLEXCASE E 2.1 SPI Communication CLOCK Problem #18452

Hi Xuanlang,

As you mentioned, since the QCA chip on the PLC module uses SPI mode 3, SpiShiftClockIdleLevel= HIGH is the correct configuration. You can also modify the CPHA using SpiSamplePoint parameter in the config tool.

I haven’t had this issue before, but I can think of a suggestion and a workaround for your application.
1. Software is the issue and it might indicate that you are using a different SPI mode. Please make sure you are running it in SPI mode 3.
2. You can use this workaround if the first suggestion doesn’t work. You can let the software drive the CS pin, but give it a dummy pin(a pin that is not connected or used, like PTF19 for FCE2.1) to drive it. You will still be able to drive the actual CS pin manually. Or alternatively, just define the CS pin as GPIO in the pinout tab and don’t define the SPICS.

Sincerely,

Amir

[AmirF]

in reply to: Can we get the execution time from the AUDESSE? #17747

Dear Yahuizhao,

I assume you are asking this question for an FCS device and you are running your algorithm on the main MCU on board. To find out the exact runtime of an algorithm running on the main MCU on Simulink, you can put the algorithm in an atomic subsystem and use the profiler block.
Please take a look at the following link as well. There is a similar question asked.
https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/LPTMR-Get-Counter-Value/m-p/1828783#M8918

Sincerely,
Amir

[AmirF]

in reply to: freemaster #17171

Hi David,

It is most probably happening because your memory block is being written in the code. Please check for “Data Memory Write” blocks in your code.

Thanks,
Amir

[AmirF]

in reply to: Can the digital inputs on FCS be pullup of down independently? #17140

Hi Garrett,

It depends on the version of the hardware you are using.

On FCS1.1 and older versions of FCS, all the Digital Inputs are pulled high in hardware and there is no software-controlled switch to pull down or float the DIs. In this version, all the DIs will read high(1), unless they get connected to a voltage less than 2V.

On FCS1.2 you can pull up all the DIs by driving PTC8 high. All the DIs will be pulled high together and unfortunately, they are not controllable separately on FCS1.2. However, on FCE2.0 and FCG1.0, which are the newer designs, you will have better control over DI pulls, as there are two separate switches for 12 DIs.

On FCS1.2, if you drive PTC8 high, each DI will read 1, either for a voltage greater than 2V or no external connection. Each DI will only read low (0), if a voltage between GND(0V) and 2V is detected on the DI header pin.

Thanks,
Amir

[AmirF]

in reply to: CAN Flashing on a Different CAN channel #17130

Dear Saiesh,

I wanted to give you an update about your question.
I have asked our team for the new bootloader file to enable you flash over CAN3 for FCE2.0 and FCG1.0. I will send you the file as soon as it is available.
Please, let me know if you have further questions.
Sincerely,

Amir

[AmirF]

in reply to: CAN Flashing on a Different CAN channel #16983

Hi Saiesh,

Which device is this question for?
Can you confirm if it is related to FCE2.0 or FCG1.0?
If so, yes. It is possible to flash over a different CAN channel. This can be changed through the binary file used in the CAN flasher. Please let us know which CAN channel you want to use, so we can provide you with a modified binary file.

Thanks,
Amir

[AmirF]

in reply to: gmake compiling errors for S32K344 MCU in Simulink #16338

Hi Kantesh,

Could you please provide some more details on your issue?
First, what is your MBDT for the S32K3 version? Are you using version 1.4?
Second, what was the exact file you replaced in your K3 library?
Third, can you check your configuration tool and see if there are any errors or warnings associated with your peripherals setting?

Thanks,
Amir Fathazam
Audesse Team

[Author]

Posts