this throws me a Linux flasher, after connecting the DM1801 it dedicates it and programs the FW, but like the others OK I have a problem with CPS not working.
....../openGD77_for_DM1801> mono FirmwareLoader-Linux.exe
Device Not Found [0x15a2:0x0073].
Error. Can't connect the transceiver
Unable to detect HT model, using GD-77 as fallback.
(process:7164): Gtk-WARNING **: 16:57:13.858: Locale not supported by C library.
Using the fallback 'C' locale.
picture:
https://drive.google.com/open?id=1TIECs ... GSR8YGrL1M
-----------------------------------------------
the problem may also be in the identification,
run mode DM1801
lsusb
> Bus 003 Device 008: ID
1fc9:0094 NXP Semiconductors
flash mode DM1801 (prg.key1 + prg.key2 + ON power = light green LED)
lsusb
> Bus 003 Device 011: ID
15a2:0073 Freescale Semiconductor, Inc.
when e.g.
dmrconfig has id specified in rules:
file 99-dmr.rules
# TYT MD-UV380
SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", MODE="666"
# Baofeng RD-5R, TD-5R, DM-1801
SUBSYSTEM=="usb", ATTRS{idVendor}=="
15a2", ATTRS{idProduct}=="
0073", MODE="666"
# Anytone AT-D868UV: ignore this device in Modem Manager
ATTRS{idVendor}=="28e9" ATTRS{idProduct}=="018a", ENV{ID_MM_DEVICE_IGNORE}="1"
==================================================
( install
mono-complete (
sudo zypper install mono-complete)
after
cd <where the rules file is located>
sudo cp 99-gd77.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules)
file 99-gd77.rules :
# USB rules for GD-77
# Place this in /etc/udev/rules.d/ to let all users talk to the radios by USB.
#
SUBSYSTEM=="usb", ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0073", MODE="0666", GROUP="plugdev"
# HIDAPI/libusb
SUBSYSTEM=="usb", ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0073", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0094", MODE="0666", GROUP="plugdev"
# HIDAPI/hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0073", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0094", MODE="0666", GROUP="plugdev"
# HIDAPI/hiddev
## We need to unbind this device, otherwise LibUsb will fail to SetConfiguration() and ClaimInterface()
# For Bootloader (usbhid)
KERNEL=="hiddev*", ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0073", MODE="0666", GROUP="plugdev", RUN+="/bin/bash -c 'ID=$(IFS=/; read -a array <<< %p; echo ${array[-3]}); echo $ID > /sys/bus/usb/drivers/usbhid/unbind'"
# OpenGD77
KERNEL=="ttyACM[0-9]*", SUBSYSTEM=="tty", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0094", MODE="0666", GROUP="dialout", SYMLINK+="OpenGD77"
==================================================
edit 2.5.2020
I removed the error message at
mono FirmwareLoader-Linux.exe
(process:7164): Gtk-WARNING **: 16:57:13.858: Locale not supported by C library.
Using the fallback 'C' locale.
I just threw in English in the locale
sudo nano /etc/environment
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
LANG="en_US.UTF-8"
LC_MESSAGES="C"
LC_ALL="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
which confirms a programmer's mistake in not treating various language mutations.
=============================================
dmrconfig malfunction partially solved, after connecting
UV380 dmrconfig also did not see TRX, I used
sudo /..whole path../dmrconfig -r -t and
dmrconfig has already seen and loaded
UV380,
ie I have the wrong user rights somewhere. (I used it all the way because I don't have dmrconfig stored in / usr / ... and sudo doesn't see it then)
unfortunately
DM1801 with
openGD77 dmrconfig still can't see (I shuffle the cables and I always have the correct USB cable attached to each TRX)
=================================
reason for
dmrconfig functionality with
openGD77 FW revealed. I found a post that explains everything, communication of
openGD77 takes place through a different channel than communication with the original FW
DM1801.
Although I tried to modify radio.c, I did not get a satisfactory result, although the communication after changing the device identification to 1fc9:0094 took place on the serial channel /dev /ttyACM0, and ..hid change to ...serial, but the device responses were not correct, ie the device did not identify them.
// Try TYT MD family.
ident = dfu_init(0x0483, 0xdf11);
if (! ident) {
// Try RD-5R, DM-1801 and GD-77.
//
if (hid_init(0x15a2, 0x0073) >= 0)
//
ident = hid_identify();
if (serial_init(0x1fc9, 0x0094) >= 0)
ident = serial_identify();
}
rogerclarkmelbourne commented on this issue 4 months ago.
@tylert
Sorry...
I don't have any personal experience using dmrconfig , I was just passing on an issue that someone else contacted me about, when using the OpenGD77 firmware and DMRConfig.
I think they were just using DMRConfig to export and import from CSV, because the OpenGD77 firmware uses a different protocol to upload and download from the radio, using USB Serial rather than USB HID.
POST A BOUNTY
Be the first to post a bounty for this issue!
Are you a developer who can solve this issue?
About Team
dmrconfig
Configuration utility for DMR radios
See More
This team needs your support!