Project

General

Profile

Actions
Copy link

Bug #314

closed

UV5R Firmware BFB291

Added by Danny Ozbirn about 12 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Dan Smith
Category:
-
Target version:
0.3.0
Start date:
09/30/2012
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5R
Platform:
All
Debug Log:
I read the instructions above:

Description

The New Firmware BFB291 Is not working with the current build of CHIRP They have a new version of the software which works with the Newer Firmware . It looks like Separate software will be required by all units with BFB291 Firmware and Newer

Files

Download all files
BFB291.dat (37.7 KB) BFB291.dat BFB291 DAT FILE Danny Ozbirn, 10/01/2012 09:25 PM
error1.jpg (7.96 KB) error1.jpg ERROR1 Danny Ozbirn, 10/02/2012 08:53 AM
debug.log (3.75 KB) debug.log Danny Ozbirn, 10/02/2012 09:42 AM
debug2.log (3.76 KB) debug2.log Danny Ozbirn, 10/02/2012 10:23 AM
debug3.log (5.59 KB) debug3.log debug3.log Danny Ozbirn, 10/02/2012 10:56 AM
debug4.log (2.96 KB) debug4.log debug4.log Danny Ozbirn, 10/02/2012 11:34 AM
debug4b.log (4.44 KB) debug4b.log Danny Ozbirn, 10/02/2012 12:10 PM
debug5.log (3.58 KB) debug5.log Danny Ozbirn, 10/02/2012 02:57 PM
BFB291.img (6.32 KB) BFB291.img Danny Ozbirn, 10/02/2012 02:58 PM
debugU1.log (5.06 KB) debugU1.log Danny Ozbirn, 10/02/2012 03:34 PM
debug6.log (4.05 KB) debug6.log Danny Ozbirn, 10/02/2012 04:38 PM
BFB291-2.img (6.32 KB) BFB291-2.img Danny Ozbirn, 10/02/2012 04:39 PM
BFB291good.img (6.32 KB) BFB291good.img BFB291 Good Danny Ozbirn, 10/02/2012 07:33 PM
debug.dl2olk.log (5.89 KB) debug.dl2olk.log Lars Komm, 10/05/2012 09:07 AM
debug.log (4.49 KB) debug.log John Buck, 10/05/2012 01:25 PM
debug20121005.log (3.78 KB) debug20121005.log Debug log from 20121005 - Radio = MTC UV-E5 John LaMartina, 10/05/2012 04:35 PM
debug.log (3.64 KB) debug.log debug log uv-5r 20121007 Alex Simpson, 10/09/2012 09:44 PM
debug1007.log (5.79 KB) debug1007.log Danny Ozbirn, 10/10/2012 05:49 PM
debug1007-291.log (3.57 KB) debug1007-291.log Danny Ozbirn, 10/10/2012 06:04 PM
debug.v201210007.date-20121011,001.log (4.19 KB) debug.v201210007.date-20121011,001.log Ali al-Azzawi, 10/11/2012 01:36 PM
debug.v201210012.date-20121012.001.log (4.33 KB) debug.v201210012.date-20121012.001.log Ali al-Azzawi, 10/12/2012 01:48 PM
debug291nr1.log (3.65 KB) debug291nr1.log This one did not work Danny Ozbirn, 10/12/2012 09:18 PM
debug291or1.log (3.57 KB) debug291or1.log This one did work Danny Ozbirn, 10/12/2012 09:21 PM
debug.log (2.88 KB) debug.log Debug Log BFB291 John LaMartina, 10/13/2012 04:52 AM
debug.v201210013.date-20121013.001.log (4.05 KB) debug.v201210013.date-20121013.001.log Ali al-Azzawi, 10/13/2012 09:06 AM
debug_v20121013_uv5r_bfb291.log (3.74 KB) debug_v20121013_uv5r_bfb291.log Alex Simpson, 10/13/2012 02:47 PM
debug1019.log (4.81 KB) debug1019.log Danny Ozbirn, 10/22/2012 01:57 PM
debug10192.log (4.42 KB) debug10192.log Danny Ozbirn, 10/22/2012 06:22 PM
Actions
Copy link
 #1

