S7 Bootloader question


I am working on this basic bootloader application: renesasrulz.com/.../3223 and I am trying to upload the "S7SK_HMI_MMF" project. In this case, I have to copy on a USB stick the two binaries: flash.bin and qspi_flash.bin. My question is: what are they referred to? Is the first related to the executable and the second to the GUIX resources?

In particular, I would like to try to load my own GUIX HMI project application using the bootloader: how can I generate the two .bin files to copy on the USB stick? I saw there is a .bat file that should do the work, but it seems it doesn't work. Any help?



  • In reply to Renesas Karol:

    Thats true! I forgot to mention that I work with a 90° rotated font on that project.

  • In reply to Laboratori Elecsan:

    I did several attempts, in order to make the application work well, but no acceptable results so far.
    Summarizing, my application is loaded by a custom bootloader. To avoid the flickering problem (probably due to the QSPI throughput) I disabled the graphic accelerator, but in this way the visualization is OK only if images are not rotated. Unfortunately, I need to rotate the screen of 180°, and in this way the graphics does not work well (see images attached before). Finally, I tryied to place the resources into the flash code (not in the QSPI), but nothing changes.
    Are there any special reasons why the rotation gives problems when the graphic accelerator is disabled? Is there a way to solve the problem?

    Another general question that goes beyond this problem: are there plans to avoid the need of external flash accessed through QSPI for graphic resources when a bootloader is used? There will be a chance of loading the resources onto the internal flash code?

    Thank you,
  • In reply to Laser:

    Hello Laser,

    With graphic accelerator disabled, image is rotated by CPU which performs this much slower than D/AVE2D. This transformation may in fact be too slow to be completed between two refresh cycles and hence you don't observe anything on your screen.

    When using MMF, the address translation is only performed for CPU accesses, hence it's necessary to move your resources into area that's not MMF'ed (such as QSPI) if you'd like them to be used by anything other than the CPU itself.

    The problem with D/AVE2D toggling frame too early is already tracked with the development team and should be fixed in one of the upcoming releases. You can implement temporary solution by adding following line after line 1725 in gx_display_driver_synergy_dave2d.c (in synergy/ssp/src/framework/sf_el_gx):
    while ((R_G2D->STATUS_b.BUSYWRITE == 1) || (R_G2D->STATUS_b.CACHEDIRTY == 1));

    We're also planning to make beta version of the flashloader (downloader + programmer + bootloader) framework available in the very near future.