md-uv380: add windows drivers and manufacturer flashing firmware inst…

[gx1400]

…ructions

[silseva]

Great work, thank you! Just a couple of notes:

• in the md-uv380 guide there is a "place link to ... here" note. Do you have the actual url, so that we can update the document?
• the procedure works also for the MD-380 series of radios, I'll make the guide generic for all the MDx devices. The only thing to change is the title.

I'll merge it in the next days as now I don't have the computer available.

[gx1400]

@silseva in the md-uv380 guide there is a "place link to ... here" note. Do you have the actual url, so that we can update the document?

Could you point me toward that? I'm struggling to find it

[gx1400]

I appear to be missing "../_media/drivers_stm32_dfumodeSuccess.jpg" on line 49 of win-stm32drivers.md

I need to check my laptop to see if I forgot to push that file or if it's in the wrong place

[silseva]

@silseva in the md-uv380 guide there is a "place link to ... here" note. Do you have the actual url, so that we can update the document?

Could you point me toward that? I'm struggling to find it

I was referring to this line https://github.com/OpenRTX/openrtx.github.io/blob/a01a0ccfc28c67286eefaeccd0f27ac4ebaf97f7/flashing/md-win.md?plain=1#L19 But apparently I misread it while looking at the markdown file. If you can add a link, good, otherwise nevermind. :)

Thank you!

[gx1400]

@silseva in the md-uv380 guide there is a "place link to ... here" note. Do you have the actual url, so that we can update the document?

Could you point me toward that? I'm struggling to find it

I was referring to this line https://github.com/OpenRTX/openrtx.github.io/blob/a01a0ccfc28c67286eefaeccd0f27ac4ebaf97f7/flashing/md-win.md?plain=1#L19 But apparently I misread it while looking at the markdown file. If you can add a link, good, otherwise nevermind. :)

Thank you!

Retevis's file download link was to an http:// IP address, not an FQDN. It was very sketchy, I dont know if it was a file drop or a permanent location.

My intent with the note was to note that the manufacturer may provide the file... Or someone could use some google-fu to find the same file online and check the hash.

At this point I do not want to drop a file link unless it's acceptable for openRTX to host the file. I'm unsure if that's reasonable.

[gx1400]

I checked my laptop and I do not appear to have the stm32 dfu image that is missing.

I left my USB cable at my parents over the holidays, so I don't currently have a cable available to take a new screenshot

[silseva]

I'll download the exe file and host it somewhere, is always a good idea to provide our own mirror as things on internet tend to magically disappear from time to time

[gx1400]

http://47.253.5.16/soft/FirmwareDownloadV3.04_EN.exe

[silseva]

Also this: https://www.hamdigitaal.nl/download/firmware/tyt_firmware/FirmwareDownloadV3.04_EN.exe

[gx1400]

Also this: https://www.hamdigitaal.nl/download/firmware/tyt_firmware/FirmwareDownloadV3.04_EN.exe

Yes, as you said, I'm generally hesitant to link files to others websites in case the file is moved or link goes dead.

I have been unsure about hosting third party software files, if there are any licensing or other concerns.

Links provided and do with it what you think is best!

[gx1400]

@silseva fixed the dead image link, I think it was a renamed image. I think ultimately it may have been a replicated image, so told it to link to a section of the same page above.

I think this may be ready for merge with your approval

[silseva]

Thank you! I'll merge it in the next days.

[silseva]

Thank you!