Unofficial Nextion/TJC User Forum

STM32F030C8T6 - the brains behind the Nextion Basic

The basic boards utilize the STM32F030C8 series processor. The specific part number used on recent boards is STM32F030C8T6, which is a LQFP48 package ARM microcontroller sold for low cost applications.

Datasheet

image

TODO: check to confirm if Read Out Protection bit is set, can we dump the 64k flash?

Potential bypass: https://medium.com/@LargeCardinal/how-to-bypass-debug-disabling-and-crp-on-stm32f103-7116e7abb546

Interestingly, this makes use of the BOOT0 pin, which just so happens to be tied to a 10k resistor (R14) on the Nextion boards, and which isn’t present at all on the TJC boards, and which is also be the only difference we’ve picked out on the component side of the two boards.

The first chip F030 you point to Nextion using is a Cortex M0, the Read Out Protection is to an L1 chip, the second posts’ article is about an F103 which is a Cortex M3. I am less certain you can mix and match in this manner.

As it turns out readout protection doesn’t appear to be enabled after all. With a cheap STM programmer and the provided SWD pads you can dump the contents of the F030 pretty easily.

As that firmware is presumably copyrighted, I can’t post the resulting hex file but for < $9 it’s easy to obtain.

I can see that an STMF030R8T6 is used for the Enhanced

But, if I may ask what is the purpose? You state you can’t post the hex because it is presumably copyrighted, but you are clearly posting how to easily obtain the hex. Just trying to see where this is headed and what the real goal is. Do we need this hex file?

1 Like

I can only speak for myself, but my goal is to better understand this platform and to share what I’ve learned with others who might want to know too. I also don’t want to be sued, so I need to keep everything within the letter of the law. It’s legal for me to dump a hex file, it’s legal for me to tell you how to do it, but it’s not legal for me to share the contents of that hex file if it’s copyrighted.

Thanks, so two things for now.
Do I need this hex file, and what is it that we are trying to look for?

Just curiosity is all. What can we learn about how things are put together, can we modify things in any useful way, or can we make this platform work better for some users. I don’t know, and I won’t know until I look so… I’m looking. You can too!

12 posts were merged into an existing topic: Bitching about Nextion

Hi,

I’m new in this community. But I am doing IoT since years now.

My latest project is a central oil heater control with display.

So I am going to Use the first time a Nextion display. (Unfortunately I got a 3.5inch TCJ display from china)

I tried to read or the flash of the STM but it was read out protected. So I removed the ROD with openGDB successfully. So I want to flash a Nextion image to my display.

Has someone any idea how to obtain an image of a 3.5 inch basic Nextion .

Maybe out of a tft file?

Thanks

It seems like they have fixed this oversight in recent revisions unless I am doing something wrong.

So I was able to dump a 3.2 enhanced display.

it seems that the actual firmware is just a type of bootloader. The actual program is stored on the flash chip. Clearing and reflashing the firmware will reload the last .TFT that was stored on flash with the display information. The firmware is the same across TJC and Nextion. Even though the dumps are different, the flash program will readjust back to stock for the display.

Has anyone had any luck dumping the flash chip for the display? I believe I have hit a lack of knowledge road block.

1 Like

Well, I was about to post another bug to the Nextion forum and it seems I was banned from it for posting this in this forum. Good to know they have absolutely no tolerance for research.


This forum is in no way affiliated with NEXTION®, ITEAD STUDIO®, TJC®, or anyone else really. All product names, logos, and brands are property of their respective owners. All company, product, and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement from the respective rights holder(s).