It's certainly possible to extract the IP address, although I'm not proficient in bash scripting. You might want to explore regular expressions (regex) for this purpose.

However, I'd like to reiterate the importance of understanding the underlying problem you're trying to solve. Currently, you're ...

How about the otherway around? So the esp uploads to a server?
Or use a broadcast message when the device boots that the other device detects.

btw, still not explaining what the underlying problem is that you want to solve.

What is the underlying problem you want to solve?
What you want is possible, but I have a gut feeling that it's not the right solution.

Why not like this?
Its a bit speudo but you get the idea.



enum LedModes
{
Off,
Blink,
On,
}
LedModes mode;

void Main()
{
Timer.SetInterval(blinkSpeed);
Timer.Start();
}

void TimerCallback
{
if(mode == Off && GetLed() == 1)
{
SetLed(0);
}

if(mode == Blink)
{
if(GetLed() == 1 ...

https://docs.docker.com/desktop/wasm/
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-docker-image.html#esp-idf-docker-image

This might be simpler, just run a container with the tool chain to compile whatever you want. Also, when a new tool chain becomes available ...

I've used this in the past to upload an angular application to the esp.

https://github.com/nopnop2002/esp-idf-ftpServer

It seems something in my memory is messed up.

Hello,

While debugging I end up in xtensa_vector.S.
Specifically under _DoubleExceptionVector at break 1, 4

Any suggestions how to figure out what triggers this?
The callstack is useless since this is an interrupt ...

I get what you're saying, but that would create a problem of itself:
Let's assume:
V1 stores the settings in NVS
V2 stores the settings in JSON

After boot, we don't know the previous version, It could be V1 or V2. In order to check what the previous version was, I need to read the settings. But I ...

Hello,

I have the following (hypothetical) scenario:
In V1 the settings are stored using NVS.
In V2 the settings are stored to FAT using JSON.

Now, when V1 is running in the field and a firmware update comes along, the settings from the NVS should be converted, so the system keeps running with the ...