Interest in developer preview?

[rudi ;-)]

[ advanced note ]

AES_IDLE_REG

*) i have not used this in preview code, for certain reasons.
but want now use - not sure - so i ask:

in technical reference manual read,
we wait for AES_IDLE_REG until reads 1

*) just in time missed a VAR for it or a define.

in esp32_technical_reference_manual_en

AES_IDLE_REG is described on side 116 with address 0x3FF01004

for a try i added directly in eagle.fpga32.rom.addr.v7.ld

Code: Select all

..
PROVIDE (AES_IDLE_REG = 0x3FF01004 );
..

and define in global app code

Code: Select all

..
extern int AES_IDLE_REG;
..

in app code i wait for the AES_IDLE_REG reads 1

Code: Select all

..
while ( AES_IDLE_REG != 1) ;
..

not sure - is this just in time the right way for AES_IDLE_REG ? ( int ? )
compile & link done - can't test flash - have no modul with esp32 release.

edit: ( S. 117 )
but think this is not the right way, because
register 10.2: AES_IDLE_REG (0x004)
is 32bit

your further help and critical ("never change the ld file" )
is welcome

best wishes
rudi

[rudi ;-)]

...
full app with decrypt comes asap in example code folder
..

for a flashing you must wait
i have no modul from ESP32 Release
..

uploaded a demo (beta ) code with crypt and decrypt.


best wishes
rudi

[jmattsson]

Whoa... no kidding that things have changed!

This is going to take a while to digest...

@ESP_Sprite: Do you know if the ESP8266 will get a similar IDF (to replace the RTOS-SDK, perhaps)?

[ESP_Sprite]

ESP-IDF for the ESP8266: Maybe. It should be pretty easy to take the existing binary libraries and put them into the ESP-IDF framework, that's not an issue. To make support for the ESP8266 in ESP-IDF as full-featured as the ESP32 is, is a different story. We're not sure what the plans are with regards to that.

[jmattsson]

Thanks for the update! At the moment it feels like the esp8266 and esp32 sdks are diverging rather than converging, and I'm trying to figure out the best way for the NodeMCU project to support both platforms with as little maintenance effort as possible. From a "lazy developer" point of view, I'd love to see the esp8266 sdk take the same path (and pace) as the esp32.

[ESP_igrr]

jmattsson: are you interested in getting the 8266 RTOS or non-OS SDK within ESP-IDF?

[jmattsson]

@igrr__: The RTOS SDK. I don't really consider it feasible to support a non-OS SDK ESP8266 and a RTOS SDK ESP32 in the same code branch. And the RTOS is much nicer to work with, even if it comes at a bit of a memory cost.

[cvgaviao]

Okay, we released the SDK.

Well, I have to congrats the Espressif team for this excellent job.
I tried the ESP-IDF today. its embedded documentation is clean and it is much easier to setup than ESP8266 one.
the menu config is awesome !

thank you all, well done !!!

[jmattsson]

Having now actively worked with the IDF over the last week, I must say this is really, really nice! Despite it still being the early days, it's feeling very slick, powerful and friendly. Sure, the docs are still a bit short in quantity, but certainly not in quality.

And while I've certainly got a soft spot for the old NonOS-SDK's rough, hackish charm, there's just no comparison. The IDF is already feeling like a mature offering and I can only see it getting better. Great work, everyone!