¿ªÔÆÌåÓý

  1. Tinysa
  2. Topics

firmware erasure?

 

Newbie attempt at updating the firmware. I was following someone's tutorial, everything seemed fine on STM32Cube, I pressed Start Programming, and instead of a long string of commands executing my process only took one second and when I went to restart there was....nothing but black screen. I don't recall the messaging at this point, but the result was the complete opposite of what I was aiming for. The power is present as can be seen by the red light indicator. But no boot...nada. I somehow managed to erase the firmware and the bios too? Now neither windows nor STM32 recognizes the device so I am a ship without a sail at this point.

Where do I go from here?

Thank you for whatever assistance you may be able to provide.

Valis
 

Now I want to add the function of wireless data transfer to the computer on tinysa, is there a better solution

valis via <valis=[email protected]> ÓÚ 2024Äê6ÔÂ14ÈÕÖÜÎå ÏÂÎç1:34дµÀ£º

Newbie attempt at updating the firmware. I was following someone's tutorial, everything seemed fine on STM32Cube, I pressed Start Programming, and instead of a long string of commands executing my process only took one second and when I went to restart there was....nothing but black screen. I don't recall the messaging at this point, but the result was the complete opposite of what I was aiming for. The power is present as can be seen by the red light indicator. But no boot...nada. I somehow managed to erase the firmware and the bios too? Now neither windows nor STM32 recognizes the device so I am a ship without a sail at this point.

Where do I go from here?

Thank you for whatever assistance you may be able to provide.

Valis

 

On the tinySA PCB there are connections for a serial interface labeled RX and TX.
Connect these so a serial - wireless module and select the serial interface in the tinySA CONFIG/CONNECTION/SERIAL and set the serial speed
--
Designer of the tinySA
For more info go to https://tinysa.org/wiki/
 

On Fri, Jun 14, 2024 at 07:34 AM, <valis@...> wrote:
Newbie attempt at updating the firmware. I was following someone's tutorial, everything seemed fine on STM32Cube, ...

Hello Valis,?
your attempt to follow an unknown tutorial has probably led you down the wrong path. ?It makes a lot of sense to trust the information in the wiki. e.g. ?

?

?
 

The latest STMcube app was the last straw for me?

Please someone, ?Make basic firmware flashing for end users a simple activity not a trip to a smoke filled starship¡¯s engine room?
 

Repeat after me

Everything On line and everything on YouTube in particular is not always right

some is out of date
some omits important steps?
some is just flat out wrong?

The dudes ¡®showing you stuff¡¯ in a staged set on wrongly chosen/connected/adjusted test equipment and with no skill apart from liking talking are worst?
 

As clearly stated you should NOT use the latest Cube programmer but version 2.15
--
Designer of the tinySA
For more info go to https://tinysa.org/wiki/
 

On Fri, Jun 14, 2024 at 03:08 AM, Erik Kaashoek wrote:
As clearly stated you should NOT use the latest Cube programmer but version 2.15
? The following was reported by a user on the NanoVNA group:

"I have found that version 2.16.1 will indeed work, but you must do the 'full chip erase' before updating the firmware. Evidently in 2.16.x the erase function is no longer integrated with the programming."

If true, that would explain why users are having problems using the Wiki "Cube programmer" upgrade procedure with versions greater than 2.15.

Herb
 

On Fri, Jun 14, 2024 at 02:41 AM, Bruce Akhurst wrote:
Please someone, ?Make basic firmware flashing for end users a simple activity not a trip to a smoke filled starship¡¯s engine room?
From the command line, use:
dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D ./tinySA4_v1.4-72-gf8c2707.bin

That's on Linux, but there are Win32, Win64, Linux AMD64, and Darwin (Mac) binaries in this zipped file:

https://dfu-util.sourceforge.net/releases/dfu-util-0.11-binaries.tar.xz

In Linux, it's probably in the repositories in most distributions.

dfu-util homepage, if you want more information:

https://sourceforge.net/projects/dfu-util/
 

On Fri, Jun 14, 2024 at 09:41 AM, Bruce Akhurst wrote:
Please someone, ?Make basic firmware flashing for end users a simple activity not a trip to a smoke filled starship¡¯s engine room?
Just install the TinySA app on your PC, get that running and then not only do you have extended features and control via a much larger GUI on your PC screen, you can also update the firmware with just a couple of mouse clicks.

