ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Hello Everybody
I am writing to you guys after seeking an answer for my issue across the web for some time and exhausting all options I could think of. I would greatly appreciate any thoughts/guidelines/know how with regards to the issue herein (Its a bit long and technical...please bear with me ) :
I received a BEOLIT15 BT speaker that broke down. I already own one speaker like this and since it is such an expensive speaker, I decided to try and fix it.
The BEOLIT15 incorporates a BT module (BTM865a) with a CSR8670 chip, which is also used as the speaker's host.
CSR provides a tool that can allow a technician/developer to connect directly to their chip for diagnostics/configuration and development purposes. I used this tool to connect to the BEOLIT15's module (There are pads allocated for this on the motherboard). However, any attempt to access the module failed (The chip simply returns unrecognizable type).
Since there was no other choice, I reached out to different sellers I knew and asked their help in obtaining some BT modules identical to the one that broke down. These were actually found in a different BT speaker. I then removed the inoperative BT module and installed the replacement
Since the BT module was not programmed to be "BEOLIT15" I used my own speaker to download the dump files and then reprogrammed the new module on the inoperative BEOLIT15. The speaker returned to operate and went through an upgrade. After changing the BT address key (BT_ADDR) I managed to connect to PC/smartphone along side my own BEOLIT15 speaker
Nevertheless, the speaker currently has a problem:Since the dump file used has been extracted from a "twin" speaker that operates in the same environment (More accurately, connects to the same smartphone), the BEOPLAY app is unable to register and operate both speakers.
From my studies using the CSR tools I learnt that BEOLIT15's program employs a set of keys which configure the speaker. I can only guess that there is an additional key besides the BT_ADDR that has to be changed, but I have no idea what it isIf you stumbled across a similar scenario and may know which key (aka PSKey) could solve this issue thereby allowing the BT to be registered correctly by the app. please be so kind to drop me a reply (Please note that regardless of the app - the speaker does connect to the phone's Bluetooth and plays music)
Alternatively if anyone has the dump files and could share them with me I would greatly appreciate it. The speaker itself is out of warranty in any case and I would wager that, though there will be two speakers with the same configuration in the world, they will most probably will not interface with each other If any additional information is required - please feel free to ask. I will do my best to answer
Thank you for your time, best regards to you all and stay safe
/Gil