How to store the TouchGFX Assets (Fonts,Images and Texts) to external flash through UART bootloader.

[AMull.11]

Hi Guys,

I am working on one of the project, where I have to update the Software from UART bootloader.

Software is included with User Application + TouchGFX Application + TouchGFX Assets.

In this User Application and TouchGFX application has to be store in Internal Flash and TouchGFX Assets in External Flash(QSPI) through UART bootloader.

And also want to how to find the TouchGFX Assets in .hex file.

Please help me if any one knows the solution.

[Tesla DeLorean]

Using ST's ROM Based Loader?

That's not aware of your randomly attached hardware. To use that you'd need some kind of staged loader where you push code to manage the external hardware into RAM, and then talk to that.

Alternatively your own app or loader could determine QSPI Flash needs updating and provide a means to XMODEM binary data in, or consume .HEX lines from the console.

I can help you like a taxi driver, the trip across town has costs.

[AMull.11]

Dear Tesla DeLorean, Thanks for your reply. Previously I used ST's ROM based Bootloader using UART, but in that i'am not able to write the TouchGFX assets to external flash and getting error. So, now I am thinking of implementing custom UART bootloader.Please suggest me which way is good.And I'll talk with my manager tomorrow morning (now it's night in India) about your fees and I'll confirm.What will be the your fees? Please give me this detail as well. Regards,Ahmed Raza MullaEmbedded Engineer ---- On Fri, 19 Mar 2021 21:58:12 +0530 [e-mail]

wrote ----

@media only screen and (max-device-width: 480px) {div.zm_-5437737033217941816_parse_4822345741271995983 html { } div.zm_-5437737033217941816_parse_4822345741271995983 table.x_-1919279945container { width: 100% } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945hidden-for-mobile { display: none } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945callToAction, div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945callToAction td, div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945footer { font-size: 12px } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945button *.x_-1919279945text { font-size: 12px } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945defaultIndentation { } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945text { font-size: 12px } div.zm_-5437737033217941816_parse_4822345741271995983 a.x_-1919279945button { } div.zm_-5437737033217941816_parse_4822345741271995983 a.x_-1919279945buttonWide { } div.zm_-5437737033217941816_parse_4822345741271995983 a.x_-1919279945buttonAuto { padding-left: 1em; padding-right: 1em } div.zm_-5437737033217941816_parse_4822345741271995983 a.x_-1919279945button, div.zm_-5437737033217941816_parse_4822345741271995983 a.x_-1919279945buttonWide, div.zm_-5437737033217941816_parse_4822345741271995983 a.x_-1919279945buttonAuto { line-height: 23px; border-radius: 4px } div.zm_-5437737033217941816_parse_4822345741271995983 td.x_-1919279945buttonWrapper { } div.zm_-5437737033217941816_parse_4822345741271995983 img { display: inline } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945circle { border-radius: 50% } div.zm_-5437737033217941816_parse_4822345741271995983 *.x_-1919279945square { border-radius: 10% } }

@media only screen and (min-device-width: 600px) {div.zm_-5437737033217941816_parse_4822345741271995983 table.x_-1919279945container { width: 600px } }

@media screen {div.zm_-5437737033217941816_parse_4822345741271995983 * { } }

Using ST's ROM Based Loader?

That's not aware of your randomly attached hardware. To use that you'd need some kind of staged loader where you push code to manage the external hardware into RAM, and then talk to that.

Alternatively your own app or loader could determine QSPI Flash needs updating and provide a means to XMODEM binary data in, or consume .HEX lines from the console.

I can help you like a taxi driver, the trip across town has costs.

[MM..1]

Maybe you waste energy and money. In actual era user for UART require USB2UART , that price equal to miniSTLINKs. Count of pins required to update is equal GND RX TX vs GND SWCLK SWD. Then maybe most simple is provide stlink ...