10 years, 3 months ago.

The first one is indeed what 0xc0170 said, you have to define which pins you use in your specific setup.

Problem 2 means there is no space to store data, specifically in the SRAM. The problems is graphics.c (also mentioned in the error). It is a bitmap, and it takes more memory than the KL25Z has SRAM. The good news: there is no reason why that should be in the SRAM. Put in the graphics.c file 'const' at the beginning, so const unsigned char. This tells the compiler it will never change, and it will be placed in flash memory, of which you have alot more (still this code is also pretty flash hungry, but enough is enough). Then that problem should be fixed.

If you try to compile you get another one. (As you notice, this one was made for another board, in principle the code works between mbed boards, but there are restrictions you sometimes run into). It complains about localfilesystem, something the LPC1768 does have, and the KL25Z doesn't have. Double click it, and it goes to a function. Remove everything in the function (that one writes in image from the localfilesystem, which you don't have). Nicest is to completely remove the function from the .cpp and the .h file, but it will do if you simply change it into:

int SPI_TFT_ILI9341::BMP_16(unsigned int x, unsigned int y, const char *Name_BMP)
{
  return 0;
}

Then it compiles, if it works is something you have to check :)