Search found 11 matches
- Fri Sep 06, 2019 10:35 am
- Forum: ESP-IDF
- Topic: [JTAG] [openocd] Error: DIR instruction generated an overrun!
- Replies: 2
- Views: 4349
Re: [JTAG] [openocd] Error: DIR instruction generated an overrun!
Thanks, it works ! I went into the both cfg files (esp-wroom-32.cfg & jlink.cfg) and wrote adapter_khz 10000 . The problem is that openocd used to say that 20000khz is to much and change it to 15000khz. But 15000khz is still too much so it gives an error but that error do not mention any speed issue...
- Thu Sep 05, 2019 12:22 pm
- Forum: ESP-IDF
- Topic: [JTAG] [openocd] Error: DIR instruction generated an overrun!
- Replies: 2
- Views: 4349
[JTAG] [openocd] Error: DIR instruction generated an overrun!
So I have that error since severals days: Hardware Esp32 devkit v1 Wroom32 With Jtag port (those 6 little dots) jtag interface: SEGGER jlink Problem I type: bin\openocd -s share\openocd\scripts -f interface\jlink.cfg -f board\esp-wroom-32.cfg -c "program_esp32 c:\xxxxxxxxxxxxxxxxxxxxxxx\bootloader.b...
- Tue Sep 03, 2019 8:00 am
- Forum: ESP-IDF
- Topic: [JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
- Replies: 1
- Views: 5911
Re: [JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
Just found an explanation.
Somehow, the ft2223h forces some pin to 2.5v and so those pin are considered as "high", that's why I got the "all one" error. This 2.5v level is constant and can't be changed so no information can be exchanged.
So I guess my ft2232h jtag interface is broken.
Somehow, the ft2223h forces some pin to 2.5v and so those pin are considered as "high", that's why I got the "all one" error. This 2.5v level is constant and can't be changed so no information can be exchanged.
So I guess my ft2232h jtag interface is broken.
- Tue Sep 03, 2019 8:00 am
- Forum: Hardware
- Topic: [JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
- Replies: 1
- Views: 4567
Re: [JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
Just found an explanation.
Somehow, the ft2223h forces some pin to 2.5v and so those pin are considered as "high", that's why I got the "all one" error. This 2.5v level is constant and can't be changed so no information can be exchanged.
So I guess my ft2232h jtag interface is broken.
Somehow, the ft2223h forces some pin to 2.5v and so those pin are considered as "high", that's why I got the "all one" error. This 2.5v level is constant and can't be changed so no information can be exchanged.
So I guess my ft2232h jtag interface is broken.
- Mon Sep 02, 2019 8:46 am
- Forum: Hardware
- Topic: [JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
- Replies: 1
- Views: 4567
[JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
So I have that error since severals weeks and tried many solutions but no one worked. Hardware - Esp32 devkit v1 - Wroom32 With Jtag port (those 6 little dots) - jtag interface: ftdi ft2232H Problem I type: bin\openocd -s share\openocd\scripts -f interface\ftdi\esp32_devkitj_v1.cfg -f board\esp-wroo...
- Thu Aug 29, 2019 9:08 am
- Forum: ESP-IDF
- Topic: [JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
- Replies: 1
- Views: 5911
[JTAG] [openocd] Error: JTAG scan chain interrogation failed: all ones
So I have that error since severals weeks and tried many solutions but no one worked. Hardware - Esp32 devkit v1 - Wroom32 With Jtag port (those 6 little dots) - jtag interface: ftdi ft2232H Problem I type: bin\openocd -s share\openocd\scripts -f interface\ftdi\esp32_devkitj_v1.cfg -f board\esp-wroo...
- Thu Jul 11, 2019 10:39 am
- Forum: ESP-IDF
- Topic: Security problem in pairing mode (AT+BLEENC)
- Replies: 3
- Views: 5303
Re: Security problem in pairing mode (AT+BLEENC)
I opened the samed issue on the git and had a quick response: we can't set a pairing key for the moment. The feature may be added in the future
https://github.com/espressif/esp32-at/issues/219
https://github.com/espressif/esp32-at/issues/219
- Thu Jul 11, 2019 8:43 am
- Forum: ESP-IDF
- Topic: Security problem in pairing mode (AT+BLEENC)
- Replies: 3
- Views: 5303
Re: Security problem in pairing mode (AT+BLEENC)
Thank you, it works ! I didn't think that it would need an AT security configuration plus a service.bin perm configuration.
I still have an problem, but different: Is it possible to set a static pairing key ?
For the moment, the pairing key is set automaticly with "+BLESECNTFYKEY:0,xxxxxx".
I still have an problem, but different: Is it possible to set a static pairing key ?
For the moment, the pairing key is set automaticly with "+BLESECNTFYKEY:0,xxxxxx".
- Wed Jul 10, 2019 7:36 am
- Forum: ESP-IDF
- Topic: [AT command] Add "at_customize.bin" and "service bin" directly from the ESP32
- Replies: 3
- Views: 5692
Re: [AT command] Add "at_customize.bin" and "service bin" directly from the ESP32
Hi, in fact there are differents firmware "levels". I resolved my problem so here is a little explenation: 1. When you buy an esp there is the basic firmware with basic AT commands. 2. If you want Bluetooth Low Energy AT commands, we must flash the firmware, you can check this tutorial . 3. If you w...
- Tue Jul 09, 2019 4:46 pm
- Forum: ESP-IDF
- Topic: Security problem in pairing mode (AT+BLEENC)
- Replies: 3
- Views: 5303
Security problem in pairing mode (AT+BLEENC)
Hi, AT+BLEENC seems to work only if a device is connected, wich is concerning because the client can write/read during a short period of time without any permission. For the context, here is a git issue tackling the problem but without solution: https://github.com/espressif/esp32-at/issues/45 Did I ...