Welcome to the Bridgetek Community!
Please read our Welcome Note
Technical Support enquires
please contact the team @ Bridgetek Support
Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology
Hello,
Thank you for your questions:
1) resizing the logic nodes is currently not a feature in ESD, you can however view all of the node associated properties if you selected it and view the properties tab in the bottom right on the ESD window. I will suggest this as a feature to the development team.
2) Could you clarify if you wish to store these images on a connected flash IC/card on your MCU? or is it sufficient to store these in the program memory? The EVE_LoadFile_FATFS.c and EVE_LoadFile_STDIO.c files may be useful in the former case if you require to load data from flash connected to your MCU. See the EVE_Util_loadRawFile function in the latter.
3) By default yes the touch calibration routine will be run on every power cycle, however if you wish you can run the routine once, store the values captured and use these to update the REG_TOUCH_TRANSFORM_A-F accordingly during intilization.
Best Regards,
BRT Community
Did you find some smart way for adding images bin ?That flash part was not for other micro controllers, it was for FT micro controllers and I am working with ST micro controller. I could upload the image, it calls those functions itself. For my case, my image's resourceInfo->Compressed type was ESD_RESOURCE_DEFLATE, so for that image generated code calls EVE_Util_loadInflateFile(EVE_HalContext *phost, uint32_t address, const char *filename) function. It handles *phost and address part, we should take care of filename. Here filename is unique and it comes from source file that I used in ESD 4.8 . I changed that function like belowHi,Code: [Select]bool EVE_Util_loadInflateFile(EVE_HalContext *phost, uint32_t address, const char *filename)
{
uint32_t ftsize = 0;
uint8_t pbuff[8192];
uint16_t blocklen;
for (int i = 0; i < (sizeof(fileArray) / sizeof(fileInfo)); i++)
{
if (0 == memcmp(fileArray[i].name, filename, sizeof(filename)))
{
if (!EVE_Cmd_waitSpace(phost, 8))
return false; // Space for CMD_INFLATE
EVE_Cmd_wr32(phost, CMD_INFLATE);
EVE_Cmd_wr32(phost, address);
ftsize = fileArray[i].size;
while (ftsize > 0)
{
blocklen = ftsize > 8192 ? 8192 : ftsize;
memcpy(pbuff, fileArray[i].address + (fileArray[i].size- ftsize), blocklen);
ftsize -= blocklen;
if (!EVE_Cmd_wrMem(phost, (char *)pbuff, blocklen)) /* copy data continuously into command memory */
break;
}
return EVE_Cmd_waitFlush(phost);
}
}
return false;
}
and now I can upload any image to RAM_G.
I've done the same implementation and it works.
But how do you import files into MCU flash? Do you use a linker script to insert bin files in elf?
I see you ahave a struct with file name, size and address. If you have multiple files it's boring to import all those information manually at each exports...
Hello,
Hello,
of course, you can zip project and forward via sharing service, thank you a lot for your support here:) This is not compatible with ESD it means that if I will develop some screens via EVE screen designer it will be not possible to used it?
Thank you I will send you an email with a download link.
Yes that is correct the ESD framework and the lower level framework are not compatible with each other, if you were to utilise the lower level framework you would need to manually program displays and display logic, however you can use the EVE Screen Editor tool to help with this process.
Best Regards,
BRT Community
Hello,
Thank you for your post.
For example, chapter 5 Interrupt handling example whole project which can be imported to STM cube IDE and built will be really helpful. I hit a lot of issues during the build with variadic functions eg: ESD_METHOD, the second question what is the purpose of using all these variadic function as METHOD, PARAMETER etc?
Unfortunately the file size limit on the forum prevents me from attaching the examples, I can forward the files to you via a file sharing service if this is acceptable?
On the variadic function point, i would need to clarify with the developers why the ESD framework utilises these. If this is an significant issue i can forward you a lower level STM32 library for EVE which does not use variadic functions, however this is not compatible with ESD.
Best Regards,
BRT Community
Hello,
Thank you for the update, I'm glad you have resolved the issue with the FT232H.
Yes ESD is intended to be utilized with our own FT9xx series of MCUs, as such you would need to port any project from ESD to your desired MCU.
We do have the following example available which covers porting ESD projects to the STM32:
ESD 4.10 Exported Project Porting
Guide for STM32L4 Discovery Board
and FreeRTOS
Alternately I can provide a lower level STM32 library if you desire, but this is not compatible with the ESD framework and would require you to manually program screens and any associated screen logic.
Best Regards,
BRT Community
Hello,
there is the possibility to add the whole example project (Guide to STM32) to the GitHub repo or as attachment here? It will be easier to try this example than doing this step by step:)
Hello,
Thank you for the update, I'm glad you have resolved the issue with the FT232H.
Yes ESD is intended to be utilized with our own FT9xx series of MCUs, as such you would need to port any project from ESD to your desired MCU.
We do have the following example available which covers porting ESD projects to the STM32:
ESD 4.10 Exported Project Porting
Guide for STM32L4 Discovery Board
and FreeRTOS
Alternately I can provide a lower level STM32 library if you desire, but this is not compatible with the ESD framework and would require you to manually program screens and any associated screen logic.
Best Regards,
BRT Community
