[Connor]

in reply to: Noise susceptibility of SPI between FlexBench MPU and MCU #19942

Hi Craig,

How does the MCU interact with the motors through software? Is it providing direct outputs, sending serial commands? If sending serial, do the commands start/stop in sync with the power up? I want to rule out timing problems in software.

[Connor]

in reply to: GPIO Numbering #19681

Hi Mathew,

The attached script has basic examples for reading/writing GPIO pins using the .pyc driver files. The only functions you’ll likely need are setup(pin, mode) , input(pin) , and output(pin, level), since the other setup functions are dummy functions for compatibility with raspi libraries.

Please follow up if you have questions about specific functions, or if the script isn’t downloading correctly.

• This reply was modified 2 months ago by Connor.

Attachments:

You must be logged in to view attached files.

[Connor]

in reply to: How to calibrate the data store over can ? #19673

The init should not be on CAN0, this indicates a problem with the peripherals config.

Please make sure you have installed the Audesse simulink blocks correctly (make sure you see the pop-up after running the install script) before opening any .slx file to ensure that the config gets set up. You do not need to put an extra config file in the folder with the sample you are working on, just put the .slx in a new folder by itself and open it.

[Connor]

in reply to: How to calibrate the data store over can ? #19649

Hi Rushikesh,

The NVM_k3 sample model is configured for CAN2, not CAN0. The error in your screenshot indicates no response from the VCU, which would make sense if you’re connected to CAN0.

[Connor]

in reply to: GPIO Numbering #19645

Hi Mathew,

You are likely using a Radxa MPU rather than a Raspberry Pi, and the pins you mention are for Raspberry Pi. I will update the FlexCase G datasheet to be more clear on that distinction.

There is a script “/usr/local/FLXdevice.py” included on your MPU that indicates your pin mappings, and also includes a driver that uses the popular python GPIO syntax so you don’t have to directly import/export from the filesystem. This driver is also used by the modem control scripts so it shouldn’t be moved from the default location.

[Connor]

in reply to: FlexCase R Flashing Issue #19403

Hi Justin,

If you flashed the default binary from the sample, the application software likely will not show anything on CAN2. To make sure your flashing bootloader is still intact, try initiating a new flash within 1-3s of powering up the device.

[Connor]

in reply to: Hard fault issue on flex case E (S32K344) #19386

Hi Kantesh,

It does look like there is some forbidden operation happening in the CAN interrupt logic.

– Is the CAN traffic when you are in this specific state of DC charging?
– Are all of your CAN reads handled by interrupt or do you have a mix of polling and interrupt?
– While in this specific state of DC charging, are you running an operation that blocks for a long time, creates it’s own interrupts, or disables other interrupts?

[Connor]

in reply to: Flexcase G Bootloader Restore #19355

Hi Mathew,

Did you flash your application software over CAN or over JTAG?

[Connor]

in reply to: JTAG #19320

JTAG flashing and debugging is not officially supported without a proprietary adapter, which requires an additional “developer” agreement between your company and Audesse. If you require this feature, please reach out to the team directly to start the process.

[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.

[Author]

Posts