It seems daunting, but once you have done it the first time, it becomes second nature.

Regards,

Martin
 

Not sure why nobody has mentioned the lines from the wiki that say:

If the upgrade fails and you get a white or black LCD screen.

If the upgrade fails for some reason (wrong file, power failure) you may get a tinySA that seems to be bricked. Luckily it is impossible to brick the tinySA. Follow these steps to unbrick:

tinySA

  • Switch off.
  • Open the case by removing the 4 screws at the back
  • Connect the two pcb edge points marked VDD and BOOT0
  • Switch on.
  • Lcd turns white
  • You can disconnect the VDD and BOOT0 if needed
  • Connect to PC using the USB cable
  • Just to be double sure, open the device manager or Linux equivalent and check a DFU device is added and the driver is correctly loaded (no yellow exclamation mark)
  • Update firmware

tinySA Ultra

  • Switch off.
  • Press the Jog button down.
  • Switch on.
  • Lcd stays black
  • Connect to PC using the USB cable
  • Make sure you hear the happy sound from your PC to be sure a driver is correctly loaded. If this does not happen, try a different USB cable, a USB 2.0 port or different computer
  • Just to be double sure, open the device manager or Linux equivalent and check a DFU device is added and the driver is correctly loaded (no yellow exclamation mark)
  • Update firmware


NOTE WHERE IT SAYS: Luckily it is impossible to brick the tinySA
 

Erik and others were right - you cannot brick the TinySA.


I deleted cube 2.16 and replaced it with 2.15. I should have exercised some quality control time

before rushing to program. As originally and clearly recommended in the wiki.


I programmed it successfully with 2.15.


It lives and breathes again.


Thank you all for the thoughtful assistance and feedback.


Valis


















StartMail makes private and encrypted email easy. !


On Friday, June 14, 2024 5:47 PM, m0cnl <m1cxz.m0cnl@...> wrote:

Not sure why nobody has mentioned the lines from the wiki that say:

If the upgrade fails and you get a white or black LCD screen.

If the upgrade fails for some reason (wrong file, power failure) you may get a tinySA that seems to be bricked. Luckily it is impossible to brick the tinySA. Follow these steps to unbrick:

tinySA

  • Switch off.
  • Open the case by removing the 4 screws at the back
  • Connect the two pcb edge points marked VDD and BOOT0
  • Switch on.
  • Lcd turns white
  • You can disconnect the VDD and BOOT0 if needed
  • Connect to PC using the USB cable
  • Just to be double sure, open the device manager or Linux equivalent and check a DFU device is added and the driver is correctly loaded (no yellow exclamation mark)
  • Update firmware

tinySA Ultra

  • Switch off.
  • Press the Jog button down.
  • Switch on.
  • Lcd stays black
  • Connect to PC using the USB cable
  • Make sure you hear the happy sound from your PC to be sure a driver is correctly loaded. If this does not happen, try a different USB cable, a USB 2.0 port or different computer
  • Just to be double sure, open the device manager or Linux equivalent and check a DFU device is added and the driver is correctly loaded (no yellow exclamation mark)
  • Update firmware


NOTE WHERE IT SAYS: Luckily it is impossible to brick the tinySA


 

Can anyone confirm that version 2.16 is working?

With full chip Erase? Before or with firmware upgrade?


For me is not seeable the "version 2.16.1" only the "2.16.0"

This version is now three months old and no further fixes have been received.


Istvan
 

I used STMCube Programmer v2.16.0 yesterday to update both my TinySA and my NanoVNA-H4 successfully. ? I just used the "Full Chip Erase" function (using the button to the right of the programming panel) before "start programming".?

I presume it would also work if you use the "Automatic Mode" and check the "Full chip erase" box.

It appears that in this version they have separated the erase function from the programming.? In the "Log" on v2.15.0 you see lines showing blocks being erased during the programming; those are not present in v2.16.0.

Note that this version also uses the Win10 default "STM Bootloader" driver, no need to install the "STM Device in DFU mode" driver required by nanovna-app and dfusedemo.? (And my earlier mention of v2.16.1 was a typo)

Stan

1 - 14 of 14