Stuck in DFU mode

[din...@objective-design.com]

After trying to update firmware on my MD-380 (using a Mac), the radio is now stuck in DFU mode, flashing red and green. Further update attempts also fail, despite others saying that if an update fails, subsequent attempts will usually succeed. The typical md380-dfu failure message is "input/output error."

Using the TYT firmware updater on Windows similarly fails. I can't really tell what failed, though, since the TYT software output is unreadable. I've tried the 11/29 and 9/8 firmware versions from the Tytera website.

This whole process worked last week when I replaced the stock firmware with Travis's patched firmware, also using a Mac. It was only when I tried to pull the latest changes and do another update that I managed to brick the radio. Note that the radio is the new vocoder version.

Is there any way to unbrick the radio? Perhaps a minimalist firmware image? Or through some internal hardware interface? Thanks!

--Dan

[Mike, DL2MF]

Does the connector fits 100% at the radio side? A little edge of plastic sometimes avoid a solid fit.

Additionally please you check your USB cable, they are sometimes broken at the USB side.

[Sergy Shu]

Dear Mike, thanks for reply. I found the source of possible reason: name of group inside my MD380 is doesn't fit. Is it possible to adjust MD380 settings to listen all DMR activity inside the channel?

четверг, 1 декабря 2016 г., 10:26:19 UTC+2 пользователь Mike, DL2MF написал:

[Dan Ingold]

UPDATE:

I'm pretty sure it's not the cable. The radio is new (1 week), the cable worked only two days ago uploading the users.csv, and it hasn't had any stress nor does it show any signs of damage at either end.

Oddly, the error message from md380-dfu changes almost every time:

➜  md380tools git:(master) ✗ sudo ./md380-dfu upgrade applet/experiment.bin
Beginning firmware upgrade.
[Errno 60] Operation timed out
➜  md380tools git:(master) ✗ sudo ./md380-dfu upgrade applet/experiment.bin
Beginning firmware upgrade.
[Errno 5] Input/Output Error
➜  md380tools git:(master) ✗ sudo ./md380-dfu upgrade applet/experiment.bin
[Errno 5] Input/Output Error
➜  md380tools git:(master) ✗ sudo ./md380-dfu upgrade applet/experiment.bin
The device has no langid

[Dan Ingold]

I don't mean to be rude, but how is this comment relevant to my question?

73,
K6DI

[Dan K6DI]

UPDATE 2:

This morning I was able to flash v13.20 to the radio using the Tytera upgrader, albeit not successfully. That is, the image appears to upload to the radio. The upgrade program then displays a small dialog box with "Upgrade" followed by gibberish.

The good news is that after this upload the radio is no longer stuck in DFU mode. The bad news is that it doesn't appear to power on at all---no splash or operating screens. I can put the radio back into DFU mode using the usual two-key sequence, but still no joy after several additional attempts at flashing v13.20.

In trying to flash Travis's hacked firmware, the md380-dfu tool still times out, or gets an input/output error, or an overflow error, with no apparent rhyme or reason. And then the radio is back flashing red/green in DFU mode as soon as you turn it on.

--Dan K6DI

[Mike, DL2MF]

Hi Dan,

ok, that looks like the firmware is not correct for your model, do you get the blank white screen after power on?

Mike, DL2MF

Am Donnerstag, 1. Dezember 2016 18:30:24 UTC+1 schrieb Dan K6DI:

UPDATE 2:

[Dan K6DI]

The screen is black after updating to v13.20. It's as though the power never was turned on. No screen. No LED lights. No tones. No nothing. 

Of course, it's not even clear that the Tytera updater actually worked. The progress bar marched across the screen. It put up an unreadable dialog when it finished, which could have said "success" or "failure" (who knows). What is odd is that I seem to remember the phone rebooting after updating last week. Now the radio remains in DFU mode after the update, until I turn it off. And then it apparently won't turn back on, although I can put it back in DFU mode. 

