[Connor]

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

Is the CAN bus terminated?

[Connor]

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

– The diagnostic buzzer is not present on the FlexCase E, thank you for pointing out a mistake in the guide, I will fix promptly.

– The error in your screenshot indicates that your computer does not recognize the peakCAN device. Did you install the peakCAN drivers mentioned in the Prerequisites for the tutorial?

[Connor]

in reply to: How to Disable Wake on CAN for Flex Case E ? #18856

This is not related to disabling wake-on-CAN, please see this thread instead:

Freemaster over CAN in FCE-G

[Connor]

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

I will also reference the duplicate thread in the NXP forums:
https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/FreeMaster-not-connecting-over-CAN-MBDT-1-5-S32K344/m-p/1886702.

I have attached an example of FreeMaster over CAN working on FCE/FCG CAN0 in case you don’t have it already. We are not officially supporting MBDT 1.5 yet since we need to re-validate our sample software, but I am guessing there is a small bug somewhere in your mex file that is preventing other busses from working. For example, from the NXP forum screenshot, the name of the CAN controller for CAN2 has the same name as CAN0, which could be causing problems. Please review the differences between your mex file and the one I posted here, and I can review potential problems.

Attachments:

You must be logged in to view attached files.

[Connor]

in reply to: rockchip Uart with MCU(FCE2.1) #18853

The GPIO12/GPIO13 pins are internal gpio mapping from the Raspberry Pi CM4, not Radxa. The datasheets have been updated to reflect the two sets of pins compatible with MPU UART5 (pins 28/31 for Raspi, pins 62/57 for Radxa CM3). The standard/focus SKU for FCE2.1 has both sets of pins populated, but if you have an alternate SKU, the Radxa-compatible pins may not be populated.

[Connor]

in reply to: CAN Flasher Bug? #18848

It looks like you’re looking in the folder you used to install the program, not the program files directory listed in the tutorial. The configs should be in C:/Program Files/FlexCaseFlash/resources/flashconfigs unless you specifically chose a different install directory.

[Connor]

in reply to: CAN Frames are dropping randomly on S32K344 – FlexCase E #18030

Hi Kantesh,

Some questions about your setup:

– Are you using Matlab/Simulink or S32DS to program the algo?
– Are you capturing your CAN messages in polling or interrupt mode?
– If you are using multiple capture modes, are there different message buffers that are more prone to problems?

[Connor]

in reply to: Flash Driver (FLS) and Flash EEPROM Emulation (FEE) #17189

Is the application for algorithm calibration? Are you programming in Matlab/Simulink or C?

[Connor]

in reply to: Application Development on C (HW and Pin details requirement) #17188

Please provide more details on which hardware you are using and the intended application.

– What linker are you referring to? The custom linker from FlexCaseFlash?
– For clock setups and other peripheral initialization, your best bet is to open one of the sample projects provided by NXP and modify for your needs.
– Internal pin mappings are in the datasheets, but if you let me know what hardware you’re using I can double check that the information is present in the datasheet

[Connor]

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

Hello,

This feature is in the works. Can you please let me know some for details of the application for using Freemaster over CAN?

[Connor]

in reply to: NVM usage on the FCE lineup. #16907

We do not currently have a guide for NVM access, but it is in our queue. I will reply in this thread with a link to the tutorial when it is ready. Thank you for your patience.

[Connor]

in reply to: NVM usage on the FCE lineup. #16770

Hi Nikhil,

NVM access is not something that is supported automatically in Simulink. Getting it to work properly would be a combination of linker changes like the ones that are done for the CAN flasher, and some “System Update” blocks to inject C functions into the code. Is your use case storing calibration values?

[Connor]

in reply to: Restoring Bootloader for S32k142 FlexCase lite #16589

Hello,

The bootloader binaries are not available by default. We will be adding bootloader binaries for specific versions of the CAN flasher soon. For your version of the FlexCase, you can indeed use your Pemicro tool.

[Connor]

in reply to: Flashing the Compute Module eMMC #16027

Please see attached files. The python tutorial also mentions setting up scripts to run at startup, which you can apply to “spiComm.py” after verifying that it runs standalone. The “spiLogger.py” can be run as needed while spiComm is running. You will also need to add the following line to /boot/config.txt to make the SPI interface available:

dtoverlay=spi0-2cs

• This reply was modified 1 year, 4 months ago by Connor.

Attachments:

You must be logged in to view attached files.

[Connor]

in reply to: Sending messages using CAN #15951

Hi Amin,

Is this variable that you use to trigger a CAN message coming from another peripheral or are you just setting it in FreeMaster? If it is a boolean variable, you can construct a “rising edge detect” by triggering the subsystem when the current value is 1 and the current value is different from the previous.

For the CAN message not changing, try to construct your CAN message in a similar way to how the default SPI communication works: individual variables merged into an array and passed to the CAN send block. Sometimes trying to edit an entire array through FreeMaster can add unnecessary complication.

[Author]

Posts