Project

General

Profile

Actions

Bug #11362

open

Retevis RT76P cannot change Power-On Message

Added by Ched Cuaresma 6 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/29/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Retevis RT76P
Platform:
Windows
I read the instructions above:
Yes

Description

Please find the template below:

What is the behavior you are seeing? The changes I made to the Power-On Message do not reflect on the radio upon upload.
What is the behavior you were expecting? Changes made to the Power-On Message are seen after uploading the settings to the radio.
Can you reproduce the problem all the time? Yes
What are the steps required to reproduce the problem? Download an image from the radio, make a custom Power-On Message under the Settings tab, upload the settings to the radio.
Is this specific to a certain radio model (driver) or something that you can reproduce with another radio? This is specific to the Retevis RT76P with RT76P-Firmware-20220808 (latest at the time of writing).


Files

Retevis_RT76P_20240529.img (8.18 KB) Retevis_RT76P_20240529.img Image of radio from Chirp. Ched Cuaresma, 05/29/2024 08:20 AM
Actions #1

Updated by Alexandre J. Raymond 6 months ago

I had a look at the code, and I think the issue is caused by the upload ranges:

_ranges = [
      (0x0000, 0x0820),
      (0x0C00, 0x1400),
      (0x1A00, 0x1C20),
  ]

versus the defined memory ranges:

MEMORY_FORMAT ranges:

[0x0000, 0x0800[: memory
--
[0x0C00, 0x1400[: names
--
[0x1A00, 0x1A2A[: settings
--
[0x1A80, 0x1A82[: skey
--
[0x1B00, 0x1BF0[: pttid
[0x1BF0, 0x1C10[: dtmf
--
[0x1FE0, 0x2000[: poweron_msg

The _ranges variable doesn't seem to be up to date with MEMORY_FORMAT. At the very least, it doesn't cover poweron_msg, which would explain the bug report.

Jim Unroe, any thoughts on that?

Actions

Also available in: Atom PDF