RISC-V Bytes: Exploring a Custom ESP32 Bootloader
danielmangum.com
RISC-V Bytes: Exploring a Custom ESP32 Bootloader
1–9 of 9 posts
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#2PSA - only the C family of ESP32 are RISC-V, the others are Xtensa.
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#3PSA - only the C family of ESP32 are RISC-V, the others are Xtensa.
Legacy chips are Xtensa.
Espressif has already decided to use RISC-V exclusively[0].
0. https://www.eenewseurope.com/en/espressif-moves-exclusively-...
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#4Very good blog post.
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#5PSA - only the C family of ESP32 are RISC-V, the others are Xtensa.
Legacy chips are Xtensa. Espressif has already decided to use RISC-V exclusively[0]. 0. https://www.eenewseurope.com/en/espressif-moves-exclusively-...
Having bought esp32 modules lately, let me tell you there's plenty of xtensa based ones still for sale.
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#6Earlier quoted context omitted.
Legacy chips are Xtensa. Espressif has already decided to use RISC-V exclusively[0]. 0. https://www.eenewseurope.com/en/espressif-moves-exclusively-...
Having bought esp32 modules lately, let me tell you there's plenty of xtensa based ones still for sale.
ESP32 will always be Xtensa. (They're hardly going to change CPU architecture without updating the model name!) Same as ESP32-S2 and ESP32-S3.
ESP32-Cx, ESP32-Hx, ESP32-Px etc are or will be RISCV.
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#7Earlier quoted context omitted.
Legacy chips are Xtensa. Espressif has already decided to use RISC-V exclusively[0]. 0. https://www.eenewseurope.com/en/espressif-moves-exclusively-...
Having bought esp32 modules lately, let me tell you there's plenty of xtensa based ones still for sale.
Yes. The legacy ones.
Obviously, nobody would trust Espressif if they didn't guarantee availability of parts for n years. The existing Xtensa parts are not disappearing overnight.
New parts will be RISC-V.
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#8Earlier quoted context omitted.
Having bought esp32 modules lately, let me tell you there's plenty of xtensa based ones still for sale.
Yes. The legacy ones. Obviously, nobody would trust Espressif if they didn't guarantee availability of parts for n years. The existing Xtensa parts are not disappearing overnight. New parts will be RISC-V.
I would bet the number of people who program the ESP32 and know anything much about the Xtensa ISA or care which ISA is used would be pretty small. They will be just "It's some weird ISA no none uses, but Espressif give us a compiler for it so it's fine".
Of course Cadence do license Xtensa to many of their EDA customers for use in some core that's not visible to the outside world. They support it, it's easier than dealing with ARM etc. Now there is RISC-V it's probably getting very few new customers, though Tensilica/Cadence do have a very nice system for adding custom instructions and automatically generating things such as the toolchain for them.
ESP32 is probably one of very few places where 3rd party programmers have access to an underlying Xtensa CPU.
I worked on software for some internal chip at Samsung where the documentation didn't give the ISA a name but just listed what the instructions where. "Hmmm", I thought, "there are 16 and 24 bit long instructions -- that sounds familiar". I checked, and the opcodes matched up to Xtensa. Plus a few custom ones.
I will say Xtensa is a heck of a lot better than the home-grown ISA inside FTDI products! It is not normally exposed, but they have one product, the VNC2, which 3rd parties can program. It is AWFUL. (I'm only assuming they use the same ISA in their other products, but probably...)
Re: RISC-V Bytes: Exploring a Custom ESP32 Bootloader
#9PSA - only the C family of ESP32 are RISC-V, the others are Xtensa.
For the record, the ESP32-H2 is also RISC-V, but this is a quibble on a module that is still vapour as far as I can tell.