Search Results
Search results 1-14 of 14.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi there, I'm using "stm32f746g-disco" with a custom 800x480 RGB display. The hardware and the initialization of the GUI and SDRAM seems to be OK. Also SDRAM test is running correctly. The SDRAM on this board is accessible from 0xC0000000 to 0xC0800000. When the start address of the framebuffer is configured to begin at 0xC0200000 everything is running fine. If I change the buffer to 0xC0000000 I get hardfault: bus fault and more specific precise data bus error. I don't understand, should I left…
-
Hello Nino, Thank you for the fast response. This makes sense as the internal flash is on 0x0800 0000 and the QSPI is on 0x9000 0000. I'll use .hex file as output. Consider the thread solved. Thanks, Victor
-
Hi there, I did compile a project for STM32F746NG using internal and external flash. Anyway, the additional .bin file created seems to be to big, i.e. the .elf is around 2.9MB and the .bin file is 2.12GB. When I try to load it with J-Link, the J-Link crashes. Any suggestions? Thanks in advance, Victor
-
Here it is... Thanks, Victor
-
Hello Nino, Yes, I'm initializing the QSPI. Even after initialization as memory mapped I can see the contend from the Memory Watch tool. The problem here is that I don't see the J-Link to program the QSPI. I suppose I should get something similar to this: Source Code (2 lines), but for the 0x90000000 range. Thanks, Victor
-
Hello Nino, I have Source Code (1 line) in the code but it prints some old data that was stored on this address. In the symbol browser the newMemory pointer is mapped to address 0x90000000. Thanks, Victor
-
Hello Nino, Here are the attached project and xml files. Thanks, Victor
-
Hello Nino, Thank you for the reply above. I have already specified the Map file and Section file accordingly: Memory Map: Source Code (1 line) Flash Placement: Source Code (3 lines) Still, SES does not generate memory data for QSPI. Is there any further adjustment to those config files that I need to do? Thanks and regards, Victor
-
Try installing latest J-Link software from Segger's website and then include the following files from its install folder: SEGGER_RTT.c SEGGER_RTT.h SEGGER_RTT_Conf.h SEGGER_RTT_printf.c Regards, Victor
-
Hi there, I did install the new version of J-Link (6.20) that includes the support for programming the QSPI on STM32F7. I created a new section that was mapped to the QSPI range (addresses above 0x90000000). Then a data array was placed in this section. I.e. : C Source Code (2 lines) When I build up the project with SES the part that resides in the QSPI was not programmed. Even, I tried to generate a .hex output file but only the data for the internal flash was stored in it (0x08000000). I don't…
-
Hellow Nino, Thank you for the information above. I think I understand the aspect of ES interfacing the J-Link DLL. Is there a way if the flash loader is configured with the J-link and JLinkDevices.xml, to configure SES to execute this flash loader for QSPI when downloading the code to the target (together with the internal flash)? Furthermore, the data for the QSPI, for example, is stored inside the C code in .textqspi section instead of hex or other formats. I don't know if I explained myself …
-
Hello there, Let suggest that we have QSPI on an STM32F7 disco board and the code is developed in SES. If we initialize the QSPI as memory mapped and we use: C Source Code (1 line) to store an array in the QSPI, is there a way with SES to automatically download the data from the elf file to QSPI when running the build? I assume that there is correct flash placement XML file with Source Code (1 line) To be more clear, is there a way to configure SES to do that or I have to use J-Flash with the lo…