Build run: https://github.com/rsaxvc/openocd-esp32-zomgsofast/actions/runs/13296869712/
Linux build: https://github.com/rsaxvc/openocd-esp32-zomgsofast/actions/runs/13296869712/artifacts/2582283547
Windows build: https://github.com/rsaxvc/openocd-esp32-zomgsofast/actions/runs/13296869712/artifacts ...
Search found 5 matches
- Thu Feb 13, 2025 12:15 am
- Forum: ESP-IDF
- Topic: Profiling on Espressif MCUs woes
- Replies: 27
- Views: 19127
- Wed Feb 12, 2025 11:20 pm
- Forum: ESP-IDF
- Topic: Profiling on Espressif MCUs woes
- Replies: 27
- Views: 19127
Re: Profiling on Espressif MCUs woes
Samuel Obuch had an issue using it, and I traced it to a VAXism in gprof. Until that can be addressed, histogram resolution is reduced for gprof compatibility. Also having a bit of trouble with the github builder today.
- Thu Feb 06, 2025 3:53 am
- Forum: ESP-IDF
- Topic: Profiling on Espressif MCUs woes
- Replies: 27
- Views: 19127
Re: Profiling on Espressif MCUs woes
I've got a new update that handles profiling with sparse memory maps by emitting multiple histograms - the sampling is now full resolution(instruction-accurate) with only 100-200KB typical filesize.
- Sat Dec 14, 2024 8:20 pm
- Forum: General Discussion
- Topic: RISC-V HardFP ABI
- Replies: 3
- Views: 3084
RISC-V HardFP ABI
I've noticed that function calls with floating point arguments are a little heavier than on RISC-V and ARM32, for the same GCC12.2.0, due to the ABI in use. Here's a trivial example:
float fmac(float a, float b, float c) {
return a * b + c;
}
RISC-V, F-ABI(not for ESP chips):
fmac(float ...
float fmac(float a, float b, float c) {
return a * b + c;
}
RISC-V, F-ABI(not for ESP chips):
fmac(float ...
- Wed Mar 27, 2024 2:07 am
- Forum: ESP-IDF
- Topic: ESP32 websocket client misses first received message
- Replies: 5
- Views: 26543
Re: ESP32 websocket client misses first received message
One case seems to be if the server responds over HTTP during the protocol change: https://github.com/espressif/esp-protocols/issues/396
If you have control of the server, you may try to delay sending to the client until the protocol change to websocket is completed.
If you have control of the server, you may try to delay sending to the client until the protocol change to websocket is completed.