Thanks Todd, The newest version is sounding great. I have the V version with the MCU set to 480MHZ on 700 and 800 MHZ
Thank you!I'm going to test both my P25RX units with the latest firmware and report back the results to you later this evening. Will test P2 at both 400 and 480 Mhz mcu speed and let you know my results.
Sorry,yes, it did.Thanks. Did P2 work for you at new default of 400 MHz? That is the main question I'm looking to answer.
Thank you for testing!Sorry,yes, it did.
Thank you for testing. I'm not sure at this point what might cause this. There is quite a bit of complexity to all the internal clocks. I may have overlooked something. Can you use the 'mcu_ver' command on the earlier firmware to report what version of the MCU you have on this receiver?UPDATE -- Had to hold the Talkgroup button for 10 seconds when powering the P25RX up and was able to flash back to the last stable version of BTConfig (6-17-2021) and the P25RX now works normally, but trying to flash to the latest TEST version (BTConfig-2021-07-15_1231) will consistently brick my P25RX
I think I found the cause. Can you give 2021-07-16_0301 a try?I went to test the 7-15 firmware and it "bricked" my first P25RX when the firmware process completed.
I've powered off the P25RX and re-ran BTConfig but it just hangs at "read sys_config".
The way I understand it is that the "V" version is spec'd to 480 MHz BUT the newer parts that are now available for Todd to build new units going forward are the "Y" versions and are only spec'd to 400 MHz. Therefor, Todd is now trying to optimize his new code to work properly with the lower frequency MCU's so he wants us to test as much as possible at 400 MHz even if we have a "V" version that can do 480 MHz.Question for you Todd, if you have a V version what MHZ should you run and if you have the Y version what MHZ should you run