Updated by Dan Smith about 12 years ago

  • Assignee set to Dan Smith
  • Model affected changed from UV5R BFB291 to UV5R

Can you get any amount of an image if you try to download with CHIRP? If so, please attach it here. Also, please attach a debug log of the attempt (regardless of if successful).

FYI, tomorrow's daily build will check for the firmware version and fail if it's >=291 just to limit any confusion and potential damage until we know further.

Actions
Copy link
 #2

Updated by Danny Ozbirn about 12 years ago

Hello Dan,

The new firmware model will not communicate with the legacy Baofeng software or the last CHIRP daily bill. Baofeng has a new version of their software that will only read and write the new BFB291 firmware version. I'm uploading you a copy of it's dat file.

Thanks.

Dan Ozbirn

Actions
Copy link
 #3

Updated by Dan Smith about 12 years ago

Yes, I understand. Thanks, but the .dat files are useless for this :)

Actions
Copy link
 #4

Updated by Danny Ozbirn about 12 years ago

The Test version GTK 2.24.10 PyGTK 2.24.0 Python 2.7.2 Oct 2 2012 Got a reply from the Radio This time Got an Error Unknown Vender (see File Error1.jpg)

Sorry About that dat file it was the only horse i had in the barn 8)

Actions
Copy link
 #5

Updated by Dan Smith about 12 years ago

Okay thanks, but I need the debug.log!

See How_to_report_issues

Actions
Copy link
 #6

Updated by Danny Ozbirn about 12 years ago

Sorry About That Dan I found the Log here it is YOU get slow when you get old

Actions
Copy link
 #7

Updated by Dan Smith about 12 years ago

Added a 291test2 build. Please test and report.

Thanks!

Actions
Copy link
 #8

Updated by Danny Ozbirn about 12 years ago

Test 2 CHIRP 291test2 GTK 2.24.10 PyGTK 2.24.0 Python 2.7.2 Radio Led Blinked 1 time ERROR Radio reported unknown vendor Debug2.log attached

Actions
Copy link
 #9

Updated by Dan Smith about 12 years ago

Sorry, test2 didn't get the changes integrated that I intended. Please ignore and retry with test3 :)

Actions
Copy link
 #10

Updated by Danny Ozbirn about 12 years ago

Test 3 CHIRP 291test3 GTK 2.24.10 PyGTK 2.24.0 Python 2.7.2 The Radio Led Blinked 1 time ERROR Radio reported invalid version string debug3.log attached

Actions
Copy link
 #11

Updated by Dan Smith about 12 years ago

Now we're getting somewhere. Please repeat with test4.

Thanks!

Actions
Copy link
 #12

Updated by Danny Ozbirn about 12 years ago

Test 4 CHIRP 291test4 GTK 2.24.10 PyGTK 2.24.0 Python 2.7.2 Radio Led blinked several times Got ERROR Value 255 not in range 0-9 No Channel information was displayed debug4.log added

Actions
Copy link
 #13

Updated by Dan Smith about 12 years ago

Looks like you might've closed and reopened chirp after doing the download as the debug log is almost empty. Is that right? If so, could you re-snag it?

Making progress...Thanks!

Actions
Copy link
 #14

Updated by Danny Ozbirn about 12 years ago

Resnage of Test 4 debug4b.log added

Actions
Copy link
 #15

Updated by Dan Smith about 12 years ago

Okay, thanks. test5 posted. I just hacked out the settings bit, which is where it was choking. Hopefully this will get you to a memory editor after the download (with probably garbage-looking data), at least enough to save out the .img.

Actions
Copy link
 #16

Updated by Danny Ozbirn about 12 years ago

