md380tools icon indicating copy to clipboard operation
md380tools copied to clipboard

Published 20 hours ago • verified publisher icon travisgoodspeed

Compatible Hardware

Open i2bator opened this issue 7 years ago • 32 comments

Its almost the end of 2018.

Anyone could please clarify these 2 questions: "What radios are still fully or partially compatible with this firmware?" (please see the list below) "Are there any compatibility issues with particular sellers online (same model but slightly different hardware or stock firmware, or New Vocoder/ Old Vocoder?

'73

Following is a list of possible DMR models in question:

TYT MD-380 UHF TYT MD-380 VHF TYT MD-380G VHF+GPS TYT MD-380G UHF+GPS

TYT MD-UV380 (UHF+VHF) TYT MD-UV380 (UHF+VHF+GPS)

TYT MD-390 UHF TYT MD-390 VHF TYT MD-390G VHF+GPS TYT MD-390G UHF+GPS

TYT MD-UV390 (UHF+VHF) TYT MD-UV390 (UHF+VHF+GPS)

TYT MD-2017 (UHF+VHF) TYT MD-2017 (UHF+VHF+GPS)

Retevis RT3 UHF Retevis RT3 VHF Retevis RT3 VHF+GPS Retevis RT3 UHF+GPS

Retevis RT3S (UHF+VHF) Retevis RT3S GPS (UHF+VHF+GPS)

Radioddity GD-77 (UHF+VHF)

?? any other radios??

i2bator avatar Oct 03 '18 23:10 i2bator

Close this issue when the list is verified and at the top of README.md. We should include a list of incompatible models just to be clear.

travisgoodspeed avatar Oct 03 '18 23:10 travisgoodspeed

Please add Retevis RT82 to this list, i think it is exactly the same as TYT MD2017. https://github.com/KG5RKI/TyMD380Tools/tree/md2017 had work on it. But it seem to be some files missing to compile it. Here are some Links to compiled binaries for the RT82. https://github.com/KG5RKI/TyMD380Tools/issues/2

Scytie avatar Nov 03 '18 21:11 Scytie

None of the dual-band radios (MD2017, RT3S) are supported by this project, only the mono-band UHF and VHF radios. TyMD380Tools is a hard fork with no version history, and merging it to the master branch will not be easy.

travisgoodspeed avatar Nov 04 '18 17:11 travisgoodspeed

Yeah, I just tried with my dual-band MD-UV390 (GPS). Had issues with the mac build (the tools couldn't find the device) but I was able to try uploading the modified firmware using the stock software. It just kept flashing red/green after the power cycle.

Re-uploading the default 17.05 firmware restored the radio.

dschuetz avatar Nov 04 '18 19:11 dschuetz

When i get my RT82 and get when KG5RKI's version running. I diff his code with this code here for a pull request. But a this moment I need a file I do not have. It is the Header of the unwrapped firmware. It should be 1.3mb - 900kb = 400kb in size. (See KG5RKI/TyMD380Tools#2)

Scytie avatar Nov 04 '18 21:11 Scytie

just a status update: Ty (KG5RKI) uploaded his RT82 Stuff: https://github.com/KG5RKI/RT82Toolz Using python = python2 I am able to build a new firmware. If I find time I will diff this repo and https://github.com/KG5RKI/RT82Toolz to merge these two.

Scytie avatar Feb 19 '19 19:02 Scytie

Please add Retevis RT82 to this list, i think it is exactly the same as TYT MD2017. https://github.com/KG5RKI/TyMD380Tools/tree/md2017 had work on it. But it seem to be some files missing to compile it. Here are some Links to compiled binaries for the RT82. KG5RKI/TyMD380Tools#2

add retevis rt80 too please

adron51 avatar May 29 '19 20:05 adron51

i can only see dmr id om my retevis would love to see all info like i do on my md380 thanks

adron51 avatar May 29 '19 21:05 adron51

Would it be worth noting on the supported MD380/MD390 models about the various hardware versions and reported incompatibilities, and how to read the hardware version in CPS?

driviera avatar Jun 18 '19 01:06 driviera

@driviera yes, please! I'm still quite new to this particular scene, but it's incredibly difficult to find good documentation on:

  • what the "difference" between TYMDToolz and BetaMDToolz and MD380tools is. The first two are forks of the former that add new features... but none? of the forks was merged back into the upstream!?

  • how to tell if the device you're holding is compatible with any of the custom firmware. the warning here just says v14 and higher wont work. My unit has a FW version of S018.003 and a CP version of 1.06. I am assuming that the "14" is in reference to the radio FW version and that 18 > 14 so i am SOL... but that warning was on the TyMDToolz page, so only that fork (which, hasn't?) been merged into upstream is? affected?

  • Which version of the vocoder do i have? That's something you figure out by looking at the cp? version?

FWIW, i have a MD-UV390 (GPS)

kquinsland avatar Jun 23 '19 17:06 kquinsland

