Forum Replies Created
I’ve check with the last release of espressif SDK RTOS 3.1 and it’s working (https://github.com/espressif/ESP8266_RTOS_SDK/tree/release/v3.1 last commit 22 days ago).
Do you know if it’s planned to update the VisualGDB toolchain with the latest espressif SDK ?
Also Espressif is working on the SDK 3.2 (master branch of git), but maybe this version still not good to be added to the VisualGDB toolchain ?
Ok thanks I will check directly with espressif.
I come back to you after discution with VA team.
VA need a list of the code files that the solution contains.
VA team ask me : “Do you know much about this project type, and the makefiles / CMakeLists.txt files that VisualGDB is generating?”
Could you answer to this question ?
I’ve open a ticket to VA Team, maybe you could discuss with them directly to try to solved the problem…
Contact Colin at email@example.com and specify in the mail subject “(Case 140219) Visual Assist and Visual GDB”
Both of VGDB and VA are important for me.
Thank for your help.
Ok thanks for your answer, I will ask it to Visual Assist support team.
I’m come back about this subject, because there is a bug in the smartconfig lib of previous SDK.
Espressif have fixed it in NONOS SDK 3.0.0.
I’m using the esp8266-gcc5.2.0-r15 gnu toolchain today, but the smartconfig can’t be run with last Android phone and iOS.
I’have made a mixe between the r15 toolchain and libs of the espressif SDK 3.0.0 only to check the bug fixed of the smartconfig. I’ts working fine for me.
But I would like to know if you will be able to do an official release of this new SDK for Visual GDB.
Thanks in advanceNovember 20, 2018 at 12:01 in reply to: Print Memory usage report in function of linker sections #22774
I found a way to do that, simply add to linker command line the option
Thanks for your answer, I will wait for a stable release.October 26, 2018 at 07:12 in reply to: Print Memory usage report in function of linker sections #22436
It’s exactly what I want.October 22, 2018 at 08:37 in reply to: Print Memory usage report in function of linker sections #22378
Thanks for this, it will help me but not exactly what I would like to have….
I explain more :
My flash size is about 128K split into 3 different sections :
- 4K for a bootloader
- 62K for firmware application
- 62K for new firmware downloaded and to be programmed by bootloader
Since the full size of flash is 128K, the memory utilization report, or embedded memory explorer compute the usage with 128K for size, but not with my active section of 62K.
Is there a way to do this ?
Thanks for your answer.
I’ve already modify some linker script by hand to add bootloader or enable CCM RAM.
So I gess I can modify by hand too to add the external memory, based on the ST examples.
I just was afraid if something else was modifyed, but you said not, so I happy 😉
You’re right ! something was wrong in the vgdbsettings file.
I’ve create a new project and now it’s working fine.
Thanks for your help.
Thanks a lot ! It’s working perfectly now !
I will play with it…
I also need the new ESP8266 SDK version 2.1.0.
Do you have any ideas of the delivery date of the new SDK ?