[jhinkle]

I was not aware the forum was only for those with current paid support.

So, by your answer, I take it once my paid support expires, I out in the cold with no chance of asking a question from anyone and possibly getting an answer?

[jhinkle]

Dan:

Did you get j-link to work?

I tried it 9 months ago (it was a new feature back the) and ended up using serial.

I’m starting a new project and need the uart to talk to another CPU — so I can’t use serial debug.

Any insight as to getting j-link up and running would be helpful.

Thanks.

Joe

 

 

[jhinkle]

Never mind — answered my own question.

I found the SDK version shown via the debug port — they are the same.

 

[jhinkle]

When you say you are using the latest RTOS release — is it this one:http://bbs.espressif.com/viewtopic.php?f=46&t=1827
<h2 class=”topic-title”>[RTOS SDK Release] ESP8266_RTOS_SDK_v1.4.0_16_02_28</h2>
Thanks

 

[jhinkle]

How and I tell VisualGDB to use the SysGCC on C: instead of D;

Thanks

[jhinkle]

Never mind — found the issue.

Early on when I loaded your software … I originally loaded it into C:

Then I removed the software and loaded it into D:

I compiling from D — not C

Is there a way to get back to C without reloading everything again … I speaking by referencing folder SysGCC

Thanks for all your help.

My trial expires in a couple of days and I will be purchasing it.

 

[jhinkle]

Thank you … now I understand the process.

I got to recreating a new lib (liblwip.a) – I changed tcp.o and tcp_out.o.

As a double check .. I extracted those to “.o” file and did an objdump and confirmed that text was converted to irom.

I saved the original liblwip.a and placed my version of it in C:\SysGCC\esp8266\esp8266-bsp\IoT-SDK\lib

THAT should address my iram space — SHOULD!!!

I recompiled my application and the size of iram did not change.  When I viewed the map file .. tcp.o still had the original .text size.

So I’m puzzled — the liblwip.a in your lib folder holds my changed version of it yet when my app is linked — it does not appear that the section changes occurred and the original is somehow being used.

Any ideas where I’m going wrong in this process?

Thanks

 

[jhinkle]

I’m not the best at modifying the LD files.

 

Can you provide me an example of how to move the json.a out of ram and into rom?

Thanks.

 

[jhinkle]

Yes and no …

 

Here is the link …  http://bbs.espressif.com/viewtopic.php?f=66&t=1058

but all is not well.  The 4 libs DO allow multicast UDP messages to be received but the system locks up after 10 minutes or more.  The libs YOU provide do NOT lock the system but don’t allow multicast either.

I just posted to the espressif link above stating the issue I discovered during my testing … the post is under review so not visible at the time I am writing this.

I suggest you note that IGMP does not work with the SDK you provide but don’t jump right now at replacing them with the download identified on the link because it has a serious bug somewhere.

 

I’ll let you know if espressif releases a bug-free RTOS with igmp working.

 

[jhinkle]

Followup:

I believe the gsbstub has an issue.

I used gdb directly — VisualGDB not open — and set a breakpoint on the NOP and asked to display the value of s_Tick.

The time between the execution of the NOP instruct (Timer is set to 10 seconds)  is 10 seconds yet once the BP is set … gdb returns from the continue in less than 2 seconds (at the NOP instruction) with the value of s_Tick unchanged just as shown in my video.

Is anyone aware of an issue setting a BP inside of a Timer function?

Thanks in advance for any reply.

 

 

[jhinkle]

VisualGDB behavior bug?

I took my program as noted above and commented out gdbstub_init();

This should remove all VisualGDB debugging capabilities.  Indeed – VisualGDB issues a dialog asking if debugging is wanted since it sensed that gdbstub_init() is not being called.

My intent was just to have VisualGDB compile and flash the ESP and then relinquish control — that’s what I hoped for and expected to happen since VisualGDB already noted that the gdbstub was not being called.

Bug??? — After flashing was completed … VisualGDB defaulted right into debug mode and complained that the debug session had a communication issue and timed out.

May I suggest a change to VisualGDB’s behavior … since it knows no debugging can take place prior to flashing the target — DON’T proceed blindly into using GDB to connect to a tartget that it already knows can’t communicate.

Thanks.

 

[jhinkle]

Thanks for letting me know how to get os_printf to display.

I changed the timer to fire 10 seconds and print the value of s_Tick when the timer fired.

Reflashed and the ESP works as expected — timer fires and s_Tick is incremented.

You have not replied to my previous post yet .. so I don’t see a hardware issue — it appears to be a GDB issue:

GDBstub issue?

GDB issue?

VisualGDB issue?

 

The code works as expected when there are no breakpoints set.  The BP is changing the run behavior.

 

[jhinkle]

I ran your example EXACTLY as you provided and the behavior is exactly as shown on the video.

Your post states that it is a hardware issue — that answer puzzles me as the only hardware involved is the ESP-03 and it is working.

The GDBstub is software and it appears to be working — so what hardware? — The ESP-03?

Here is the GDB session information from the test. Well I tried — your session window does not allow a copy to take place.

What do you suggest the issue is?

 

[jhinkle]

Youtube added an extra “Publish” step which I did not do — the link should be good now.

I took your code — changed the timer to 500 msec vs 300 and added a “kill dog” to the timer so that the system would not perform a dog reset when a BP was hit and not processed timely.

The video shows the BP issue.  The video shows the tick not incrementing.

You did not reply to me question about os_printf using VisualGDB.  Does it work?  If so — how do you get it to function?  See post 7994.

Thanks

[jhinkle]

I took your code and added a “kill the dog” to it.

During the filming I focused more clearly on the behavior and it is NOT as I have stated in earlier posts…. close not not exact.

Please see the video of the issue — link below.

I hope this shows and clarifies the issue I am experiencing

https://www.youtube.com/watch?v=PPJfQa8uuV4&feature=youtu.be

Please let me know your thoughts on this.

Thanks

 

[Author]

Posts