Sysprogs forums › Forums › VisualGDB › ESP8266 project convert to Standalone
- This topic has 5 replies, 2 voices, and was last updated 6 years, 5 months ago by support.
-
AuthorPosts
-
July 9, 2018 at 13:59 #21313Andrzej.TParticipant
Hi,
When I try convert ESP8266 project to standalone, I get a message:
VisualGDB version: 5.4.3.2193 ------------------ System.NullReferenceException ------------------ System.NullReferenceException: Object reference not set to an instance of an object. at VisualGDB.Common_GUI.WPF.Property_pages.EmbeddedDebugPropertyPage2.ControllerImpl.TryUpdateProjectContext(sb2 newProjectContext, n8 ctx2) at s11.v.m(v c, sb2 a, n8 b) at s11.n1(sb2 a, h1 b) at s11.p(Boolean a, eb2 b, String d, Action c) at s11.v.d.b(Object a, eb2 b) at fl.i(Object b, EventArgs a) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame) at System.Windows.Window.ShowHelper(Object booleanBox) at System.Windows.Window.Show() at System.Windows.Window.ShowDialog() at nj.GDBProjectProperties.ExecuteForProject(nj addin, Object objPrj)
and then Visual Studio 2017 crashes.
A<span id=”result_box” lang=”en”>fter restarting Visual Studio and the compilation process I received a message: </span>
<span id="result_box" lang="en">cannot find entry symbol _start; not setting start address</span> 1>------------------- Memory utilization report ------------------- 1>Used SPIFLASH: 0 bytes out of 16MB (0%) [-219K] 1>Used INSTR_RAM: 0 bytes out of 32KB (0%) [-25K] 1>Used DATA_RAM: 0 bytes out of 80KB (0%) [-25K]
I could ask for help in solving the problem.
Regards
Andrzej.TJuly 9, 2018 at 20:07 #21318supportKeymasterHi,
Thanks for reporting this, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2348.msi
July 10, 2018 at 07:19 #21324Andrzej.TParticipantThanks a lot.
But now debugging not working, the Segger J-Link debugging method has disappeared.July 10, 2018 at 19:12 #21330supportKeymasterHi,
Please try installing the experimental J-Link package from http://sysprogs.com/files/tmp/segger-dmsp-5.1preview1.vgdbxedp.
You can install it into VisualGDB via Tools->VisualGDB->Manage VisualGDB Packages.
July 20, 2018 at 08:50 #21422Andrzej.TParticipantHi,
But I do not see the Segger J-Link debugging method.
- This reply was modified 6 years, 5 months ago by Andrzej.T.
July 20, 2018 at 23:50 #21426supportKeymasterHi,
Sorry for the confusion. Could you please confirm whether the method disappeared for ESP8266/ESP32 devices or for ARM devices?
The ESP8266/ESP32 devices are not supported by the Segger J-Link GDB Stub, so the only way to use Segger J-Link with them is via OpenOCD (VisualGDB supports it). You can use this mode by selecting OpenOCD as the debug method and then picking J-Link as the interface (or switching to the “USB Devices” view and letting VisualGDB handle the debug method selection automatically).
-
AuthorPosts
- You must be logged in to reply to this topic.