-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootstrapping S013.020 #181
Comments
…o we can disable their symbol requirements when porting to a new target. #181
We will maintain support for old and new vocoder hardware as well as both GPS and non-GPS devices. S013.020 was chosen for this issue because it is the most different from 2.032, and by targeting it we will hopefully be able to link against all firmware revisions and targeting all hardware revisions. |
the header of the "S" Type radios is changed ...
the "xor" is the same as the "D" Version temporary --unwrap and then --wrap makes different version of the encrypted file. |
I think ... this is not a problem ... @cr can you confirm that? |
I have an report ... from a md390, old vocoder, with gps user |
I start to generate symbols_s13.020 with d13.020 as gold -> lot of matchs |
|
I noticed one bug: If I assign 1750 Hz Tone to one button the secondary function (long or short press) does not work. |
I think that I'm finish with the port on s13.020 in some days. |
@HB9TQJ ... Please open a new issue. ... Than I I'll label it with "bug on original s13.020 fw " |
---- first test version now ... 4fdd675
flash please with @ all: please report ... i have no gps type radio to test |
UPDATE: S13.020 port is finished now. but not tested yet. It works hopefully on the flowing radios:
|
make flash_S13.020 works for my md390 with old vocoder with GPS (original firmware s003.012) |
Just a short rough test, but s13.020 seems to run fine on my MD-380G. |
CAN CONFIRM: Tested here, seems to work as it should! Great work! Only thing that I could think of would be the welcome logo. The M. Rogerbeep is slightly higher pitched, I can see if I can do a demo video here. I will check for bugs and report back. |
https://youtu.be/yVnGagVu3W8 1st is D002.032 > S013.020 The S013.020 firmware sounds slightly higher pitched, also on D002.032 the M.RogerBeep setting also affects other sounds which, in my opinion, sounds better. |
Can we say: that the "S" Version is supported yet? Doku moved to #292 |
I would definitely say that the S013.020 build is stable enough to pass, I have not bumped into any problems. I got two MD390 GPS both running this firmware without problems. The GPS seems to work as it should too, tested both GPS Info and ViewGPS (from other radio)! |
@bendikz Since you have a GPS radio handy, could you please check the features listed at the top of this issue? I think that only the startup demo is still broken, but I'd like to know for sure. |
I have conducted some more tests and you are right @travisgoodspeed. I have attempted to look into the boot logo as well however they have done something different with the newer versions.. It seems like that USB Comms does not work 100% yet. I attempted to interpret the call log with md380-tool but nothing showed up (the radio interfaced with PC, showed up "Hooking calls!". Other features such as flashing firmware and csv and dmesg worked. This test was done on a 64 bit computer running Ubuntu 16.04 (latest LTS).
|
That is likely it. I got a timeout error when I attempted to hook the call log, see http://pastebin.com/pnLET9Xb. This appeared after CTRL-C interrupting. |
my md 380 g (with gps) has arrived. so i can test it. @sijskes there are important things that I should transfer from "merge_d13.020" to merge_s13.020? I do not think so... |
@aeickho if you can:
|
Dmesgtail stops the menu task. Menu, channel switch and power off is not working. I have a ram dump to the spi flash with inactive USB hooks and Our USB transfer ram ... I think is it unused .. I dump ram to flash 5 sec after power on Tomorrow .. I'll create an now issue for this problem |
@aeickho i've merged two labels in flash.r for the S13.020 fw. |
@travisgoodspeed can we include the s13.020 build in the ci-builds? |
@aeickho dmesgtail slows down D13 as well. |
I can do that ... Ci-builds also with s13.020 |
confirmed S13 RT8GPS |
I'll close it now... gps radios are working |
This issue is to track bootstrapping S013.020 firmware with at least the following features. Wherever possible, they should be implemented as C function hooks with an absolute minimum of assembly patching. After S013.020 is targeted in this manner, we'll try adapting other releases.
Close this issue when the firmware boots with the following features:
Update 20160907, df8av
All symbols, patches and hooks adapted -- but not checked yet
The text was updated successfully, but these errors were encountered: