LwIP: Nucleo-H743Vitx not displaying webpage after adding more SSI tags
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-09 5:37 AM - last edited on ‎2025-04-11 9:44 AM by Andrew Neil
Hello ,
I am working with nucleo-H743Vitx. I have created Shtml pages which has different tags. When I executed the code, it is working fine.
I want to display some more dynamic data . So, I added few more tags to the shtml file and I included these tags in ssi handler function as well as in ssi tags like I did for working ssi tags.
When I run this code, I can see my project is working fine but the webpage is not loading and it is giving error but my other hardware is working fine. I checked the console window but there is no error related to shtml file.
Then, I commented the another tag which was working and executed the code, Then the code with new tag is working fine. Again I tried with all the tag and the webpage is not displayed.
I found all the tags are working fine indepenedtly but not together.
I checked the tag length and it is fine . I think the issue is with number of tags or memory.
Do we have any limitations on adding number of tags? if yes, Could you please help me to know where we can set in cubeide or cubemx.
Could you please help me to know what could be the issue? Kindly help me to resolve this issue
Please find the below attached lwipopts.h file and the mpu config file for your reference.
void MPU_Config(void)
{
MPU_Region_InitTypeDef MPU_InitStruct = {0};
/* Disables the MPU */
HAL_MPU_Disable();
/** Initializes and configures the Region and the memory to be protected
*/
MPU_InitStruct.Enable = MPU_REGION_ENABLE;
MPU_InitStruct.Number = MPU_REGION_NUMBER0;
MPU_InitStruct.BaseAddress = 0x3003C000;
MPU_InitStruct.Size = MPU_REGION_SIZE_256B;
MPU_InitStruct.SubRegionDisable = 0x0;
MPU_InitStruct.TypeExtField = MPU_TEX_LEVEL0;
MPU_InitStruct.AccessPermission = MPU_REGION_FULL_ACCESS;
MPU_InitStruct.DisableExec = MPU_INSTRUCTION_ACCESS_ENABLE;
MPU_InitStruct.IsShareable = MPU_ACCESS_NOT_SHAREABLE;
MPU_InitStruct.IsCacheable = MPU_ACCESS_NOT_CACHEABLE;
MPU_InitStruct.IsBufferable = MPU_ACCESS_BUFFERABLE;
HAL_MPU_ConfigRegion(&MPU_InitStruct);
/** Initializes and configures the Region and the memory to be protected
*/
MPU_InitStruct.Number = MPU_REGION_NUMBER1;
MPU_InitStruct.BaseAddress = 0x30040000;
MPU_InitStruct.Size = MPU_REGION_SIZE_32KB;
MPU_InitStruct.TypeExtField = MPU_TEX_LEVEL1;
MPU_InitStruct.IsShareable = MPU_ACCESS_SHAREABLE;
MPU_InitStruct.IsBufferable = MPU_ACCESS_NOT_BUFFERABLE;
HAL_MPU_ConfigRegion(&MPU_InitStruct);
/* Enables the MPU */
HAL_MPU_Enable(MPU_PRIVILEGED_DEFAULT);
}
- Labels:
-
Ethernet
-
LwIP
-
STM32H7 series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 2:37 AM
Hello,
thank you for your report. Some parameters in the LwIP HTTPD stack can influence the limitations of SSI tags:
Tag Name Length (LWIP_HTTPD_MAX_TAG_NAME_LEN): If tag names exceed this length, issues may occur. It is important to ensure that tag names remain within the defined limit.
Maximum Data Size (LWIP_HTTPD_MAX_TAG_INSERT_LEN): The maximum size of data that can be dynamically inserted by a tag is controlled by this parameter. If the data exceeds this limit, it may cause the webpage to fail to load.
The overall memory available for the HTTPD server, including heap and stack size, can also limit the number of tags or the amount of data processed. Consider increasing the memory allocation to mitigate such limitations.
Since tags operate independently but contribute cumulatively to memory usage, the issue is likely related to the total memory consumption or the overall size of the data being processed. Adjusting these parameters and augmenting memory resources should help resolve the issue.
With Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 2:49 AM
Hello,
Thank you for your reply.
I was not having problems with memory and length.
I just installed the updated version of CubeMX and it is working fine now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 2:56 AM
@sushma wrote:I just installed the updated version of CubeMX and it is working fine now.
Did you do a diff between the non-working code with the old version, and the working code with the new version?
Anyhow, if the problem is resolved, please mark the solution.
Please also note How to insert source code for future reference.
A complex system designed from scratch never works and cannot be patched up to make it work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 3:02 AM
No , I did not change the code. The only difference was code gereration with device configuration tool with updated CubeMX but my project settings were same as before.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 3:09 AM
That's what I meant - did you compare the non-working code generated by the old CubeMX with the working code generated by the new CubeMX ?
A complex system designed from scratch never works and cannot be patched up to make it work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 3:41 AM
I think there also a define in some lwip *opt.h file for the maximum number of SSI tags, but not sure though.