Test 5 Got am img file this time it looks pretty good the offsets on ch 2 and 4 are wrong but looks pretty good i am adding it to the files and will add the debug log too

Actions
Copy link
 #17

Updated by Danny Ozbirn about 12 years ago

Actions
Copy link
 #18

Updated by Dan Smith about 12 years ago

Okay, great! Better than I expected. Are you willing to try an upload at this point? I think the risk is quite low that anything will be problematic or irreversible, but there's always a risk. If so, that's the next thing I'd like to try, but will require me to spin another one.

Actions
Copy link
 #19

Updated by Danny Ozbirn about 12 years ago

H Have a back up saved on there software so i am game i will try an upload

Actions
Copy link
 #20

Updated by Danny Ozbirn about 12 years ago

Could not upload adding debugU1.log no led flash and no upload

Actions
Copy link
 #21

Updated by Dan Smith about 12 years ago

Right, I haven't written the upload bit yet :)

Coming in a few minutes, stand by...

Actions
Copy link
 #22

Updated by Dan Smith about 12 years ago

Okay, test6 is up with potential upload capability.

Actions
Copy link
 #23

Updated by Danny Ozbirn about 12 years ago

Test 6 WAS able to up load and download alright Non standard offsets are a little buggy but every thing else seems to be alright when i run across a non standard offset i will not download but i was able to upload it standard ham band offsets are working ok

Actions
Copy link
 #25

Updated by Dan Smith about 12 years ago

Okay, great news! Can you tell me what the offsets are supposed to be for channels 2 and 4 in the image you sent?

Actions
Copy link
 #26

Updated by Danny Ozbirn about 12 years ago

Memory 2 should have been a + 2.88 Offset

Memory 4 should have been a - 3.625 Offset

Actions
Copy link
 #27

Updated by Danny Ozbirn about 12 years ago

The Offset Problem could have been a Bad programing of the radio after reprogramming it and downloading it is ok see the image I added

Actions
Copy link
 #28

Updated by Dan Smith about 12 years ago

Okay, excellent. I sounds like you've done multiple downloads and uploads at this point, modified the image, etc without any trouble, is that right? If so, I think it might be good to go ahead and push what we have into the daily builds to see how it works for the masses.

What do you think?

Actions
Copy link
 #29

Updated by Danny Ozbirn about 12 years ago

I have rolled it around pretty good and it seems like it is good for a run in the daily build I think it will do ok there are getting to be several BFB291 Radios out there so give it a try

Actions
Copy link
 #30

Updated by Lars Komm about 12 years ago

Hi folks,

I will attach here as I might be of help here.
I installed the latest daily build and got the same what Danny had before. Radio reports unknown vendor.
Debug info attached.

Greets, Lars

Actions
Copy link
 #31

Updated by morgan r about 12 years ago

win7
prolific 3.2.0.0

purchased UV-5RE model with BFB291 from 409shop. Using generic usb cable and driver I attempted to download from the radio and got the following errors:

daily 10/3
"Radio did not respond"

daily 10/5
after 4 seconds a quick red led blink and screen goes to purple
"Radio reported unknown vendor"
so it appears there is some communication?

has anyone gotten a UV-5RE to work with Chirp?

thanks,

Actions
Copy link
 #32

Updated by Shawn Somers about 12 years ago

It appears that there is another variant that uses 6t instead of DH as part of the vendor string.

Actions
Copy link
 #33

Updated by John Buck about 12 years ago

Just to back up what Morgan and Shawn reported.

My Baofeng UV-5R received from 409shop.com isn't recognized by the daily build of CHIRP. I had the exact same experience as Morgan R.

I pulled this from the debug log:

Vendor is '6t\x04', expected ('DH\x04', '\x00\x04y')
Radio reported unknown vendor

Actions
Copy link
 #34

Updated by John LaMartina about 12 years ago

Same with the UV-E5

Vendor is '6t\x04', expected ('DH\x04', '\x00\x04y')
Radio reported unknown vendor

