STM32 REMOTE DEBUG

[psain.1]

Hello,

I have designed several custom boards based on STM32 MCUs, And are running fine problem is i have installed these across the country over 50 locations and now it very costly to go to each location for for required software updates or to debug if any issue arises.

What i thought that i will put and ESP32 and a small display on the board. So that whenever i need to debug the system i will simply ask client to connect system to the available wi-fi and will get remote debug interface and do whatever i need to do.

I can use any STM32 MCU series, cost is not an issue.. But it has to be MCU not a windows or Linux system.

1. Is it possible to do that.

2. If yes.. then how to proceed? what would be the components required and system architecture?

 

[Pavel A.]

For inspiration... memfault.com

 

[psain.1]

doesn't full fil my requirement

[Tesla DeLorean]

Design your stuff so it's easy to debug, diagnose, and update. Have standard (ubiquitous) modes of connectivity, observation and control

Use RemotePC

 

>>But it has to be MCU not a windows or Linux system

Yeah, but WHY? You can make head-less systems.

Because of familiarity? You've got a lot of experience executing?

[psain.1]

Actually the space limitation the pc installation is not possible

[MM..1]

Completely lost your idea. You say use ESP32 and then STM32 ?  You mean next STM32 ahead your target used as STLINK between MCU1 and ESP32 ? Why not use normal STLink ?

But any choiced , i mean remote gdb can run only on host OS, that you restrict. Then ?

For simple remote debuging your remote system require only SWD conector and STlink connected to some hw with run gdbserver and forward debug session port on router. 

Your idea ESP conncted on remote place to wifi is security flaw and good network admin dont allow this.

[Tesla DeLorean]

I'm assuming ESP32 in terms on conjuring a WiFi link, but as you point out nobody wants your equipment on their corporate network, tunnelling out to the broader internet.

Not even photocopiers or food chillers. Documented examples of vunerabilities and data exfiltration.

Cellular modems, perhaps, but definitely a walled-garden with no connectivity on to corporate network internally.

I can find Chrome / Android / LINUX / Win10 boxen for under $99 that would make a good VNC platform. Probably a RPi Pico CMSIS-DAP for "debug" if you need to single-step your own code to understand how it behaves.