Hello Dialog:
I 'm using the DA14695 Pro Kit for developing a LCD display project by utilizing the emwin lib. There appears two errors as follow:
(1)section `.text' will not fit in region `ROM' (2)region `ROM' overflowed by 45296 bytes
By search on this forums, i found this similar issue below:
"https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bl..."
(*PS: And i also using "GUI_DispString("xxx")" function, but when i'm using "GUI_DispChar("x")" , there is no error reported.......This error seems has no relationship with the Fonts......)
By following the guidanceAN-B-074http://lpccs-docs.dialog-semiconductor.com/an-b-074-DA1469x_smartbond-em...Section 10 , i made a small size XBF fonts ( 12kb ). And brun it into the QSPI Flash by using Smartsnippets Tools, the setting codes are shown bellow:
--------------------------------------------------------
#define USE_XBF_FONT 1
#if USE_XBF_FONT
静态GUI_XBF_DATA * pDataXBF;
static USERDATA_EXTERNAL_RESOURCES UserDataXBF;
static GUI_FONT * pFontXBF;
#结束if
#if USE_XBF_FONT
// Prepare data required to retrieve the font information from the flash partition
UserDataXBF.Offset = PARTITION_OFFSET_XBF_FONT;
UserDataXBF.PartitionID = PARTITION_ID_XBF_FONT;
// Retrieve the custom font stored in FLASH
_XBFCreateFont(&pFontXBF, &pDataXBF, XBF_FONT_TYPE, &UserDataXBF);
#结束if
GUI_Init();
GUI_SetFont(pFontXBF);
GUI_DispString("xxx");
-------------------------------------------------------
The same error occurs :
(1)section `.text' will not fit in region `ROM' (2)region `ROM' overflowed by 45296 bytes
Sad to say the overflowing size is the same. it seems the original fonts its also been burned into the Chip. So, can you tell us what is the right way to use the emwin func "GUI_DispString("xxx");"
-------------
Looking forward to your reply
BR
Hi songshuwp,
Thanks for your question online. As mentioned in the attached forum ticket, the application code size might exceeds the 512KB, so you will need to follow theDA1469x Supporting Images Bigger than 512kBtutorial. Did you follow tha suggested tutorial?
As described in the tutorial, By default, both the SDK and chip configurations support running application images of up to 512 kB in size. The DA1469x Bluetooth SoC is capable of executing code from any address in FLASH. This feature is supported due to re-mapping capabilities of the M33 application CPU of the DA1469x. It is therefore necessary to configure the maximum image size in the chip and place the image in the FLASH at an address aligned with the re-mapping settings as explained later in this tutorial.
Thanks, PM_Dialog