Experimental changes to code optimisation
Experimental changes to code optimisation
Guys,
Before I release this as the 'latest' version, I think its prudent if I release it as a experimental version.
The main differences between this version and the 16th, that make it experimental, is that I have changed the compiler optimisation on as many files as possible, so that parts of the firmware will run a bit faster; including the code that handles the DMR audio buffering and the beep, but I've also changed settings on some of the CPU SDK (software development kit) files from the CPU manufacturer (NXP).
There are still some quirks (bugs) in the source code, which prevent all the source files being optimised, so currently its a bit of a balancing act between enabling optimisation on as may files as possible without breaking the code and then having to track down quite complicated bugs.
I've also updated the development environment (IDE) on my PC and the SDK files, but this should not make any difference, because I know Daniel and possibly Alex have been using the newer IDE and SDK for quite along time.
This version has been running for me for around 2 days, but I don't use scanning that much, so the only way to really test it is to make it public
Before I release this as the 'latest' version, I think its prudent if I release it as a experimental version.
The main differences between this version and the 16th, that make it experimental, is that I have changed the compiler optimisation on as many files as possible, so that parts of the firmware will run a bit faster; including the code that handles the DMR audio buffering and the beep, but I've also changed settings on some of the CPU SDK (software development kit) files from the CPU manufacturer (NXP).
There are still some quirks (bugs) in the source code, which prevent all the source files being optimised, so currently its a bit of a balancing act between enabling optimisation on as may files as possible without breaking the code and then having to track down quite complicated bugs.
I've also updated the development environment (IDE) on my PC and the SDK files, but this should not make any difference, because I know Daniel and possibly Alex have been using the newer IDE and SDK for quite along time.
This version has been running for me for around 2 days, but I don't use scanning that much, so the only way to really test it is to make it public
- Attachments
-
[The extension sgl has been deactivated and can no longer be displayed.]
Re: Experimental changes to code optimisation
hi, been running for about 1 hour now (scanning), all seems fine. will test hotspot at a more civil hour (6:35am here )
Re: Experimental changes to code optimisation
all right from about 1 hour of operation including scan ... thanks
Sal
Sal
Re: Experimental changes to code optimisation
all ok, hotspot mode great (blue dv), scanning great(analoue/digital combined), nothing out of the ordinary to report.
unable to test repeaters, as there are none in range
unable to test repeaters, as there are none in range
Re: Experimental changes to code optimisation
Nothing special either to report, everything seems Ok
Re: Experimental changes to code optimisation
Globally It seems OK to me except a difference.
I am not sure 100% that this is specific to the experimental version as just here I am looking deep.
When scanning, the scanner stops on my local repeater even if it is only used on slot 2 though I set the GD77 on slot 1 (of course I set on TIER 2 option and I ear nothing)
I have no problem with the sound (with one of my GD77/openGD77, I have something wrong as I said on the forum). I don't know if the +4dB is implemented on this experimental version.
73. Luc
I am not sure 100% that this is specific to the experimental version as just here I am looking deep.
When scanning, the scanner stops on my local repeater even if it is only used on slot 2 though I set the GD77 on slot 1 (of course I set on TIER 2 option and I ear nothing)
I have no problem with the sound (with one of my GD77/openGD77, I have something wrong as I said on the forum). I don't know if the +4dB is implemented on this experimental version.
73. Luc
Re: Experimental changes to code optimisation
Думаю можно называть ее стабильной
EDIT from F1RMB: "I think you can call it stable"
EDIT from F1RMB: "I think you can call it stable"
Re: Experimental changes to code optimisation
Спасибо Дэниел
Tnx Daniel
Tnx Daniel
Re: Experimental changes to code optimisation
Seems to be working fine, I have not found any issues with it yet but will keep testing.
I did notice a couple of time on the local dmr repeater, while in the scan mode, durning a conversation. The screen would show a talk group and I'd but no audio was heard. When the transmittion was dropped, the next ham replyed the audio was heard again and the rest on both sides of the exchanges where heard fine.. the signal was fine and only happened twice on two different times while testing
I did notice a couple of time on the local dmr repeater, while in the scan mode, durning a conversation. The screen would show a talk group and I'd but no audio was heard. When the transmittion was dropped, the next ham replyed the audio was heard again and the rest on both sides of the exchanges where heard fine.. the signal was fine and only happened twice on two different times while testing
Last edited by KU4ZD on Sat Jan 18, 2020 8:12 pm, edited 1 time in total.