carlos@dobleausa.com

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: Debug doesn't work with Arduino UNO or Mega #28836

    Hi,
    Could you be so kind as to answer my question below?
    Thanks,

    avr-gdb doesn’t exist in folder C:\Users\Carlos\Documents\ArduinoData\packages\arduino\tools\avr-gcc\7.3.0-atmel3.6.1-arduino7\bin
    How to install it and where can I download it?
    Regards,

    Carlos<div>How can I install it and where can I download it?</div>
    Regards,
    Carlos

    in reply to: Debug doesn't work with Arduino UNO or Mega #28790

    Support

    Please could you see bellow:

     

    When I tried to run the command line, you sent me,  I received the following error: avr-gdb is not recognized as an internal or external command

    I saw that avr-gdb is not in the folder :  “C:\Users\Carlos\Documents\ArduinoData\packages\arduino\tools\avr-gcc\7.3.0-atmel3.6.1-arduino7\bin”

    Regards,

     

    Carlos

    in reply to: Debug doesn't work with Arduino UNO or Mega #28762

    When I tried to run the command line, you sent me,  I received the following error: avr-gdb is not recognized as an internal or external command

    I saw that avr-gdb is not in the folder :  “C:\Users\Carlos\Documents\ArduinoData\packages\arduino\tools\avr-gcc\7.3.0-atmel3.6.1-arduino7\bin”

    Regards,

     

    Carlos

     

    support wrote:

    Please try opening the Command Prompt window and run the following command:
    C:\Users\Carlos\Documents\Ardu<wbr />inoData\packages\arduino\tools<wbr />\avr-gcc\7.3.0-atmel3.6.1-<wbr />arduino7\bin\\avr-gdb –interpreter mi “C:/Users/Carlos/source/repos/<wbr />ArduinoProject2/Output/Arduino<wbr />_Uno/Debug/ArduinoProject2.<wbr />ino.elf”
    Then please share a screenshot of the output and screenshots of any error messages you get while trying to run it.

    in reply to: Debug doesn't work with Arduino UNO or Mega #28761

    HI
    <div>avr-gdb doesn’t exist in folder C:\Users\Carlos\<wbr />Documents\ArduinoData\<wbr />packages\arduino\tools\avr-<wbr />gcc\7.3.0-atmel3.6.1-arduino7\<wbr />bin</div>
    <div>Regards,</div>
    <div></div>
    <div>Carlos</div>

    in reply to: Debug doesn't work with Arduino UNO or Mega #28759

    I ran it using the option Program and Start without Debugging in Debug menu and It ran ok.

    Deleting and recreating the program doesn’t eliminate the error.

    Regards,

     

    Carlos

    in reply to: Debug doesn't work with Arduino UNO or Mega #28757

    Here is the log you asked:

    C:\Users\Carlos\Documents\ArduinoData\packages\arduino\tools\avr-gcc\7.3.0-atmel3.6.1-arduino7\bin\\avr-gdb –interpreter mi “C:/Users/Carlos/source/repos/ArduinoProject2/Output/Arduino_Uno/Debug/ArduinoProject2.ino.elf”
    [ 0 ms] -gdb-version

    in reply to: Debug doesn't work with Arduino UNO or Mega #28752

    Please send me the link of how to do a GDB log. It didn’t come in your emails.

    Regards,

     

     

    in reply to: Debug doesn't work with Arduino UNO or Mega #28749

    Hi,
    <div>I think this is Log you asked me.</div>
    <div></div>
    <div>Initializing assemblies: 14 msec
    Registering factories: 157 msec
    Initializing VisualGDB 5.4.112.3309
    Checking fonts/colors: 12 msec
    Level 2 initialization: 1008 msec
    Arduino project is outdated due to C:\Users\Carlos\source\repos\<wbr />ArduinoProject2\Output\<wbr />Arduino_Uno\Debug\sketch\<wbr />ArduinoProject2.ino.cpp
    Arduino project is outdated due to C:\Users\Carlos\source\repos\<wbr />ArduinoProject2\Output\<wbr />Arduino_Uno\Debug\sketch\<wbr />ArduinoProject2.ino.cpp
    RenameHighlightSmartTaggerProv<wbr />ider: creating tagger for BuildOutput…
    Locating dependency paths for arduino:avr:uno: 0 msec
    ReportQueuedMessages()
    [+0] ReportQueuedMessages() – 1 queued messages
    [+6] ReportQueuedMessages()
    [+0] ReportQueuedMessages() – 1 queued messages
    [+1569] ReportQueuedMessages()
    [+0] ReportQueuedMessages() – 1 queued messages
    [+1] ReportQueuedMessages()
    [+0] ReportQueuedMessages() – 1 queued messages
    Launching gdbserver…
    ExecuteRawCommand(-gdb-<wbr />version, d)
    [+25] GDB command result:
    [+0] ExecuteRawCommand(version, e)
    [+0] Aborting commands: (True/True)
    [+0] ExecuteRawCommand(-list-<wbr />features, d)
    [+0] Aborting commands: (True/True)
    [+0] ExecuteRawCommand(-gdb-set disassembly-flavor intel, d)
    [+0] Aborting commands: (True/True)
    [+0] ExecuteRawCommand(-gdb-set print demangle off, d)
    [+0] Aborting commands: (True/True)
    [+75] ExecuteRawCommand(-gdb-set stop-on-solib-events 1, d)
    [+0] Aborting commands: (True/True)
    Unexpected exception: GDB session exited prematurely. Please verify that the project is built, the selected GDB binary exists and the working directory is specified correctly.
    —————— xi1+p ——————
    xi1+p: GDB session exited prematurely. Please verify that the project is built, the selected GDB binary exists and the working directory is specified correctly.
    at xi1.l()
    at rt1.c_2()
    at VisualGDB.GDBDebugEngine.j1(nc b, z a)
    Unexpected exception: GDB session exited prematurely. Please verify that the project is built, the selected GDB binary exists and the working directory is specified correctly.
    —————— xi1+p ——————
    xi1+p: GDB session exited prematurely. Please verify that the project is built, the selected GDB binary exists and the working directory is specified correctly.
    at xi1.l()
    at rt1.c_2()
    at VisualGDB.GDBDebugEngine.j1(nc b, z a)
    [+7963] ExecuteRawCommand(-gdb-exit, d)
    [+0] Aborting commands: (True/True)
    RenameHighlightSmartTaggerProv<wbr />ider: creating tagger for DebugOutput…</div>

Viewing 8 posts - 1 through 8 (of 8 total)