Travis Goodspped and team is the originator of the so called 'experimental firmware', aka custom firmware. MD380Toolkit is a shell and a bundle of utility scripts, using the Travis' firmware as the 'engine' for this Toolkit. Both are well supported and each add-on or modification / bug-fix is well tested by the Travis-team before release. The ToolZ are an earlier off-spring and isn't following the Travis guidelines.

Op zo 23 jun. 2019 19:13 schreef Karl Q. [email protected]:

@driviera https://github.com/driviera yes, please! I'm still quite new to this particular scene, but it's incredibly difficult to find good documentation on:

what the "difference" between TYMDToolz and BetaMDToolz and MD380tools is. The first two are forks of the former that add new features... but none? of the forks was merged back into the upstream!?

how to tell if the device you're holding is compatible with any of the custom firmware. the warning here http://www.miklor.com/DMR/DMR-Toolz108.php just says v14 and higher wont work. My unit has a FW version of S018.003 and a CP version of 1.06. I am assuming that the "14" is in reference to the radio FW version and that 18 > 14 so i am SOL... but that warning was on the TyMDToolz page, so only that fork (which, hasn't?) been merged into upstream is? affected?

Which version of the vocoder do i have? That's something you figure out by looking at the cp? version?

FWIW, i have a MD-UV390 (GPS)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/travisgoodspeed/md380tools/issues/890?email_source=notifications&email_token=AF37CP35MBT6MSIXWIRSYFTP36VLHA5CNFSM4FY4QCK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLC55I#issuecomment-504770293, or mute the thread https://github.com/notifications/unsubscribe-auth/AF37CP4BTDDN5BV337E5UDLP36VLHANCNFSM4FY4QCKQ .

PD0DIB avatar Jun 23 '19 17:06 PD0DIB

FWIW, i have a MD-UV390 (GPS)

These tools are not for the MD-UV390. They are for the MD-380 and MD-390 (with or without GPS; and parallel single-band radios). Many of the features of the MD380Tools are already integrated into the native MD-UV390 firmware.

driviera avatar Jun 23 '19 23:06 driviera

The MD-UV380 does not have the same features as this custom firmware, like ad-hoc mode, and a support for this radio would be greatly appreciated by me, and the community.

brokechubb avatar Jul 05 '19 14:07 brokechubb

I too would love extra features on the MD-UV380

73 Dave

G4AON avatar Jul 16 '19 16:07 G4AON

Bump. Got the dual band version of the tyt 390G and found out the hard way that the dual band wasn't supported: red/green blinkies and no boot. Support for this radio would be awesome.

AppliedEM avatar Jan 21 '20 05:01 AppliedEM

Could someone let me know whether the encryption on the UV-380/390 is the same , or possibly similar to the MD-380, or whether it would be possible to retrieve a copy of the bootloader from those radios, like Travis originally did?

It does not matter to me whether the MD-380 tools binaries work on these radios, which they almost certainly won't since the baseband IC is not the same.

But I'd like to be able to encrypt and upload my own firmware.

rogerclarkmelbourne avatar Apr 23 '20 02:04 rogerclarkmelbourne

@rogerclarkmelbourne I suspect the UV-380 is basically just a MD-2017 in a -380 case. If that's true, you might try Ty Weaver (KG5RKI)'s fork of md380tools, branch md2017: https://github.com/KG5RKI/TyMD380Tools/tree/md2017

ghost avatar Apr 23 '20 02:04 ghost

@mach327

Thanks. I'll take a look.

I'm thinking of buying a UV-380 (actually a RT3S which I'm pretty sure is the same radio), but I don't want to throw money away on something which the encryption hasn't been broken. Because although I'm going to solder to the SWD connections, for dev work, I need to be able to deploy to other people's radio via the normal firmware load procedure.

rogerclarkmelbourne avatar Apr 23 '20 03:04 rogerclarkmelbourne

Is it possible to read and write code plug .rdt files to and from the UV-380 with md380-dfu? I'm not trying to do firmware updates at this stage, just to program my radio. If not is there any other known way to read and write code plugs to a UV-380 without having to use the TYT CPS software on Windows?

ae14 avatar May 19 '20 09:05 ae14

@ae14 md380tools will not. I vaguely recall getting MD2017 codeplug to-radio to work in one of my branches a few years back, but ... not really, no.

Mr Farnsworth's excellent Editcp will do this. Editcp does a great job as a full TYT CPS replacement/clone.

If you're running Mac or Linux, and have Chrome or Chromium, you might also try my WebDFU programmer entirely in the browser and let me know how it works for you. It's, uh... not ready for primetime yet, but it Works On My Machines (tm) and I could use the feedback for when I get back to working on it. You (or anyone else) can email me directly until I can get the project up and public on github.

Mine currently won't read codeplugs off the radio and give you an RDT, it just gives an unwrapped bin, but it writes codeplugs just fine!

ghost avatar May 19 '20 11:05 ghost

Further to my other dumb questions....

Has anyone extracted the bootloader from the MD-9600 or the UV-380

Actually, I'm sure I can extract the bootloader from the UV-380, but I'm not sure if the tools can be used to extract it from the 9600 and I don't have access a 9600 to try it

rogerclarkmelbourne avatar Sep 13 '21 23:09 rogerclarkmelbourne