Well, I've found another remote, which worked without any issue. So no problem on the receiver side.
I then reprogrammed the nvram of the broken one with the dump from the new one - now my friend has two functional remotes. The first thought is often the right one
I monitored today the activity on the spi interface between the transceiver and the mcu. Sometimes you can see some activity after a key press, sometimes not.
Could not find a system behind it.
I'll try to find another remote for testing....
Yes, after removing the white foil I tested all keys - they are all NO and closing every single one of them causes a wake up. The current draw looks fine for me - about 5 ma on start up, about 3 ma when awake and almost zero when asleep.
I noticed another strange behavior. There a light switch on the buttom side, which turns on LED Backlight of the keypad and also wakes up the MCU. This wakeup works always, the LEDs however sometimes don't react.
Thanks, I will try it tomorrow. I actually tested the frequently used keys and the reaction of the MCU (wake up) was adequate, but I didn't check all of them. I hope I'll get this white stuff off without damaging it.
I'm trying to fix this RF Bose remote (model nr. 420129) for a friend. After applying supply voltage the display shows the Bose logo, after a short period of time it goes dark and the MCU enters a sleep mode. It wakes up after a key is pressed, the display remains dark all the time after the start up sequence.
Sometimes it can still be paired with the main unit and you can control it for a short period of time, then the unit stops reacting again.
The pcb is clean, there are no signs of corrosion. The voltages look adequate.
Leave a comment: