FlexCase-S (Raspberry Pi OS Flashing + 32-bit / 64-bit)

[shwetawankhade]

#21153

Hi,
I’m currently working with the FlexCase-S platform and I had a couple of clarifications:
How do I flash Raspberry Pi OS onto the FlexCase-S using only the micro-USB connection?
If there is an official document, step-by-step guide, or video walkthrough available, please share it.
Should I use the 32-bit or 64-bit Raspberry Pi OS for FlexCase-S?
Since the platform uses an ARM Cortex MCU + compute module, I want to confirm which architecture is recommended and officially supported.
Any guidance or official reference material would be very helpful.
Thank you!

[shwetawankhade]

#21164

I would also like some clarification regarding the OTA capabilities available for the FlexCase S variant.
Specifically, I want to confirm:
Whether this SmartCase variant supports OTA updates.
If supported, what level of OTA is provided—application-level, firmware-level, or configuration-only.
The recommended procedure or workflow to follow for performing OTA updates on this platform.

A brief overview of the expected OTA pipeline (device → telematics module → backend → update deployment) would also be very helpful for our integration.

Thank you, and looking forward to your guidance.

Best regards,
Shweta

[Audesse Team]

#21169

Hi Shweta,

Thank you for reaching out with your questions regarding the FlexCase-S platform. I can certainly clarify the flashing procedures and the current status of OTA capabilities for this variant.

1. Raspberry Pi OS Flashing & Architecture

Regarding the flashing method via the micro-USB connection, this functions similarly to how standard development units work for the specific microprocessors used on the FlexCase-S.

However, please note that everything should already be pre-installed on the unit, so you generally should not need to change anything or choose between 32-bit/64-bit architectures manually.

Clarification needed: Could you let us know why you are looking to reflash the processor? Understanding your specific use case will help us determine if a manual reflash is actually necessary or if there is a different configuration solution.

2. OTA Capabilities & FlexCase-S Lifecycle

Regarding your second post about OTA updates, it is important to mention that the FlexCase-S is not recommended for new developments for FlexConnect.

The firmware on the S-variant is older.

It will not be receiving the same updates and support as the newer FlexCase-E and FlexCase-G models.

OTA Support Levels: The OTA support available is very similar to the tools and processes we provide for in-person flashing.

Supported: Application-level updates and configuration tools.

Not Supported: We generally do not provide firmware-level customization unless it is part of a larger enterprise deal.

Next Steps & Required Information

To help us guide you toward the right hardware and software strategy, could you please provide the following details?

Deployment Plan: What is your plan for deployment regarding the location, the total number of units, and your target time frame?

OTA Pipeline: Regarding the “Device → Telematics → Backend” workflow, could you clarify what specific parts are unclear based on the FlexConnect overview page (https://www.audesseinc.com/products/flexconnect/)? Knowing exactly what guidance you are missing will help us fill in the gaps.

Best regards,

Rhyse

[shwetawankhade]

#21172

Hi Rhyse,

Thanks for your earlier clarification. I’m continuing to work with the FlexCase-S and had a few follow-up questions regarding the Raspberry Pi Compute Module 3+ (headless variant) inside the unit.

CM3+ Power-On Behavior
After powering the SmartCase, I’m not seeing any clear indication that the CM3+ has actually booted.
Could you share what the expected signs of a successful CM3+ startup are on this variant?
For example, are there any status LEDs on the board, or does the module take a certain amount of time before it becomes active?

Accessing the CM3+ Interface
Since this is a headless rpi setup, I want to understand the proper way to access the CM3+ interface for debugging and development.
We also need this access because part of our workflow involves verifying internal communication between the NXP S32K3 and the Raspberry Pi CM3+.
Could you guide us on the correct way to reach the CM3+ (e.g., SSH details, default hostname, or any other supported access method) so that we can confirm the connectivity and interaction between these two components?

[Audesse Team]

#21183

Hi Shweta,

Thank you for providing those clarifications regarding the FlexCase-S platform’s flashing procedures and its current lifecycle status.

I recommend that you look at the Compute Module 3+ (CM3+) datasheet for details on the operational characteristics and expectations for the CM3+ within the unit. A good starting point might be examining the power consumption as a first clue to understanding its operational status.

Regarding device interfacing, SSH is the recommended way to interface with the module.

I believe you have an S32K1 chip, as we have never shipped the CM3+ variant with the K3 processor. The SSH access details, which are the recommended interface for that module, were included on the pamphlet provided when the device was shipped if the default passwords are not working.

If the passwords are not working, and you are unable to access the device via SSH, you will most likely need to reflash the operating system.

Rhyse

[shwetawankhade]

#21325

Hi
I would like some clarification on how can I connect raspberry pi to the internet .I am going for using USB dongle but i wanna know what type of dongle is supported.

[shwetawankhade]

#21326

Hi
I would like some clarification on how can I connect raspberry pi to the internet .I am going for using USB dongle but i wanna know what type of dongle it supports.I have somehow figured out the rpi has pre installed drivers for RTL8192cu.Is there any other option i can connect rpi to the internet

[Audesse Team]

#21341

Hi Shweta,

We do not have a formal list of supported dongles. Your best bet would be to look up the supported chipsets based on the OS/Kernel present on the device. For the most likely success I would target an older chipset, which is popular. I’d probably target something USB2.0/fast Ethernet.

Best,

Rhyse

[Author]

Posts