@theAnonymous1 are yours low powered versions? i got a couple of these ones from different sellers on Ali, one has the app you mention, but just didnt like how it would go nuts and restart the module if it got too loud. And thats even with a capacitor put on the +/- to ensure adequate power supply
https://www.aliexpress.com/item/100....order_list.order_list_main.79.40fe18022reqXV
https://www.aliexpress.com/item/100....order_list.order_list_main.79.40fe18022reqXV
Thanks to this program, I changed the qcc3031 mini very easily, thank you very much.
Hi I'm finding this months later,
I'm using the Wondom JAB5 (aka Dayton KABD 4100), and trying to change the name of the bluetooth transceiver, as you did with the qualcomm chip earlier in this discussion.
Wondom hid the name of the bluetooth chip but on the Dayton one you can read BTM99-QCC30AHD-34, and their website tells it is Qualcomm so I'm guessing the green chip is based on Qualcomm's QCC3034 but I can't find what that particular green chip is, to find a pinout and program it with QCC Tool.
Would you have any idea of what that chip is or where I can find the pinout?
I'm using the Wondom JAB5 (aka Dayton KABD 4100), and trying to change the name of the bluetooth transceiver, as you did with the qualcomm chip earlier in this discussion.
Wondom hid the name of the bluetooth chip but on the Dayton one you can read BTM99-QCC30AHD-34, and their website tells it is Qualcomm so I'm guessing the green chip is based on Qualcomm's QCC3034 but I can't find what that particular green chip is, to find a pinout and program it with QCC Tool.
Would you have any idea of what that chip is or where I can find the pinout?
Have You had any luck contacting Wondom?
I'm guessing no, since (I think) they sell the renaming and are not very responsive on this subject
Tested but it seems to change only a software name or something, because its bluetooth name is still WONDOM
@batttoleo I don't know, maybe there is some kind of firmware lock? It works perfectly on the boards I have. Type in new name, click "SET NAME", then click "REBOOT EFFECT". It immediately goes in to pairing mode with the new device name.
Hello All,
I'm new in the forum, unfortunately i never see this before!!
We are moving our project from CSR 867x to QCC (QCC3024 and we have also board with QCC5124).
Has anyone managed to have two eSCO audio connections open at the same time?
What i mean is:
Unit A <- First Audio eSCO -> Unit B <- Second Audio eSCO -> Unit C.
We can create the first audio connection between unit A and Unit B.
We achieve this by directly invoking the ConnectionL2capConnectRequest and ConnectionSyncConnectRequest, creating an eSCO channel. Subsequently, we connect the sink to the DSP through the AudioConnect API.
I can create the second L2CAP and Sync connection, but wen i call for the second time AudioConnectio the unit has going into panic.
The third unit could also be a phone (only phone call no music); it doesn't necessarily have to be another QCC board.
The audio must be Mono, I already have SCO and A2DP at the same time.
Thanks to all for the time.
Best regards
I'm new in the forum, unfortunately i never see this before!!
We are moving our project from CSR 867x to QCC (QCC3024 and we have also board with QCC5124).
Has anyone managed to have two eSCO audio connections open at the same time?
What i mean is:
Unit A <- First Audio eSCO -> Unit B <- Second Audio eSCO -> Unit C.
We can create the first audio connection between unit A and Unit B.
We achieve this by directly invoking the ConnectionL2capConnectRequest and ConnectionSyncConnectRequest, creating an eSCO channel. Subsequently, we connect the sink to the DSP through the AudioConnect API.
I can create the second L2CAP and Sync connection, but wen i call for the second time AudioConnectio the unit has going into panic.
The third unit could also be a phone (only phone call no music); it doesn't necessarily have to be another QCC board.
The audio must be Mono, I already have SCO and A2DP at the same time.
Thanks to all for the time.
Best regards
Hi all,
I have a QCC5125 (BTM525) and it is not turning on. The USB isn't being detected in Windows 11 device manager either. The LED will turn on when I flip the switch for SYS_CTRL, but it is very dim and it remains on until I unplug the device from power. I probed the 1.8V pin when given power and I get 1.795V, so the internal regulators are working, it just refuses to boot. Please let me know if there are any mistakes in the hardware design below!
Schematic design:
PCB:
I have a QCC5125 (BTM525) and it is not turning on. The USB isn't being detected in Windows 11 device manager either. The LED will turn on when I flip the switch for SYS_CTRL, but it is very dim and it remains on until I unplug the device from power. I probed the 1.8V pin when given power and I get 1.795V, so the internal regulators are working, it just refuses to boot. Please let me know if there are any mistakes in the hardware design below!
Schematic design:
PCB:
So I’m trying to get into a device with dual QCC3024s. Removed the chips to follow the ball pins out to pads that are present. This is what I got
PIO-61
Sys-ctrl
PIO-17
USB-DN
Vdd-PMU Vindig
There’s other pads but they don’t go directly to the BT chips. With these identifications is there any method for getting into the chip?
PIO-61
Sys-ctrl
PIO-17
USB-DN
Vdd-PMU Vindig
There’s other pads but they don’t go directly to the BT chips. With these identifications is there any method for getting into the chip?
