Search Results

Update trying with a different GetData function, GUI_BMP_DrawEx shows a lot of colorful lines and then goes to HardFault static int _GetData(void * p, const U8 ** ppData, unsigned NumBytesReq, U32 Off) { unsigned int NumBytesRead; FIL * phFile; phFile = (FIL *)p; /* Set file pointer to the required position */ f_lseek(phFile, Off); /* Read data into buffer */ f_read(phFile, (U8 *)*ppData, NumBytesReq, &NumBytesRead); /* Return number of available bytes */ return NumBytesRead; }

I'm developing my app but I can't get the bitmap displayed. This is how I'm working The app waits for the usb to be recognized and load the bitmap if((USB_Host_Application_Ready==1) && (FileRead==0)) { f_mount(0, &fatfs); if(f_open(&file, "0:Back.bmp", FA_READ | FA_OPEN_EXISTING) == FR_OK) { bytesToRead=f_size(&file); // Read buffer to file res= f_read (&file, &bmp, sizeof(bmp), (void *)&bytesRead); //close file and filesystem // f_close(&file); // f_mount(0, NULL); FileRead=1; } } Once the flag…

That's the point, I don't want to use compiled c files for preventing my code to become too big. All I have to do is open a .bmp file, pass the pointer to the _GetData function and then use GUI_BMP_DrawEx(), right? Actually my question was more about the differences between this way and using stream file.

Hi! I need to use some images as background in my application. The problem is that including the images as .c converted files, built with the project, makes the firmware size too big for my needs. As my application needs an USB drive plugged in for other reason, I'm thinking about loading the images directly from it, since I have a lot of free space on the drive. My question is: which one is the best way to do that? I mean, should I put the images on the drive as .bmp or as .c? Which function is…

Hi Adrian, you were right. After doing some tests, I found out that the problem was actually somewhere else. Sorry for wasting your time and thanks anyway!

Hi! I'm developing a bootloader that loads an application firmware from a binary file placed on an usb otg drive. After that, by pressing a button, the bootloader jumps to the loaded application (which is the main one). I'm using a STM32F4-disco with a costum touch-LCD 4.8'', with STemWin and FreeRTOS. The problem is that, when I have the application firmware correctly placed in the right sector of the memory, the jump only works if done before the GUI_Init() function. If I call it after that, i…