nevyn

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • in reply to: ESP32 An existing connection was forcibly closed #23071

    nevyn
    Participant

    Forgot to mention, the same project deployed to a WROVER-KIT has always worked with no issues when deployed from the same PC.

    Regards,
    Mark

    in reply to: ESP32 An existing connection was forcibly closed #23069

    nevyn
    Participant

    PC has Windows Defender as the only firewall/AV and I have turned it off temporarily.

    Started a debug session and the GDB Session reports Remote communication error.  Target disconnected.: No error.

    OpenOCD log:

    C:\SysGCC\esp32\esp32-bsp\OpenOCD\bin\openocd.exe -c "gdb_port 50810" -c "telnet_port 50811" -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -c "adapter_khz 3000" -f target/esp32.cfg -c "echo VisualGDB_OpenOCD_Ready"
    Open On-Chip Debugger 0.9.0 (2018-10-12)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    adapter speed: 3000 kHz
    Info : auto-selecting first available session transport "jtag". To override use 'transport select '.
    esp32 interrupt mask on
    VisualGDB_OpenOCD_Ready
    Info : clock speed 3000 kHz
    Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
    Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    cpu0: Current bits set: BreakIn BreakOut RunStallIn
    cpu1: Current bits set: none
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : Target halted. PRO_CPU: PC=0x00000000 (active) APP_CPU: PC=0x00000000
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : accepting 'gdb' connection on tcp/50810
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : Target halted. PRO_CPU: PC=0x40007BA1 (active) APP_CPU: PC=0x00000000
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
    Info : esp32: Core was reset (pwrstat=0xFF, after clear 0xFF).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
    Info : esp32: Core was reset (pwrstat=0xFF, after clear 0xFF).
    Info : Target halted. PRO_CPU: PC=0x00000000 (active) APP_CPU: PC=0x00000000
    Info : Flash mapping 0: 0x3ffc0590 -> 0x3ffc0590, 1048321 KB
    Info : Flash mapping 1: 0x3ffc0590 -> 0x3ffc0590, 1048321 KB
    Info : Flash mapping 2: 0xc35c38 -> 0x23f8a014, 10559 KB
    Info : Flash mapping 3: 0x1378fb8 -> 0x134de78, 19932 KB
    Info : Flash mapping 4: 0xa4fccc -> 0x4921f9, 19939 KB
    Info : Flash mapping 5: 0x17 -> 0x1482608, 4543 KB
    Info : Flash mapping 6: 0x13698c0 -> 0x23f8a044, 10559 KB
    Info : Flash mapping 7: 0xa4fcc8 -> 0x224, 6457 KB
    Info : Flash mapping 8: 0x1 -> 0x2b, 19767 KB

    plus more of the same.

    GDB Session Log:

    The first line has the telnet port and GDB port off by 1, is this correct?

    Regards,
    Mark

    • This reply was modified 2 years, 2 months ago by  nevyn.

    nevyn
    Participant

    Looks like this has fixed the issue.

    Thank you for the quick turn around,
    Mark


    nevyn
    Participant

    Deleting the cache and CodeDB folders did not help.

    Created a new project based upon Blinky and then copied the code and header files across into the new project.  Deleted blinky.c and then added the copied files using Add Existing Item.  Still seeing the same problem.

    Used the wizard to create a new Import project, still seeing heh same problem.

    Regards
    Mark

    in reply to: ESP32 5.2.0 R13 Toolchain Problems #22190

    nevyn
    Participant

    Solved this by removing the ESP32 toolchain, installing latest preview and then installing the ESP32 toolchain once more.

    Regards
    Mark

    in reply to: ESP32 Toolchain 5.2.0 R12 #21917

    nevyn
    Participant

    Installed OK through Manage VisualGDB Packages menu item.

    Thanks for the quick response,
    Mark


    nevyn
    Participant

    Been investigating this over the last couple of days.  Moved to a different board and I’m getting good results with that.

    Back to the original board as I have to get code working on it.  Given that the code works on the second board I wondering if it could be a connection / wiring problem.

    Regards,
    Mark


    nevyn
    Participant

    Restarted the computer and recompiled the program, tried to debug.

    Failed to connect to the debug stub.  Please click View gdb stub log to see the detailed gdb stub output.

    If I do this then you see the text above.  Clicking the Ignore button to get to the openocd shows similar text to the second log above.  The gdb log shows text similar to the first message above.

    Regards,

    Mark


    nevyn
    Participant

    Using the Test button I get the message Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host

    I powered off the board and disconnected the JTAG debugger.  Powered on the board and then reconnected the debugger.

    Output becomes:

    c:\SysGCC\esp32\esp32-bsp\OpenOCD\bin\openocd.exe -c "gdb_port 50099" -c "telnet_port 50100" -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -c "adapter_khz 3000" -f target/esp32.cfg -c "echo VisualGDB_OpenOCD_Ready"
    Open On-Chip Debugger 0.9.0 (2018-07-30)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    adapter speed: 3000 kHz
    Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
    esp32 interrupt mask on
    VisualGDB_OpenOCD_Ready
    Info : clock speed 3000 kHz
    Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
    Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    cpu0: Current bits set: BreakIn BreakOut RunStallIn
    cpu1: Current bits set: none
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : accepting 'gdb' connection on tcp/50099
    Info : Target halted. PRO_CPU: PC=0x40007BA1 (active) APP_CPU: PC=0x00000000
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).
    Info : esp32: Debug controller was reset (pwrstat=0xE5, after clear 0x5F).
    Info : Target halted. PRO_CPU: PC=0x00000000 (active) APP_CPU: PC=0x00000000
    Info : Flash mapping 0: 0x3ffc0590 -> 0x3ffc0590, 1048321 KB
    Info : Flash mapping 1: 0x3ffc0590 -> 0x3ffc0590, 1048321 KB
    Info : Flash mapping 2: 0x0 -> 0x5f4924a4, 10559 KB
    Info : Flash mapping 3: 0x4b68ca0 -> 0x4b616d8, 77295 KB
    Info : Flash mapping 4: 0xa4fccc -> 0x4921f9, 77219 KB
    Info : Flash mapping 5: 0x17 -> 0x3512930, 4543 KB
    Info : Flash mapping 6: 0x4b6cf58 -> 0x5f4924f4, 10559 KB
    Info : Flash mapping 7: 0xa4fcc8 -> 0x254, 6457 KB
    Info : Flash mapping 8: 0x1 -> 0x24, 77189 KB
    Info : Flash mapping 9: 0x4b7bfa0 -> 0x0, 4516 KB
    Info : Flash mapping 10: 0x0 -> 0xa4fccc, 77189 KB
    Info : Flash mapping 11: 0x756cc870 -> 0x5bed4406, 4194303 KB
    Info : Flash mapping 12: 0x756b7084 -> 0x60161f, 77188 KB
    Info : Flash mapping 13: 0x6c666d -> 0x6c68fe, 77188 KB
    Info : Flash mapping 14: 0x1f -> 0x2c5b560, 0 KB
    Info : Flash mapping 15: 0x4b68ca0 -> 0xa4fca4, 0 KB
    Info : Flash mapping 16: 0xa4ffcc -> 0x4b616d8, 0 KB
    Info : Flash mapping 17: 0x4b7db68 -> 0xa4fd4c, 4502 KB
    Info : Flash mapping 18: 0x4b616d8 -> 0x64d850, 0 KB
    Info : Flash mapping 19: 0x64dbf0 -> 0x64da18, 77371 KB
    Info : Flash mapping 20: 0x4b8eba0 -> 0x604f7f, 77138 KB
    Info : Flash mapping 21: 0xa4fd01 -> 0x0, 22752 KB
    Info : Flash mapping 22: 0x0 -> 0x10, 0 KB
    Info : Flash mapping 23: 0x186a0 -> 0x1, 4194303 KB
    Info : Flash mapping 24: 0x0 -> 0x74d9ec, 0 KB
    Info : Flash mapping 25: 0xfffffffc -> 0x0, 0 KB
    Info : Flash mapping 26: 0x220 -> 0x1a0, 0 KB
    Info : Flash mapping 27: 0x2c5b7c8 -> 0x1a0, 45418 KB
    Info : Flash mapping 28: 0x7031bcdd -> 0xa4fdac, 1838214 KB
    Info : Flash mapping 29: 0x2c5b878 -> 0x2c60b30, 1838214 KB
    Info : Flash mapping 30: 0x70321b37 -> 0x2c5abb8, 0 KB
    Info : Flash mapping 31: 0xa4fdd0 -> 0x0, 0 KB
    Info : Flash mapping 32: 0x100 -> 0x1, 0 KB
    Info : Flash mapping 33: 0xac28e3be -> 0xa4fdd8, 10559 KB
    Info : Flash mapping 34: 0x74b05aeb -> 0x1a0, 0 KB
    Info : Flash mapping 35: 0xa4fdd0 -> 0xa4fe0c, 1911830 KB
    Info : Flash mapping 36: 0xa4ffcc -> 0x74b0a560, 0 KB
    Info : Flash mapping 37: 0x5f492544 -> 0x4b68fcc, 4500 KB
    Info : Flash mapping 38: 0x1a0 -> 0x1, 4 KB
    Info : Flash mapping 39: 0xa4fe0c -> 0x4, 1955955 KB
    Info : Flash mapping 40: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 41: 0x1 -> 0xc3b4, 128 KB
    Info : Flash mapping 42: 0x3510000 -> 0x0, 0 KB
    Info : Flash mapping 43: 0x4b4af90 -> 0x4b4af91, 6455 KB
    Info : Flash mapping 44: 0xa4feb8 -> 0x467ad7, 6455 KB
    Info : Flash mapping 45: 0x4b4af90 -> 0xffffffff, 4505 KB
    Info : Flash mapping 46: 0x466bb0 -> 0x466010, 77285 KB
    Info : Flash mapping 47: 0xffffffff -> 0x3512930, 0 KB
    Info : Flash mapping 48: 0x3511824 -> 0x3512930, 0 KB
    Info : Flash mapping 49: 0x3511824 -> 0xa4feb8, 4103 KB
    Info : Flash mapping 50: 0x3512930 -> 0x6381ed, 54341 KB
    Info : Flash mapping 51: 0x6381f4 -> 0x6381ac, 1955955 KB
    Info : Flash mapping 52: 0xa4ffcc -> 0x756cc870, 54341 KB
    Info : Flash mapping 53: 0x1d -> 0x3511824, 6337 KB
    Info : Flash mapping 54: 0xd -> 0x3511720, 0 KB
    Info : Flash mapping 55: 0x0 -> 0x1d, 54342 KB
    Info : Flash mapping 56: 0xa4ff80 -> 0x4013eb, 0 KB
    Info : Flash mapping 57: 0x3511720 -> 0x3511b30, 0 KB
    Info : Flash mapping 58: 0x1e3f8eac -> 0xa4ff08, 1956248 KB
    Info : Flash mapping 59: 0xffffffff -> 0xcccccccc, 3355443 KB
    Info : Flash mapping 60: 0xcccccccc -> 0xcccccccc, 3355443 KB
    Info : Flash mapping 61: 0xcccccccc -> 0xcccccccc, 3355443 KB
    Info : Flash mapping 62: 0x14c -> 0x8664, 10559 KB
    Info : Flash mapping 63: 0x34 -> 0x3511720, 54342 KB
    Info : Flash mapping 64: 0xf410a447 -> 0x0, 1561287 KB
    Info : Flash mapping 65: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 66: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 67: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 68: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 69: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 70: 0x0 -> 0x0, 4101 KB
    Info : Flash mapping 71: 0x401500 -> 0xa4ff94, 2884 KB
    Info : Flash mapping 72: 0x401500 -> 0x401500, 10559 KB
    Info : Flash mapping 73: 0x741c8674 -> 0x2d1000, 1902369 KB
    Info : Flash mapping 74: 0xdc57e7f0 -> 0xa4ffdc, 1956119 KB
    Info : Flash mapping 75: 0x2d1000 -> 0x1e3f8fa4, 0 KB
    Info : Flash mapping 76: 0x0 -> 0x2d1000, 0 KB
    Info : Flash mapping 77: 0x0 -> 0x0, 0 KB
    Info : Flash mapping 78: 0x1e3f8fa4 -> 0xa4ffa0, 0 KB
    Info : Flash mapping 79: 0xa4ffe4 -> 0x77657840, 1736097 KB
    Info : Flash mapping 80: 0x0 -> 0xa4ffec, 1956119 KB
    Info : Flash mapping 81: 0xffffffff -> 0x7766acf3, 0 KB
    Info : Flash mapping 82: 0x0 -> 0x401500, 2884 KB

    Regards,

    Mark

    in reply to: Import MSBuild Project #20335

    nevyn
    Participant

     

    Thank you for the quick reply.

    Is it possible to have a 30-day trial of the Embedded Quick View as this is not enabled in my licence?

    Regards,
    Mark

    in reply to: ESP32 – Cannot set hardware breakpoint #9985

    nevyn
    Participant

    The -Og change solved it.  Thought I’d followed the tutorial carefully, can’t believe I missed that.

    Thanks for the help,
    Mark

    in reply to: ESP32 – Cannot set hardware breakpoint #9974

    nevyn
    Participant

    I have just retried programming the chip and debugging as follows:

    1. Set project properties to Alway program, compiled the code.
    2. Reset the chip and hit debug to upload the code.
    3. Once complete I reset the properties to Assume programmed, reset the chip and then pressed F5.

    Doing this generates a SIGINT exception and the source windows shows the breakpoint in xPortGetCoreID method.

    If I run without the debugger attached and check the output on the COM port I get the following message:

    Guru Meditation Error of type IllegalInstruction occurred on core 0. Exception was unhandled.

    along with a register dump and traceback.  The chip then enters a cycle of software resets as the same error is generated over and over again.

    BTW – I’m using a Segger J-Link EDU.

    Regards
    Mark

    in reply to: ESP8266 Tutorials #6949

    nevyn
    Participant

    So I’ve made it through the Blinky LED tutorial so I know I can programme the device and even single step through the code.  First couple of times the device was prgrammed everything went OK.

    Today I have tried to reprogramme the chip and I get a dialog with the following:

    Loading ESP Firmware
    Tick beside Preparing Image
    Arrow icon -> Loading Image.

    The system just stops at that point.

    I’m using the J-Link Edu programmer and the LED on the programmer is flickering green.

    Regards
    Mark

    in reply to: ESP8266 Tutorials #6932

    nevyn
    Participant

    You were spot on, it was a wiring problem.

     

    Thanks for the help,
    Mark

    in reply to: ESP8266 Tutorials #6929

    nevyn
    Participant

    Would I be better using the Segger J-Link Edu if there are known reset issues with the USB-TINY-H?  The Edu version is supposed to be an educational / research version of the full J_Link product.

    I’ll double check the wiring later today.  That was one of the first things I verified but it does not harm to have another look.

    One thing I have noticed is that the Segger is outputting signals to the ESP8266 but the USB-TINY-H does not appear to output anything.

    I’ll report back later on what I find

    Thanks for the input,
    Mark

Viewing 15 posts - 1 through 15 (of 17 total)