FlexCase
Quick-Start Guide
- Connect prototyping wire harness
- Connect to microcontroller
- Flash prebuilt files
Software Prerequisites (Windows)
- Ensure you have S32DS for Arm and VirtualHere installed.
- Download and unzip S32DS/Simulink Templates and MCU Samples from our sample software
Assemble Wire Harness
Assemble the provided wire harness:
- The two header connectors (C1 and C2) should already be attached to the FlexCase. If not, fasten the connectors with a 1/4″ socket/wrench. Neglecting to properly fasten the connectors will result in poor quality signals.
- Use the ethernet adapters to connect C1 to your computer via USB or Ethernet
- Industrial Ethernet to RJ45 cable
- RJ45 to USB adapter
- Connect C2 to the 4-pin power connector
- Leave the 2-pin CAN connector unconnected
Supply power to the FlexCase by connecting the power supply to a wall outlet, then pressing the On/Off button. The button will glow to indicate that power is supplied to the device.
Start the Required Software
Run the VirtualHere client executable. It will begin automatically searching for the FlexCase and auto-connect when a connection is found.
Be patient. This process can take up to 5 minutes on complicated networks. If the device can’t be found automatically, you can also specify the IP address of the FlexCase that appears on your computer’s network configuration.
While you wait for VirtualHere to find the FlexCase, import the flashing project to the IDE (S32DS) with the following steps:
- Open S32DS
- Click File > Open Projects from File System…
- Select Directory…
- Select the unzipped ExampleFlash folder that you downloaded earlier
- Click Finish
Establish the Programming Interface
Once the VirtualHere client has found the FlexCase, use the following steps:
- Right click the OpenSDA device
- Select “Use this device” (Device should read “In use by you”)
- (Optional) select “Auto-Use Device” to have the board connect whenever the client is running
Flash a Precompiled Example File
In S32DS, set up and run the flashing configuration:
- Select Run > Flash from file…
- In the debug configurations window, select ExampleFlash_Debug_FLASH_PNE configuration from the options in the left column. If you don’t have the configuration you can create a New_configuration by double clicking on GDB PEMicro Interface Debuging.
- Select the Debugger tab to setup the physical interface
- Ensure that Interface is set to OpenSDA Embedded Debug – USB Port
- Ensure that Port is recognized as some USB port (Not blank)
- Ensure the Target matches your processor variant:
- S32K144F512M15
- S32K142F256M15
- Ensure the GDB Client Settings > Executable has the configuration text ${S32DS_ARM32_TOOLCHAIN_DIR}/bin/${arm32_cross_prefix}gdb${arm32_cross_suffix}
- Select the Main tab to select and flash the file
- Select Browse… from the C/C++ Application section
- Select Buzzer.elf (142 or 144) from the MCU sample files and Open
- Click Flash in the bottom-right corner of the flash configurations window
- S32DS will flash the program to the FlexCase. After about 10s the device should reset and start beeping periodically
Success!
You have successfully flashed your first program. To turn off the beeping you can select the EmptyProject.elf for the C/C++ Application and flash back to the template project.
You will always hear a short beep to confirm the board has been flashed, reset, and is running the chosen program.
Shutdown
You can shutdown the device with a few options. The goal is to gracefully shutdown the MPU to avoid possible data corruption:
- All Devices (Automatic) – (Requires that power is supplied separately from ignition) – Remove the ignition signal and scripts running on the device will shutdown the MPU automatically.
- FlexCase Prototype Harness – This is the in-harness power button. The LED in the button will go out after 10 to 20 seconds when everything is powered down.
- FlexBench – This is available through the rear I/O connector.
- All Devices (Manual) – SSH into your device and run the shutdown command, included below.
- FlexBench – Use the HDMI (connected to a display) and GUI connection to manually shut down the MPU.
Warning: Suddenly removing power can cause memory corruption to the MPU over time so a graceful shutdown is recommended.