[chirp_users] FT70 fails to download
Howdy!
Running a Yaesu Ft-70DR that just arrived today. First thing's first: download to Chirp! Running daily 20190221 on Debian current stable, using the builds from the website.
Just one problem - it didn't download.
After following instructions (battery off, DC and USB in (specifically the USB cable that came with), hold AMS key while powering on, select Download option, set the right options (/dev/ttyACM0, Yaesu FT-70D)), hit the BAND button so it says TX, and...
...no activity. It times out, radio shows ERROR.
Long and short, I'm not sure if I'm doing something wrong here. So in short:
* What am I missing? * What other information is needed from me to properly answer?
-Dennis KE7KIF
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that would be assigned to a modem a fake modem such as an OTG-connect3d phone or something like that. Check this by first unplugging the cable from the comouter and then doing: ls /dev/tty* Then plug the cable back into the computer and repeat the command. a new device should have appeared. That's the device for your cable. on my computer, USB serial dongles get addresses like /dev/ttyUSB0
On Wed, Apr 3, 2019 at 9:35 PM Dennis Carr dennisthetiger@chez-vrolet.net wrote:
Howdy!
Running a Yaesu Ft-70DR that just arrived today. First thing's first: download to Chirp! Running daily 20190221 on Debian current stable, using the builds from the website.
Just one problem - it didn't download.
After following instructions (battery off, DC and USB in (specifically the USB cable that came with), hold AMS key while powering on, select Download option, set the right options (/dev/ttyACM0, Yaesu FT-70D)), hit the BAND button so it says TX, and...
...no activity. It times out, radio shows ERROR.
Long and short, I'm not sure if I'm doing something wrong here. So in short:
- What am I missing?
- What other information is needed from me to properly answer?
-Dennis KE7KIF
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Silly me. On Debian systems (and on my Gentoo system) you can just do this: ls -l /dev/serial/by-id This directory has a file whose name is the ID string of each serial device , linkte to the tty filename. With this approach you do not need to unplug and re-plug your cable.
On Wed, Apr 3, 2019 at 9:51 PM Dan Clemmensen danclemmensen@gmail.com wrote:
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that would be assigned to a modem a fake modem such as an OTG-connect3d phone or something like that. Check this by first unplugging the cable from the comouter and then doing: ls /dev/tty* Then plug the cable back into the computer and repeat the command. a new device should have appeared. That's the device for your cable. on my computer, USB serial dongles get addresses like /dev/ttyUSB0
On Wed, Apr 3, 2019 at 9:35 PM Dennis Carr dennisthetiger@chez-vrolet.net wrote:
Howdy!
Running a Yaesu Ft-70DR that just arrived today. First thing's first: download to Chirp! Running daily 20190221 on Debian current stable, using the builds from the website.
Just one problem - it didn't download.
After following instructions (battery off, DC and USB in (specifically the USB cable that came with), hold AMS key while powering on, select Download option, set the right options (/dev/ttyACM0, Yaesu FT-70D)), hit the BAND button so it says TX, and...
...no activity. It times out, radio shows ERROR.
Long and short, I'm not sure if I'm doing something wrong here. So in short:
- What am I missing?
- What other information is needed from me to properly answer?
-Dennis KE7KIF
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, 3 Apr 2019 22:03:22 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
Silly me. On Debian systems (and on my Gentoo system) you can just do this: ls -l /dev/serial/by-id
Well, that comes out with usb-26aa_001b_000000000000-if00 - which matches the devid in lsusb.
-Dennis
On Wed, 3 Apr 2019 21:51:05 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that would be assigned to a modem a fake modem such as an OTG-connect3d phone or something like that.
Yeah, confirmed, it's /dev/ttyACM0. Tried 'watch'ing that, but 'watch ls /dev/tty*' is kinda useless as it overflows.
on my computer, USB serial dongles get addresses like /dev/ttyUSB0
I got that as well with the Baofeng clone cable I've got, doesn't seem to be the case here.
The only other thing making me think about this a bit is the fact that 'lsusb' comes up with this:
Bus 003 Device 025: ID 26aa:001b
...that's it, no description following the devid. So my computer sees something there, it just doesn't know what it is.
...am I missing something somewhere, a kernel mod maybe?
-Dennis
that's the device ID for a pl2303. the name of the module is pl2303
execute lsmod to see if the module got loaded.
If not, sudo modprobe pl2303 to force-load the module
On Wed, Apr 3, 2019 at 10:07 PM Dennis Carr dennisthetiger@chez-vrolet.net wrote:
On Wed, 3 Apr 2019 21:51:05 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that would be assigned to a modem a fake modem such as an OTG-connect3d phone or something like that.
Yeah, confirmed, it's /dev/ttyACM0. Tried 'watch'ing that, but 'watch ls /dev/tty*' is kinda useless as it overflows.
on my computer, USB serial dongles get addresses like /dev/ttyUSB0
I got that as well with the Baofeng clone cable I've got, doesn't seem to be the case here.
The only other thing making me think about this a bit is the fact that 'lsusb' comes up with this:
Bus 003 Device 025: ID 26aa:001b
...that's it, no description following the devid. So my computer sees something there, it just doesn't know what it is.
...am I missing something somewhere, a kernel mod maybe?
-Dennis _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, 3 Apr 2019 22:20:07 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
that's the device ID for a pl2303. the name of the module is pl2303
execute lsmod to see if the module got loaded.
It's there:
dennisthetiger@goodfellow:~$ lsmod | grep pl2303 pl2303 20480 0 usbserial 49152 1 pl2303 usbcore 253952 17 uvcvideo,usbhid,snd_usb_audio,usb_storage,ehci_hcd,cdc_acm,ohci_pci, usbserial,xhci_pci,snd_usbmidi_lib,uas,ohci_hcd,pl2303,xhci_hcd, ehci_pci
To wit, just started an update. None of the updates contain anything USB flavored. =/ About to test this out in my windows VM and see if I get some success there; it'll at least tell me if there's something I'm missing on the Linux side.
-Dennis
-Dennis
Sorry, I made a few mistakes, apparently. You will need to get an answer from someone who has an FT-70. See this thread: http://intrepid.danplanet.com/pipermail/chirp_users/2017-October/012735.html
On Wed, Apr 3, 2019 at 10:20 PM Dan Clemmensen danclemmensen@gmail.com wrote:
that's the device ID for a pl2303. the name of the module is pl2303
execute lsmod to see if the module got loaded.
If not, sudo modprobe pl2303 to force-load the module
On Wed, Apr 3, 2019 at 10:07 PM Dennis Carr < dennisthetiger@chez-vrolet.net> wrote:
On Wed, 3 Apr 2019 21:51:05 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that would be assigned to a modem a fake modem such as an OTG-connect3d phone or something like that.
Yeah, confirmed, it's /dev/ttyACM0. Tried 'watch'ing that, but 'watch ls /dev/tty*' is kinda useless as it overflows.
on my computer, USB serial dongles get addresses like /dev/ttyUSB0
I got that as well with the Baofeng clone cable I've got, doesn't seem to be the case here.
The only other thing making me think about this a bit is the fact that 'lsusb' comes up with this:
Bus 003 Device 025: ID 26aa:001b
...that's it, no description following the devid. So my computer sees something there, it just doesn't know what it is.
...am I missing something somewhere, a kernel mod maybe?
-Dennis _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, 3 Apr 2019 22:36:26 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
Sorry, I made a few mistakes, apparently. You will need to get an answer from someone who has an FT-70.
No, you're fine, you're on the right track - but you're probably not wrong about anyone else who's had the experience.
Of note, having issues with virtualbox seeing my USB devices. I'm just gonna have to do this on my Windows box at work, methinks.
-Dennis
After sleeping on it, I'm almost certain that we made some mistaken assumptions. I think the micro-USB "data" port on the DFT-70 is really an OTG port, not an embedded pl2303 chip. This explains why your Linux box calls it /dev/ttyACM0 and instead of /dev/ttyUSB0. If this is the case, the pl2303 module is not needed at all, and it had probably been loaded when you had some other cable plugged in. To support USB OTG, your Linux box loads one of several modules whose name starts with g_ (g_serial, g_cdc, g_multi). I think the choice depends on the capabilities that the OTG device advertizes, or possibly one or more modules whose names start with cdc_ (cdc_ether, cdc_subset, cdc_eem).
you can test this theory by first removing the pl2303 module: sudo modprobe -r pl2303 and then plugging your FT-70 back in. If my theory is correct, /dev/ttyACM0 will come back into existence, but pl2303 will not reload.
On Wed, Apr 3, 2019 at 11:06 PM Dennis Carr dennisthetiger@chez-vrolet.net wrote:
On Wed, 3 Apr 2019 22:36:26 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
Sorry, I made a few mistakes, apparently. You will need to get an answer from someone who has an FT-70.
No, you're fine, you're on the right track - but you're probably not wrong about anyone else who's had the experience.
Of note, having issues with virtualbox seeing my USB devices. I'm just gonna have to do this on my Windows box at work, methinks.
-Dennis
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Thu, 4 Apr 2019 08:41:09 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
you can test this theory by first removing the pl2303 module: sudo modprobe -r pl2303 and then plugging your FT-70 back in. If my theory is correct, /dev/ttyACM0 will come back into existence, but pl2303 will not reload.
You're potentially right, and I can look at this when I get home.
In the meantime, I tested this on my windows box here at work using the latest daily build. In this case, there was a pop-up telling me the necessary steps to do this - and rather than removing the battery and leaning on DC, it had me 1) remove the battery while the radio was powered on and plugged into USB, 2) hold power and AMS, and 3) reconnect the battery. Doing it the original way in Windows had the same result as last night - but doing it *this* way got me on the path to success. So I've got two things to consider at this point. =)
More later, once I get home and have a chance to test this.
-Dennis
On Thu, 4 Apr 2019 08:41:09 -0700 Dan Clemmensen danclemmensen@gmail.com wrote:
I think the micro-USB "data" port on the DFT-70 is really an OTG port, not an embedded pl2303 chip.
OK, I think I've got it.
The g_* modules only had g_serial, but the cdc_* were all available. After removing the *2303 module and modprobing the cdc_* set, I tried again. Downloading was fine, but after powercycling I could not upload - the radio failed to ACK block 1.
After futzing with it, accidentally hard resetting the radio, and getting started again (and in fact fearing bricking the thing), I did a raw upload, loaded my new dataset that I ported over from my Baofeng, and uploaded this successfully.
This requires some testing, but we may be able to get away with *not* having to dress up as a harem girl and dance the watusi while facing north and plugging in the radio all at the same time. =D
Dan, thanks for the help and 73.
-Dennis KE7KIF
It's usually /dev/ttyUSB0
Make sure you're a member of the dialout group.
On 04 April 2019 at 00:51 Dan Clemmensen danclemmensen@gmail.com wrote:
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that would be assigned to a modem a fake modem such as an OTG-connect3d phone or something like that. Check this by first unplugging the cable from the comouter and then doing: ls /dev/tty* Then plug the cable back into the computer and repeat the command. a new device should have appeared. That's the device for your cable. on my computer, USB serial dongles get addresses like /dev/ttyUSB0 On Wed, Apr 3, 2019 at 9:35 PM Dennis Carr < dennisthetiger@chez-vrolet.net mailto:dennisthetiger@chez-vrolet.net > wrote: > > Howdy!Running a Yaesu Ft-70DR that just arrived today. First thing's first: download to Chirp! Running daily 20190221 on Debian current stable, using the builds from the website. Just one problem - it didn't download. After following instructions (battery off, DC and USB in (specifically the USB cable that came with), hold AMS key while powering on, select Download option, set the right options (/dev/ttyACM0, Yaesu FT-70D)), hit the BAND button so it says TX, and... ...no activity. It times out, radio shows ERROR. Long and short, I'm not sure if I'm doing something wrong here. So in short: * What am I missing? * What other information is needed from me to properly answer? -Dennis KE7KIF _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com mailto:danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com > _______________________________________________chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net
On Thu, 4 Apr 2019 09:08:06 -0400 (EDT) "Nigel A. Gunn G8IFF/W8IFF" nigel@ngunn.net wrote:
It's usually /dev/ttyUSB0
Not in this case, it isn't. =/
Make sure you're a member of the dialout group.
Just tested, it's good.
-Dennis
participants (3)
-
Dan Clemmensen -
Dennis Carr -
Nigel A. Gunn G8IFF/W8IFF