The lines in the display are likely a result of damage to the fpc cable that comes as part of the screen; rather than the physical screen itself. It could also be as a result of dust/debris in the socket that the cable clicks into or an incorrectly seated cable. The screen itself is only delicate under flex and drops - the cable however like all fpcs is very easy to damage.
Hard disagree - the LCD is a multilayer stack of glass and tiny silicon structures that arenât visible to the naked eye. Itâs trivially easy to flex it far enough to tear some internal connections without causing visible damage. And in the picocalc specifically, itâs really easy to get the edges of the lcd (which are especially delicate) pinched between the pcb and the plastic case and then put significant pressure on it by cranking down on the screws. Mechanical advantage does the rest.
Whereas the flex cable, by definition, is flexible and can handle a fair amount of bending and even folding as long as itâs not sheared or cut.
hmm. whilst what you are saying is probably true in most situations, I was attempting to describe situations under which lines would appear on the screen whilst the screen itself appears to be visually intact. My comment regarding the fpc was regarding the contacts at each end rather than the ribbon part itself - although, of course hard kinks in a flex cable is capable of creating a faulty display too. Iâm not sure there is any benefit in debating the point though - feel free to disagree as you wish but I suspect if you jump on everybody you disagree with you will probably run out of energy quite quicklyâŚ
Honestly youâre not wrong - thereâs a real tendency for people to be contrary just for the sake of it. Which is why I specifically said I disagree, not that youâre wrong. After all, neither of us have seen the panel in question.
I was simply speaking from experience and from the specific circumstances that everyone who has a broken PicoCalc display seems to have gone through. Oh, and my own electronics engineering background. Doesnât mean I canât be incorrect! Either way the panel is still toast.
Nick,
Iâve been running into the problem you were having with the STM32 Firmware upload process. I too have a Pico 2W and upgraded the U2FLoader to allow my Pico to use the latest Pico 2 flashware versions. That works good now.
But I cannot seem to upgrade the STM32 Bios. It wonât work. I connect my Pico to my Windows 10 PC using the UART and COM:X settings in STMCubeProgrammer. That part works.
When I try to âDownloadâ the new version binary file âPicocalc_BIOS_v1.4.binâ I grabbed from the GITHUB ClockworkPI.Picocalc.Bin folder, I get the same error you did, i.e. âOperation exceeds memory limitsâ
I tried the 1.1 and the 1.2 version binary files as well. Looking at your screenshot, I notice your file, which has a size of âx3227Aâ and looks very much like an ASCII script or source code file, instead of a compiled binary file, like the screenshot from user âguuâ. His file is sized âx10000â whcih makes sense if it was compiled.
The trouble is all the versions of the STM32 âbinariesâ 1.1, 1.2 and 1.4 appear the be big ascii files instead of compiled BIN files. You said the file you downloaded (FROM github?) was âcorruptedâ, or as I see it, it was never compiled.
Where did you find the corrected file? I canât find a different one anywhere. Please advise.
I do not understand why this is happening. How do you âdownloadâ, what âtoolâ do you use for that purpose.
When I use chrome to access the bin directory and click on one if the bin files chrome starts the download and I receive the bin file in my download directory.
The two files are:
If you click on the line above the download for the binary files should start.
1 Like
Just as a test, I went to PicoCalc/Bin/PicoCalc_BIOS_v1.4.bin at master ¡ clockworkpi/PicoCalc ¡ GitHub under Chrome on Windows and clicked the âDownloadâ button and it downloaded a 64K binary, as expected. I do not see how one could end up with a file full of ASCII unless somehow one mistakenly downloaded one of the .hex files in the directory. But then it should end in .hex not in .binâŚ
1 Like
The newer versions of PicoMite will not run correctly until you update your firmware, so if you want to run MMBasic > 6.00.03 youâll need to update your firmware first.