debug log from 20121005 attached

Actions
Copy link
 #35

Updated by Alex Simpson about 12 years ago

another log for the uv-5r hopefully its helpful,
Thanks
Alex

Actions
Copy link
 #36

Updated by Alex Simpson about 12 years ago

Also to clarify this is a BFB291 with a generic usb cable (Prolific clone).
Alex Simpson wrote:

another log for the uv-5r hopefully its helpful,
Thanks
Alex

Actions
Copy link
 #37

Updated by Danny Ozbirn about 12 years ago

Tried downloading a BFB291 and BFB251 radio with the October 7 build Both work Added is the debug log from the BFB251 for reference My internet was down from Friday night to yesterday Starting to catch up thanks four you good work

Actions
Copy link
 #39

Updated by Ali al-Azzawi about 12 years ago

I've got a UV-5R, just bought it, and it report BFB291. Attached is the debug log running, chirp-daily-20121007.

Actions
Copy link
 #40

Updated by Ali al-Azzawi about 12 years ago

Using a UV-5R (reports BFB291). Attached is the debug log running, chirp-daily-20121012.

Actions
Copy link
 #41

Updated by Dan Smith about 12 years ago

Doh! The change I made yesterday was not the one I intended. Please try tomorrow's daily and let me know.

Thanks!

Actions
Copy link
 #42

Updated by Danny Ozbirn about 12 years ago

Try ed 2 different radios one would upload the other would not

Added both debug files both radios BFB291 Firmware

Actions
Copy link
 #43

Updated by Danny Ozbirn about 12 years ago

I am starting to think some these newer firm ware radios may have io problems

Actions
Copy link
 #44

Updated by John LaMartina about 12 years ago

Getting Closer... Daily Build 20121013
Test run with UV5R BFB231 and UV-E5 BFB291.

.
Upload/Download works great with both radios with no problem.
.
However, the saved .img file from the BFB231 unit will not upload to the BFB291 unit.
The image files are not transferable betreen the two.
.
Log file from BFB291 unit after uload attemp attached.
John K3NXU

Actions
Copy link
 #45

Updated by Ali al-Azzawi about 12 years ago

Good result! ... log attached

Using a UV-5R (reports BFB291). Attached is the debug log running, chirp-daily-20121013.

Upload/download seems to work. Made some changes on channel listing, and seen the change work on the actual radio,

I've not done anything more ambitious than this, as I'm new to this radio. However, looking forward to doing things like extending the frequency range, as I'd like to Rx on airband.

Thanks for the good work.

Ali - M0PSI

Actions
Copy link
 #46

Updated by Alex Simpson about 12 years ago

Upload and download seems to work well with 20120113. Attached is the debug log. Running uv5r, BFB291.
Thanks,
Alex
VA3GAZ

Actions
Copy link
 #47

Updated by Danny Ozbirn about 12 years ago

radio would not download with this version

added debug log

Actions
Copy link
 #48

Updated by Danny Ozbirn about 12 years ago

The Last debug log may have been due to a usb problem this one has a missing block

Actions
Copy link
 #49

Updated by Dan Smith about 12 years ago

  • Status changed from New to Closed
  • Target version set to 0.3.0
  • Platform changed from Windows to All

As of r1758, settings support should be restored for the newer firmware. I'm going to close this as done and we can open new bugs for additional issues as appropriate.

Actions
Copy link
 #50

Updated by mert akça almost 3 years ago

ben anlamamak bunları hangi klasöre atmak? video ile öğretsenize lütfen.ben var sıfır bilgi.

Actions
Copy link
 #51

Updated by Bernhard Hailer almost 3 years ago

  • Model affected changed from UV5R to Baofeng UV-5R

Neyi kastettiğinden emin değilim?
I'm not sure what you are referring to?

Actions
Copy link

Also available in: Atom PDF

Copyright 2023 CHIRP Software LLC