Bootstrapping D013.020

[aeickho]

build and flash the D013.020 with make flash_ng

Supported Hardware

• Tytera/TYT MD380 (old vocoder)
• Tytera/TYT MD380 (new vocoder)
• Tytera/TYT MD390 (new vocoder, no gps)
• Retevis RT3

md380-gfx is not modified for D13.20 ... Own start up logo is temporary not possible

Close this issue when the firmware boots with the following features:

• USB communications
• Startup demo
• Promiscuous (monitor mode), see D13.020 - promiscuous-mode does not work #222
• Menu items
• Menu no exit on rx
• Caller ID. (users.csv)
• Color Code patch on patch.py
• adjust beep tones frequency
• 1750 Hz relay open tone, only with programmed sidebutton CPS 1.32
• check new DMESG_START address
• corr boot logo patcher (md380-gfx )
• Monitor Mode "Eye", with old bad hook ;)
• Edit DMRid
• switch to D013.020 as default
• Proper booting on GPS devices. --> MD390 GPS D13.020 - White screen only after welcome screen #226

[iball]

@aeickho FYI: I've flashed this to both my MD-380 and MD-390-no-GPS.
Let me know if there's anything I can test out for you.

[aeickho]

Some notes /todos:
..................
sapplet.getadr("dmr_apply_squelch_hook"),0);
merger.hookbl(0x0804105a, sapplet.getadr("dmr_apply_squelch_hook"),0);

• check monitor mode

..........
#These aren't quite enough to skip the Color Code check
in patch.py

• add Color Code patch to d13.020_patch.py

........
beep tone setup has been changed

• adjust beep tones

........
movement from applet/src/dmesg.h
DMESG_START from 0x2001d500 to 0x2001f700

• hopefuly free ... please check stability

.....
applet/src/usb.c

• add nicer variable names

......
../../md380-gfx --firmware=patched.img --gfx=0x80f9ca8-troopers-color.ppm relocate and write
don't work with d13.020

• look for the problem (img location) OR add an new bmp with ppm2h.py

........
travis test, temponary all tests in all cases: green

• better tests

.....
applet/src/rtc_timer.c
MD380_FONT_SMALL + MD380_FONT_NORM

• move to symbols_

....
reformat symbols_d13.020

• synced with d02.032

...
micbargraph screen update not ok

.....
monitor mode "eye" screenupdate not ok

.....
@travisgoodspeed tnx for your tool symgrate
...
30h working hours - ( pull requst #217)
..
This Issure can be closed, when D013.020 is default

[travisgoodspeed]

The color code is enforced both by firmware and by the C5000 baseband chip, so I'm cutting that as a requirement for closing this issue.

[aeickho]

@travisgoodspeed can you check the monitor mode patch please? I have no test environment ready...

[aeickho]

@travisgoodspeed "check new DMESG_START address" is only a wish - that somebody is confirming my view. Please look at this.

[aeickho]

check new DMESG_START address ... radio is working fine ... Ram address ok :)

[aeickho]

On the md380 main directory
make clean
make flash_ng

• Alex

Tnx for testing

Am 26. August 2016 11:06:37 MESZ, schrieb "Sören Kornetzki" [email protected]:

I would like to test this firmware on my MD380 (old vocoder). How do I
produce the "md380tools-XXXX-XX-XX" directory structure using the
D013.020 release (since it is not the default)?

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#218 (comment)

[DL9LBG]

Not only the beep tones are too deep in frequency (which doesn't matter much to me) but also the 1750 Hz tone for european FM repeaters (assigned to the side buttons in CPS 1.32) is much too low (I think about 800 Hz or so).

73s de Michael DL9LBG

[aeickho]

Hi Sören,
I'm unsure if I understand your mail correct.

Correct is: the displaying of promiscuous symbol is not good yet, I have found I'm recent months not a good position to call the drawing functions. No update after some moments. But this has no problems with the radio functionality.

I draw the promiscuous symbol on the ant symbol drawing.

Have you problems with the radio ..."cannot connect to relay" I have no idea what you mean.... Please recheck it with promiscuous mode off ... Maybe side effect from #222

Tnx for your assistance
Alex

[aeickho]

Hy Michael, The radio has an 1750 beep tone now .. nice ... Tnx for reporting ...

Please send me a link with the code plug programm for the cps 1.32... I have only 1.30 code plugs.....

I'll correct the frequency for release date.

Alex

[DL9LBG]

Hello Alex!

CPS 1.32 for RT3 is available at Retevis' download site -> http://www.retevis.com/material/programming_software/RT3_programming_software.zip

At the bottom of the dropdown list of functions to assign to the sidebuttons you'll find "1750 Hz". Supported with the new stock firmwares from July.

73 - Michael DL9LBG

P.S.: Also the new CPS for RT8 contains the 1750 Hz tone.

[aeickho]

Michael, tnx my radio has now a 1750Hz sidebutton with ≈ 700 Hz...I'm going to search now

[aeickho]

With 123a910 ... 1750Hz tone is working again

[DL9LBG]

Great work - tnx Alex!

[travisgoodspeed]

On my device with GPS, the image boots to a blank white screen, but USB is still functioning properly. Perhaps the rtc_timer task that manages the LCD is getting stuck somewhere?

Should we add GPS support to the requirements, or close this issue and open another for bootstrapping S013.020? (If at all possible, I'd like to merge all four of Tytera's branches back to a single firmware image that runs on all hardware.)

[travisgoodspeed]

Added GPS target, and pushed core dumps to /cores/ in the repo.

[aeickho]

I'll bootstrapping S013.020 this week. I think this is a straightforward job.
... but i have no radio with gps :( so I have to work error free.

The steps, as I imagine it

• add usb
• Ram Dump to check memory @ DMESG_START is free
• Port other additions

Then we can compare the too firmwares.
Yes only one version is nicely. I think ... S13.020 is a good candidate!

-> now we talk about the S13.020 on #181

[HB9TQJ]

If I try to make flash_ng it does not work:
root@inspiron6000:~/md380tools# make flash_ng
make: *** No rule to make target 'flash_ng'. Schluss.
How can I flash the new Firmware? If I do make all flash it looks likes it uses old FW.

[HB9TQJ]

I forgot to do git pull. Now it works.

[travisgoodspeed]

I'm standing by with GPS hardware for testing, but a more urgent priority might be fixing #226, where D013.020 refuses to boot on GPS devices.

Alternately, we might try to get S013.020 booting on the non-GPS devices.