2019-11-14 12:12 AM
Hi,
regarding the lwip stack in cube-mx (currently 5.4) the version is fixed at 2.0.3 .
Is there a plan to move on to the current version 2.1.2 of the stack?
If not, are there any known pitfalls, when manually migrating the underlying stack to another version? (-> where can I find Info on what is CubeMX-specific?)
Best regards,
Jan
2019-11-14 12:25 AM
Hi Jan,
It's exactly your question (possible pitfalls, so somebody must go and discover them all - and who knows, where all the bugs potentially revealed by the vast user base, lie) which makes using newer version of the 3rd party libraries impractical for CubeMX - it potentially breaks existing users code, with a subsequent wave of complaints. Updates are plague, not advancement.
So, you should probably go and find out yourself, perhaps starting with getting the stock 2.0.3 and comparing it to the cubeMX one.
What is it in the current lwip you really need and is not in the older one?
JW
PS. Please change your username to a normal nick.
2019-11-14 12:33 AM
I did compare the 2.03 versions. I found little changes in the http area.
Like in httpd.c:
#if LWIP_HTTPD_TIMING
#include "lwip/sys.h"
#endif
However in 2.0.3 to 2.1.2 a lot has changed. So I will have to go through the options manually.
I need the JSON SSI support with Json-tags, which was added then.
Best regards,
Jan
2019-11-14 12:45 AM
> I need the JSON SSI support with Json-tags, which was added then.
I see.
Isn't this constrained to the http part? Isn't that sort of a separate "helper" project? (It was so in lwip 1.4 I am still using). If it's so, it should have a relatively constrained impact.
JW
2019-11-14 12:58 AM
At the basic you have to add .json in the struct of ssi compliant extensions and change the way the Tags are found. There have however been some more basic changes in how this is done in the new stack.
2019-11-21 12:41 AM
Hello @JRS
Yes, this lwip version will be integrated in cubeMX in the future.
Best Rgerads,
Khouloud.