I'm sure this is the right firmware. In fact, it's exactly the same firmware I flashed last week when I first received the radio (before I changed to Travis's hacked firmware), and the radio worked fine then. 

Thanks for the suggestions, though. This is a real mystery, as supposedly if the radio can be put into DFU mode it can be recovered. 

--Dan

[Dan K6DI]

UPDATE 3: Success! The patched firmware uploaded and the radio is functional again.

HOWEVER, I did this by going back to the original computer I used last week (also a Mac, which I didn't have with me earlier this week). So apparently the problem was not with the tools, radio, or firmware, but with some characteristic of the environment.

I don't know the cause, but suspect it's a bad driver or the wrong library. Unfortunately I didn't keep notes on how I configured the computer that works, and so I also don't know how the new computer might be configured differently. I'll do some checking and report back.

[t...@thesounddesign.com]

This just happened to my radio ... on OSX 10.9.5 / MacBook Pro 2013

I used the debian virtual machine by KD4Z, using the latest GLV of MD380Tools....  did anyone ever figure out how to restore the radio? 

[Dale Farnsworth]

It has been my experience that when we see the flashing red/green lights we think it's in DFU mode, when that's not necessarily true.  Before attempting to reflash the radio, make sure you you put the radio in DFU mode by powering on while pressing the button above the PTT.  Try using KD4Z's md380tools virtual machine to program the firmware again.  As a fallback, if you can get access to a Windows or Linux machine, use could editcp to flash the original firmware.

Just in case, note that md380tools do not work on the MD-UV380/390.

I hope you can get your radio going soon.

Dale, NO7K

--
You received this message because you are subscribed to the Google Groups "md380tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to md380tools+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/md380tools/53a02603-2258-4438-bccf-05ace38bcd85%40googlegroups.com.

[Tim Boyce]

Thanks Dale, 

      I seem to get a different error each and every time I try flashing ... (does the screen shot attach?) .. 

Sometimes an I/O error, sometimes Other Error, sometimes Read Error, sometimes Config Error ... just seems no rhyme or reason. . . This is on a MD380 .. in fact it HAD 380Tools already installed when I got it .. but when I tried to update the codeplug it got weird, then I tried to flash it and after few attempts of it not connecting/working, it got stuck in DFU. 

This was all in VirtualBox or FusionVM through KD4Z tools on OSX ... I started using FusionVM because it asked me specifically , so I want to connect the USB to linux or OSX .. Virtualbox seemed like the host OSX was stealing the USB first

 ... what is editcp,   I have a Parrot USB stick I could boot from,  or run it through a VM ... it would be the same machine though. I only have 1x laptop

You received this message because you are subscribed to a topic in the Google Groups "md380tools" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/md380tools/TXzJuGG9vLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to md380tools+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/md380tools/CAEy-6SZaZJXj2ob0o9N5ith2d%2B8xPnfUaz_%3DXL4p-fB80uVH%2Bg%40mail.gmail.com.

--

---

      Tim Boyce
Mastering and Design NYC
+1 315 436-7449
www.thesounddesign.com

[Dale Farnsworth]

It sounds like something is broken/intermittent on the USB connection between your computer and the radio, either software or hardware.  Or, it could be because of different timing when running in a VM.  An editcp user reported an issue running in in a VM on Mac.  I lengthened a delay during firmware programming that seemed to resolve his issue.

You might try editcp in a VM, either the Linux version or the Windows version.  It can write firmware and read/edit/write codeplugs.

https://www.farnsworth.org/dale/codeplug/editcp/

But, I'll say it once more: flashing red/green does not mean DFU mode.  It could just mean a failed boot.

Dale, NO7K

To view this discussion on the web, visit https://groups.google.com/d/msgid/md380tools/CANRzYye-vkQA6NSLbdM_QT_84BMXjcs3xM69FrCMW8UieYPXKg%40mail.gmail.com.

[Tim Boyce]

Thanks Dale, 

   I'll check out editcp

 I can boot the radio in two modes ... 

 "STMicroElectronics Digital Radio in USB Mode"
 or  "STMicroeletronics USB Device"

It almost always boots into "...Digital Radio in USB Mode"  which I assume is DFU

To view this discussion on the web, visit https://groups.google.com/d/msgid/md380tools/CAEy-6Sb_3Aobxg9TV4fTuM0AWmt1ZuKDc8-J%3DQRD4b14s0quzQ%40mail.gmail.com.