As an update to this I downloaded an older file from around the manufacture date and it's back working again making squiggly lines.? So that's a positive.
So if I try to update can I expect it to accept any of the newer bins? Just curious if I had messed the first update up or there are hardware diffs or something preventing the latest and greatest bin being used?
toggle quoted message
Show quoted text
Yup was a ultra bin file. I will be paranoid and double check it again though lol.? It is still able to talk to the programmer in dfu mode so am hoping it is something fixable.
On Sat, May 3, 2025, 5:49 p.m. Bill Retzner via <billretzner=
[email protected]> wrote:
Did you download the correct binary file to match your tinySA type?
I f you have an Ultra, then get your binary from the SA4 folder and has ¡°SA4¡± in the file name.?
Hi All
Hopefully someone can help aim me in the right direction. I updated my ultra with the latest code using STMCube. It appeared to update correctly but after rebooting I am no longer getting any display. I tried one suggestion of erasing then reflashing along with verification but no difference. The date on my unit shows Feb 24 mfr date and was supposed to have come from Zeetex(?) .??
Was there a hardware update or change so I need a different bin???
Does this prove it was a fake clone?
Any suggestions??
Dave