Updating DVMega Firmware on Pi 3B
Jul 30, 2016 13:42:06 GMT -7
Post by AA7US on Jul 30, 2016 13:42:06 GMT -7
Hi Bob,
I apologize in advance for asking this on your board because it's not strictly D-Star Commander related...
As you may recall, I was recently able to update the firmware on my dual-band DVMega to eliminate a problem where the G4KLX D-Star Repeater software wouldn't see the DVMega board after cold-booting the Pi. To do the firmware update I used an older model B Pi which I had laying around.
At first I had trouble getting the avrdude programming software to communicate with the DVMega, but ultimately I found there was a getty process running and accessing the ttyAMA0 port, thus preventing avrdude from gaining exclusive access to that port for the firmware update. Once I prevented that getty process from starting up at boot, avrdude ran perfectly. Problem solved!
So now I'm trying to assist a fellow ham who's also having the same cold-boot problem with his dual-band DVMega (I know... blind leading the blind). In his case he'll be using Pi 3B for the firmware update because that's what he has. In trying to document the specific steps he'll need for the update, I'm trying it out on my own Pi 3B first which is running D-Star Commander 2.01. Unfortunately I'm encountering the EXACT same behavior I'd initially run into on my old model B Pi, where avrdude seeming can't access the /ttyAMA0 port. Of course I quit both the G4KLX D-Star Repeater and Gateway software before attempting to run avrdude.
Some Googling suggested maybe the Pi 3B's built-in Bluetooth and remapping of the GPIO pins could be the culprit. So I tried killing and preventing Bluetooth from running with the following commands:
sudo systemctl disable bluetooth
sudo systemctl disable hciuart
sudo systemctl stop bluetooth
sudo systemctl stop hciuart
I see the /boot/config.txt file has this at the very end to prevent remapping of the GPIO ports by Bluetooth...
#disable reassignment of GPIO pins 14/15 to miniUART (disables bluetooth on pi3)
dtoverlay=pi3-miniuart-bt
I found a website which suggested using the following line in the config.txt file:
dtoverlay=pi3-disable-bt
I tried using both separately, but I still haven't been able to get avrdude to communicate with the DVMega board.
I've also tried adjusting the baud rate avrdude uses to communicate with the DVMega board... no luck.
So my question to you Bob is this: Can you think of anything else I should look at to get avrdude to communicate with the DVMega board on a Pi 3B?
Thanks and 73,
John
AA7US
I apologize in advance for asking this on your board because it's not strictly D-Star Commander related...
As you may recall, I was recently able to update the firmware on my dual-band DVMega to eliminate a problem where the G4KLX D-Star Repeater software wouldn't see the DVMega board after cold-booting the Pi. To do the firmware update I used an older model B Pi which I had laying around.
At first I had trouble getting the avrdude programming software to communicate with the DVMega, but ultimately I found there was a getty process running and accessing the ttyAMA0 port, thus preventing avrdude from gaining exclusive access to that port for the firmware update. Once I prevented that getty process from starting up at boot, avrdude ran perfectly. Problem solved!
So now I'm trying to assist a fellow ham who's also having the same cold-boot problem with his dual-band DVMega (I know... blind leading the blind). In his case he'll be using Pi 3B for the firmware update because that's what he has. In trying to document the specific steps he'll need for the update, I'm trying it out on my own Pi 3B first which is running D-Star Commander 2.01. Unfortunately I'm encountering the EXACT same behavior I'd initially run into on my old model B Pi, where avrdude seeming can't access the /ttyAMA0 port. Of course I quit both the G4KLX D-Star Repeater and Gateway software before attempting to run avrdude.
Some Googling suggested maybe the Pi 3B's built-in Bluetooth and remapping of the GPIO pins could be the culprit. So I tried killing and preventing Bluetooth from running with the following commands:
sudo systemctl disable bluetooth
sudo systemctl disable hciuart
sudo systemctl stop bluetooth
sudo systemctl stop hciuart
I see the /boot/config.txt file has this at the very end to prevent remapping of the GPIO ports by Bluetooth...
#disable reassignment of GPIO pins 14/15 to miniUART (disables bluetooth on pi3)
dtoverlay=pi3-miniuart-bt
I found a website which suggested using the following line in the config.txt file:
dtoverlay=pi3-disable-bt
I tried using both separately, but I still haven't been able to get avrdude to communicate with the DVMega board.
I've also tried adjusting the baud rate avrdude uses to communicate with the DVMega board... no luck.
So my question to you Bob is this: Can you think of anything else I should look at to get avrdude to communicate with the DVMega board on a Pi 3B?
Thanks and 73,
John
AA7US