nicFW900 V4.00.12 [firmware only]
Added 2025-05-20 09:49:13 +0000 UTCUse with SPI Application V4.00.11 (previous release).
This release changes the timing of the communication between the MCU and the BK48(1/2)9 in an attempt to prevent destabilization and error conditions.
The "Console Debug" option has been updated to perform a live read of all registers rather than reporting the cached values, should give me better information. Note the value of Register 0x00 when doing this (convert to hexadecimal).
A new temporary menu option "69. BK Reset" has been added. Its purpose is to perform a full reset of the BK48(1/2)9 chip to see if this causes it to properly recover from a glitched state. This is not intended as a fix for the problem but rather a way to test a potential recovery procedure after an automatic sanity check.
Comments
Like the TK 11? I know TK 11 has both of these chips and from a logical perspective i don't think it will make sense to have them both running at the same time if at least the registers weren't the same. Also, it feels like there might be some more undocumented or "hidden" registries that allows the TK 11 to go down into the HF bands without the need of a dedicated chip like the si4732, unless they are running some sort of SDR type of firmware but even then, it's way beyond the documented capabilities of the BK4819, BK4829. But that's unrelated to NicFW 😊
RedJohn
2025-05-21 09:08:15 +0000 UTCI have the Register manual for the BK4819 can’t find the one for the BK4829 yet to compare it to. But I did find that some HTs use both chips for true 2 channel VFO operations. Also some set the 4819 Reg for auto mic gain level control as opposed to manual. This radio is not dead I can connect to it via USB serial and monitor the activity. Seems to imply the power switch is a “soft” on/off even though the screen is black. I am using a port monitor to see if I can spot what’s going on.
Ken
2025-05-20 21:33:00 +0000 UTCWhen you get it, find out what stops it. Does it still happen if you open the menu for example? Meaning, while it's stuttering does opening the menu stop it, if so does it start again after closing the menu. Things like that need exploring.
Marcus Dudley
2025-05-20 17:09:15 +0000 UTCSo I haven't been able to reproduce the radio going deaf after several hours of scanning, so I think you've nailed it with whatever change you made. But...I do now get the helicoptering / stuttering issue which I never got before. Is running in debug mode and capturing the registers going to be of any use for that? Are there any other settings I should try tweaking?
David
2025-05-20 16:31:38 +0000 UTCI don't think your radio is working properly Ken. Send it back and get it replaced. That doesn't happen to anyone else and when the radio becomes glitched for anyone else simply turning it off and on restores it. Something's clearly not right with yours and feedback based on a faulty radio isn't going to be productive.
Marcus Dudley
2025-05-20 16:00:34 +0000 UTCYeah for now use the Voltage readout. Goes from 8.4 full down to around 7.0 empty although I've yet to pin down the low level for calibration of the percentage. But bear in mind that the battery life on the RT-900 is exceptional.
Marcus Dudley
2025-05-20 15:57:14 +0000 UTCI am glad you can now watch the registers in action. What software are you using? I noticed on the example circuit they are using two 68pf caps with the 26Mhz crystal instead of two 22pf caps. And the high end of the frequency range is now slightly lower. It seems like they may have been chasing a timing/stability issue for one. They don’t give any reason for the change, what was changed or “improved” on the new device or why. Weird. As far as some feedback, I installed the last update after my radio recovered from another zombie state, and It ran ok so I turned the volume down and let it run overnight. When I got up it was still working. I shut it down to recharge the battery. I turned it back after about 5 hours. It ran like it had been and two hours later I was listening to a transmission on 2m band and it decided to go zombie again, no clue, I removed the battery like before and will leave it like that for a few hours and see if it wakes up again. And will install the latest firmware. The BK4819 is used in other devices and I have been poking around to see if there are any similar problems reported. So far nothing. I am curious if there maybe a saturation ( switching time) issue with this chip that it is triggering an automatic internal shutdown? Marcus’s firmware runs faster than the original. Just a thought. It would be interesting to see the register states right before it goes zombie. I think your last idea will give us some answers Marcus. I will install the latest when Rip-Van-radtel wakes up again.
Ken
2025-05-20 15:31:16 +0000 UTCI s the Battery calibration still inwork, as mine after being charged all night still only shows 89%?
Stacy Poteet
2025-05-20 14:56:07 +0000 UTCNot having the issue I reported yesterday where after setting the Sq Tail Elim to anything other than Off, it causes it to transmit off frequency after you receive a transmission.
Scott Stone
2025-05-20 14:42:10 +0000 UTCSo far so good for me too, I've scanned a few times now and no issue
Tyler W
2025-05-20 12:48:30 +0000 UTCSo far so good, have been scanning for nearly an hour now and no sign of the radio going deaf, previously it would happen after 5-10 minutes
David
2025-05-20 11:04:26 +0000 UTC
