Project

General

Profile

Actions

Bug #10251

open

Yaesu FTM-7250DR

Added by Terry Palmatier almost 2 years ago. Updated about 1 month ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/09/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next (py3)
Model affected:
Yaesu FTM-7250DR
Platform:
Windows
Debug Log:
I read the instructions above:

Description

This is the same issue as before. At the end of the cloning process I get the following error: Checksum failed [064A-06CB(@06C9)]


Files

debug.log (193 KB) debug.log Terry Palmatier, 01/09/2023 09:21 PM
ftm7250d.py (6.66 KB) ftm7250d.py UNSAFE FOR UPLOAD test driver Dan Smith, 01/12/2023 12:03 AM
Yaesu_FTM-7250D_20230111.img (63.9 KB) Yaesu_FTM-7250D_20230111.img Terry Palmatier, 01/12/2023 01:47 AM
Yaesu FTM-7250DR file.tab (2.7 KB) Yaesu FTM-7250DR file.tab Terry Palmatier, 01/12/2023 02:23 AM
chirp.log (189 KB) chirp.log Debug log reading from FTM-7250D Matt Foster, 01/13/2023 07:07 PM
debug.log (10.7 KB) debug.log Joe Polcari, 09/28/2024 08:26 PM

Related issues 1 (1 open0 closed)

Has duplicate Bug #9327: Yaesu FTM-7250DFeedback08/28/2021

Actions
Actions #1

Updated by Dan Smith almost 2 years ago

  • Status changed from New to Feedback

Hi Terry.. what "same issue as before" are you talking about? Do you have another bug to reference?

That looks like a legit checksum error, in that the code is doing what it is supposed to, although I'm assuming it's a false positive based on your comment. If there's more context to read, let me know. I don't have or have access to one of these radios, so there's probably not much I can do to resolve it without that. We could try reaching out to the original author of that driver.

Actions #2

Updated by Dan Smith almost 2 years ago

  • Has duplicate Bug #9327: Yaesu FTM-7250D added
Actions #3

Updated by Dan Smith almost 2 years ago

Ah, I see you have another one already reported. Normally I would close this one as a duplicate of that, but the debug logs attached to the original issue have no error information in them but yours attached to this one does.

I'm adding the original author of that (sub-)driver to this issue, so maybe he will have some ideas.

@Iain White ?

Actions #4

Updated by Dan Smith almost 2 years ago

Terry,

Can you load the attached module and try to do a download with it? The module disables the checksum checking purely so you can try to get an image, save it, and attach it to this bug for me to look at. Don't use this to upload as it could push bad data into your radio, if the checksums are really failing for legit reasons.

Also, if you could tell me what kind of cable/usb adapter you're using that would be helpful. Can you download the radio using any other software, like Yaesu's using the same cable?

Actions #5

Updated by Terry Palmatier almost 2 years ago

I don't know how to load the attached module to make this test.

But, I can tell you I am using a USB-29F cable. Also, I can download to Yaesu's programming software with this cable.

Terry, AC8NR

Actions #6

Updated by Dan Smith almost 2 years ago

In the Help menu, enable Developer Mode. Restart chirp and then the File menu will have a Load Module function. Run that, choose this file. It's only active until you restart chirp.

Actions #7

Updated by Terry Palmatier almost 2 years ago

Dan Smith wrote in #note-6:

In the Help menu, enable Developer Mode. Restart chirp and then the File menu will have a Load Module function. Run that, choose this file. It's only active until you restart chirp.

OK that worked, a little. What it downloaded isn't exactly what is programmed into the radio. I've attached a copy of what I downloaded.

Actions #8

Updated by Dan Smith almost 2 years ago

Great, thanks. Can you describe a little about what you mean by "isn't exactly what is programmed into the radio"?

Based on that, however, I'm guessing I won't be able to do anything without access to a radio, but it's a start. I'll take a look later.

In case it matters, have you applied any firmware updates and/or does the radio show you a firmware version?

Actions #9

Updated by Dan Smith almost 2 years ago

Oh jeez, I just loaded up the image and .. I see. Definitely don't upload that back to your radio. Something is very wrong there, so someone with access to a radio will definitely need to do some debug on that. Thanks for the data here though, it should provide a good start.

Actions #10

Updated by Terry Palmatier almost 2 years ago

Dan Smith wrote in #note-9:

Oh jeez, I just loaded up the image and .. I see. Definitely don't upload that back to your radio. Something is very wrong there, so someone with access to a radio will definitely need to do some debug on that. Thanks for the data here though, it should provide a good start.

Cool beans. As far as I know the firmware has never been upgraded. The radio was discontinued soon after it came out. I will attempt to send a copy of the programmed file with this reply.

Terry, AC8NR

Actions #11

Updated by Matt Foster almost 2 years ago

I'm also getting the checksum error on my 7250. Attaching debug log...

Actions #12

Updated by Joe Polcari about 1 month ago

I have the same issue

Actions #13

Updated by Joe Polcari about 1 month ago

Here's my debug.log

Actions #14

Updated by Joe Polcari about 1 month ago

I'm also using the 29F USB cable and the Yaesu software reads and writes just fine using this cable.

Actions

Also available in: Atom PDF