[AmirF]

in reply to: Reading the PWM on PLC Multiplexed Digital Input 12 #19110

Hi Kantesh,
You can read the DICP or DI12 in the same way you read all other digital inputs.
If you want to read the DI12 in GPIO mode, you need to define the pin in both Dio MCAL and in the pinout section in the config tool. For digital status read, you can use SIUL2.

For PWM reads, you need to add a custom C code in your Simulink. Also, you need to set the pin in the config tool as input EMIOS, modify the pin in ICU MCAL, and set the clock reference, and interrupt setting.

You can take a look at the attached example for both GPIO and PWM applications.
Example file is compatible with MatlabR2022a and MBDT1.4. This is not part of our standard templates. Please use with caution.

Thanks,
Amir

• This reply was modified 1 week ago by AmirF.

Attachments:

You must be logged in to view attached files.

[AmirF]

in reply to: FCG Setup #19099

Hi Mobina,

Every time you build the code, Simulink tries to upload the generated files directly to the specified hardware(S32K3 in this case). So, this is an expected message, as Simulink can’t find the MCU, because this needs a direct connection to the MCU or some sort of onboard debugger. You are using another method to flash your binary files to the MCU over CAN using the FlexCase Flash software.
So, please ignore this message and select “abort” every time it pops up.

• This reply was modified 1 week, 3 days ago by AmirF.

[AmirF]

in reply to: FCE/G Configurations #18986

Unfortunately, the feedback ADCs for high-side outputs from 8 to 10 are unusable on ADC_MA channels. This is a bug on FCE2.0 and is resolved in the next versions.

As a workaround for feedback for HSO9/10 ADC, you can use another ADC channel ID available on that pin(ADC1_S18). Just ensure the secondary channel ID is not being used on any other physical pin.

Unfortunately, there is no workaround for the feedback pin for HSO7/8.

Thanks,
Amir

[AmirF]

in reply to: Unlocking the bootloader on FlexCase E with Red Beet #18981

Thanks for the clarification. Unfortunately, because of ASIL safety features JTAG flashing is disabled by default on FCE2.1 boards. Please get in touch with us directly to discuss this matter further.
Thanks,
Amir

[AmirF]

in reply to: Unlocking the bootloader on FlexCase E with Red Beet #18973

Hi Kantesh. May I ask what are trying to achieve with JTAG flashing? And why aren’t you using flash over CAN?
In general, you won’t be able to flash over JTAG on FCE2.1, unless you have a special development board to do it.

Amir

[AmirF]

in reply to: FlexCase E Not Communicating over CAN #18946

Could you confirm that you are writing to the same CAN that is connected to your PCAN device?
I believe that for flashing software you are using CAN2(CAN2L->pin C3, CAN2H->C4). Can you confirm that the CAN write block you are using in your Simulink is also for CAN2?
Also, please don’t remove the termination throughout the connection.
Please see the attached image.
Thanks,
Amir

Attachments:

You must be logged in to view attached files.

[AmirF]

in reply to: Freemaster over CAN in FCE-G #18693

Hello Rishabh,

We will work on this feature and let you know as soon as we have an update.

[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

[Author]

Posts