|
Hi all,
received my tinySA today (Aliexpress Toolbox-Store). Since some buyers
reported in this shop: 'no clone' I did risk it, because it was delivered within
~ 1 week from Czech Republic to Austria (without customs control, inside the EU)
- delivered in a dark brown box with golden print, tinySA in molded PVC
- cables + antenna etc. included
- sticker on the back of the tinySA looks OK (?)
- self test is OK !
VERSION:
- tinySA v0.3
- version tinySA_v1.1-66-g2015f17
- build time: Dec 27 2020 22:01:49
- internal shields are perfectly soldered
- device itself does what is supposed to do, via touch screen
but - on 2 differnt Win 7 PC and one Win 10 PC, on all of them, it says 'unknown USB device'.
Did the suggested procedure as on tinysa.org 'PC Control' but none of my PC recognized the
serial USB. Installed the drivers of en.stsw-stm32080.zip - no change, USB is not recognized.
Since there is no com port, I can not use the PC software or try to upgrade firmware.
any ideas please ?
greetings
Wolfgang
|
Seller Toolbox-store is known to have sold at least one clone. Can you post a picture of the front and back of the tinySA? --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Erik, thanks for the reply! Oh yes, it says 'HICH' on the front and not 'HIGH' :-( Sorry, will check at Zeenko Store on Aliexpress - up until mid of this year, there is no customs & VAT charge... hopefully! greetings Wolfgang   
|
This is a clone, but the USB driver has nothing to do with whether it is a clone or not. The USB-CDC serial port can be correctly identified without installing a driver on a fully installed Windows 10 operating system, unless their USB port is installed incorrectly.
|
On Tue, Feb 9, 2021 at 10:01 AM, Hugen wrote:
... unless their USB port is installed incorrectly
Thanks Hugen for the info, I guess so. If I connect, I just see in 'USB-Controller' an 'Unknown Device' and in this device property: This device does not work properly because the device firmware does not provide the necessary resources. (Code 29) Installed the drivers out of en.stsw-stm32080.zip with no sucess for the tinySA.
Looks like, there is no info from this 'tinySA' to tell Windows what kind of USB device it is, therefore no driver is selected to activate a com port. This has been tried on two different Win 7 Pro PC and on my Win 10 Laptop. Otherwise this thingy shows on inputs & touch display what it should do. But no com port...? :-(
|
Try a USB 2.0 port
Try a different USB cable --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Erik, all kind of different cables and ports was the very first thing I tried - without success ?
|
Hi Wolfgang,
Hugen said a tip: USB-CDC
How to do it: download that pdf file and find the cdc download link and its installation in the description.
I hope this helps in the solution.
Link: http://ha3hz.hu/images/download/Preparing_to_run_NanoVNAPartner_on_Windows_XP_HU.pdf
--
73, Gyula HA3HZ
|
Or even simpler: Goto device manager app Right click on faulty driver Click remove or uninstall drive unplug tinySA plug back in The driver may now install correctly If not, try again but when asked "remove driver from computer" or similar? say "Yes" ? --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Gentlemen,
thanks for all your tips. Whatever port I plug in, or cable I am using, the tinySA never
shows up in com ports, just in the section of the 'USB Controller' section as an 'unknown device'
Right click and remove / deinstall and power cycling the tinySA results in the same info.
Windows 10/x64 Laptop:
Info: Unknown USB device (error requesting a device description)
in properties: This device stopped because it caused errors. (Code 43) An error occurred while solving the USB device descriptor.
Windows 7 Pro/x64
Info: Unknown device
in properties: This device does not work properly because the device firmware does not provide the necessary resources. (Code 29)
Windows 7Pro/x64
Today this PC did not even recognized the connected device, different cables, different ports, plug-in/plug-out cycling
Have no idea why.
Remark: I am using Windows 7 pro and Windows 10 in German language, the shown messages had been translated.
So, it looks like, the USB section in this clone has a fault and does not report it's device type to Windows.
FYI: I am a developer for Ham Radio software, 'CW via CAT' etc. , so I am pretty firm with all this com port stuff.
Never mind, a hopefully 'real tinySA' was ordered at Aliexpress Zeenko Store yesterday.
|
|
|
On Wed, Feb 10, 2021 at 09:26 AM, Gyula Molnar wrote:
/g/tinysa/message/3040
interresting link, thanks for that. But all this can and will not help in my setup, because my tinySA (clone) is not shown as a com port device with a missing driver. Therefore
DfuSeDemo? does not recognize my tinySA clone in DFU mode. The STM32 Boot-
loader does not help.The only indication I see is in Windows Device Manager on 'USB Controller' as an 'Unknown Device' (see picture). My default com ports showing no changes or new entries if I plug in/power on the tinySA clone. Deinstalling the 'Unknown Device' will bring it up after the next off/on cycle. USBVIEW.exe (Microsoft) and USBDeview.exe (Nirsoft) showing all kind of connected, or even disconnected devices, but never ever any info/change by the tinySA clone. I guess, since the one message (see my previous post) says 'Error 29' Windows does not know what type of? USB device has been connected - audio, keyboard, com port, or whatever. Looks like a garbled USB interface routine in the firmware. At the end, it's a lesson learned about crippled USB devices ;-) 73's de OE1MWW Wolfgang  
|
When I connect the tinySA to the USB port, it appears in device
manager on the Ports(COM & LPT) as "USB serial device (
COM6)".
As soon as I enter DFU mode via config, the device disappears
from the Ports list. On the tinySA app it appears on the upload
firmware as Port_#0003.hub_#0004 followed by a string of code.
Upload works OK. It also works on STMicroelectronics? Dfuse Demo.
Again, no indication on the device manager but it works.
On 10/02/2021 18:42, Wolfgang OE1MWW
wrote:
toggle quoted message
Show quoted text
On Wed, Feb 10, 2021 at 09:26 AM, Gyula Molnar wrote:
/g/tinysa/message/3040
interresting link, thanks for that. But all this can and will not
help in my setup, because
my tinySA (clone) is not shown as a com port device with a missing
driver. Therefore
DfuSeDemo? does not recognize my tinySA clone in DFU mode. The
STM32 Boot-
loader does not help.
The only indication I see is in Windows Device Manager on 'USB
Controller' as an
'Unknown Device' (see picture). My default com ports showing no
changes or new
entries if I plug in/power on the tinySA clone. Deinstalling the
'Unknown Device'
will bring it up after the next off/on cycle.
USBVIEW.exe (Microsoft) and USBDeview.exe (Nirsoft) showing all
kind of connected,
or even disconnected devices, but never ever any info/change by
the tinySA clone.
I guess, since the one message (see my previous post) says 'Error
29' Windows does
not know what type of? USB device has been connected - audio,
keyboard, com port,
or whatever. Looks like a garbled USB interface routine in the
firmware.
At the end, it's a lesson learned about crippled USB devices ;-)
73's de OE1MWW
Wolfgang
 
|
What vendor ID/product ID pair do you see?
Gr¨¹?e, Carsten
|
Geoff, you wrote ''As soon as I enter DFU mode via config, the device disappears from the Ports list''. That is how it is supposed to be with the TinySA in DFU mode. Now, in Device Manager, section Universial Serial Bus controllers you should see ''STM Device in DFU Mode''. Martin 9A2JK 
|
Thanks Martin, mine works OK and is exactly as you say. The other
chap seemed concerned that it was not in the Ports list when in
DFU mode.
On 11/02/2021 09:34, Martin J.K. wrote:
toggle quoted message
Show quoted text
Geoff,
you wrote ''As soon as I enter DFU mode via config, the device
disappears from the Ports list''.
That is how it is supposed to be with the TinySA in DFU mode.
Now, in Device Manager, section Universial Serial Bus controllers
you should see ''STM Device in DFU Mode''.
Martin 9A2JK
|
?
There are two firmware upgrade software components: a driver and firmware upgrade software, DfuSe.?
The driver is included with the DfuSe software but it is not always properly installed.
Step by step instructions how to install the driver are in ''Absolute Beginner's Guide to NanoVNA''.?
This PDF guide could be downloaded from file section of nanovna-users group:
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA
Martin 9A2JK
|
So, now, a 'original' tinySA from Zeenko Store is on it's way from China to me.
Monday 22. Feb. Aliexpress should step in to finalize the dispute I have opened with
the Toolbox-Store. Toolbox-Store answers are either 'cheating' or they have no idea
what and why I complain about their delivery, even shown in pictures & videos + text
from my side.
Nevertheless, the com port on the 'bad clone' does not work via USB-C - no way!
If I bring the device into DfuSeDemo? mode and connect via the UART pins on the board
will this allow me to access and upgrade the firmware?
On the board, the TX and RX port, are they labled as 'TX has to go to the 'TX' and 'RX
goes to RX' port of a serial USB device, or cross-over?
|
The UART is currently NOT enabled in any of the SW If you want to use something else than serial over USB (DFU mode) you will have to use an ST-Link with STM32CubeProgrammer and connect it to GND, SWCLK and SWDIO --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Rudi Imbrechts, #3040,
his link to STM32 Bootloader, solved my driver problem immediately !
I have downloaded and installed this Bootloader and it works perfect now.
!! Thanks !
Hans DF2MC
|
Gyula Molnar