[support]

Hi,

We have fixed this in the updated nRF5x BSP. Please download the new version via Tools->Embedded Tools Manager.

[support]

Hi,

Strange. If you are sure that the output window did not contain any other text or error messages, please feel free to send us the project causing this so that we could fix that. If VisualGDB skips some relevant error messages, we would rather fix it.

[support]

Can you share the toolchain test log? Alternatively you can ignore the toolchain testing error, create your project and try to build it. Do you get a meaningful error message that way?

[support]

Yes, but that would involve editing the BSP XML files.

We don’t have much documentation on that, so you can either try experimenting with the BSP.XML file in %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\<ID> or look through our open-source BSP generators: https://github.com/sysprogs/BSPTools/

[support]

Hi,

If you are compiling the code on Raspberry Pi, please open VisualGDB Project Properties, go to the IntelliSense Settings page and reload all include directories. If you are using a cross-compiler, simply resynchronize the sysroot from the Build Settings page of VisualGDB Project Properties.

[support]

Hi,

Please check the Output window for further details on the error. If this does not help, please share the contents of the Output window here so that we could help you.

[support]

Good to know.  Let us know if you encounter further problems.

[support]

Hi,

Yes, please change the function declaration as follows:

static inline void __attribute__((__optimize__(0, "omit-frame-pointer"))) bootloader_util_reset(uint32_t start_addr)

[support]

Hi,

Sorry, but OpenOCD is quite fragile and we only support the Windows binaries that we built and tested ourselves. You are welcome to experiment with Linux builds of the ESP8266 of OpenOCD, but you’ll have to do trial-and-error to figure out what’s wrong.

[support]

No problem!

[support]

Hi,

Thanks for the project, we have fixed the problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.612.msi

[support]

OK, we’ve compared our bootloader to the esptool.py once again and it looks like the only difference is that esptool.py retries the sync several times after each reset. Can you try replacing the Sync() method in the bootloader test tool with this:

        public void Sync()
        {
            _Port.SetTimeouts(500, 1, 500, 0, 0);
  
            List<byte> syncMagic = new List<byte> { 0x07, 0x07, 0x12, 0x20 };
            for (int i = 0; i < 32; i++)
                syncMagic.Add(0x55);

            for (int i = 0; ; i++)
            {
                try
                {
                    if (i % 5 == 0)
                    {
                        _Port.EscapeFunction(SerialPortStream.CommFunction.CLRDTR);
                        _Port.EscapeFunction(SerialPortStream.CommFunction.SETRTS);
                        Thread.Sleep(5);
                        _Port.EscapeFunction(SerialPortStream.CommFunction.SETDTR);
                        _Port.EscapeFunction(SerialPortStream.CommFunction.CLRRTS);
                        Thread.Sleep(5);
                        _Port.EscapeFunction(SerialPortStream.CommFunction.CLRDTR);
                        Thread.Sleep(5);
                    }

                    _Port.Purge();
                    RunCommand(Command.ESP_SYNC, syncMagic.ToArray());
                    for (int j = 0; j < 7; j++)
                        RunCommand(Command.ESP_NO_COMMAND);
                    _Port.SetTimeouts(5000, 0, 5000, 0, 0);
                    return;
                }
                catch (Exception ex)
                {
                    if (i >= 20)
                        throw;

                    Console.WriteLine("Exception: " + ex);
                    Console.WriteLine("Extra output from COM port:");
                    for (;;)
                    {
                        byte[] data = new byte[512];
                        int done = _Port.Read(data, 0, data.Length);
                        if (done == 0)
                            break;
                        Console.Write(Encoding.ASCII.GetString(data, 0, done));
                    }
                    Console.WriteLine("-----------------------");
                }
            }
        }

If this does not help, please try running this version of esptool.py and attach its output. It should show what is sent to the device and when the device replies.

[support]

Hi,

Thanks for the feedback, we will investigate the complexity of checking out .vgdbsettings and Makefiles prior to modification and add this feature to either 5.1 or 5.2.

Note that you can disable the creation of the .old files via Tools->Options->VisualGDB->General->Tweaking->Create .old files.

[support]

Yes, please refer to the following post: http://stackoverflow.com/questions/2222162/how-to-apply-gcc-fvisibility-option-to-symbols-in-static-libraries

[support]

No problem. We always try to be transparent about things we support and don’t support and we always welcome feedback.

Feel free to share your findings on the _48 problem and do not hesitate to ask for further advice if you get stuck.

[Author]

Posts