Flashing CC2531-USB Variant with 5 pin holes

[joshdinsdale]

Hi All

I have 2 x CC2531 USB sticks, one is the standard version with the normal pin headers, i have this flashed and working nicely.
I also have a second CC2531 however this one doesnt have a header, but just 5 pin holes labeled as debug.
https://i.ebayimg.com/images/g/w3YAAOSwaIpb19Ed/s-l1600.jpg

Does anyone have a guide for flashing this variant (i would like to use it as a router).? I cant seem to find a pinout for this version...

Thanks!

[ptvoinfo]

@joshdinsdale It is necessary to know the meaning of each pin. You may request it from the seller.

[FlorentSueur]

Hi @joshdinsdale, I also bought a CC2531-USB variant with 5 pin holes. Did you get the meaning of each pin and did you flash it with the cc debugger ?

Thanks

[FlorentSueur]

I found this picture in an other case (#790) but it seems to be the CC2540-USB1 as written on the board

[andyfitzsuse]

I also have a stack of this variant, shorter than the other one.
Got them because they include a casing, should have looked closer.
connecting it could prove troublesome since the ribbon cable can't mount and the debug holes are in a weird order. i guess there's a way...

[GHPS]

I have the same issue - blue CC2531-USB adapter in acrylic case.

I hope that the manufacturer radioland-china.com wasn't mean enough
to change the pinout from the programming adapter that has a
double line (DIL) and a single line (SIL) header. So I checked the
connections:

1          5
+----------+
|O O O O O |
+----------+
 | | | | |
 1 2 3 4 7

2         10
+----------+
|O O O O O |
|O O O O O |
+----------+
1          9

That's a good sign since it makes sense according to the official documentation

So the pinout of the SIL connector should be

1: GND
2: Target Voltage Sense
3: DC - Debug Clock
4: DD - Debug Data
5: Reset

On my USB stick pin 1 is the right most pin with the USB connector
facing left. That means that the pins are in reversed order compared
to the picture posted previously by @FlorentSueur.

Update: I just opened the acrylic case and did a basic check of
the voltage - pin 1 is GND, pin 2 3.3 Volts.

BTW: It's very easy to open the case without damage if
start leveraging with a small knife between the USB connector
and the case.

[LordMyschkin]

I can confirm that flashing zigbee2mqtt was possible (and suprisingly simple) using the above information following the guide on http://www.zigbee2mqtt.io/information/alternative_flashing_methods.html using a raspberry pi zero w.
Although cc_chipid returned b522 - i'll still have to confirm zigbee2mqtt works....

[GHPS]

Thanks for the feedback.

[Brandon4466]

How did you go exactly about flashing this? How were you able to connect it to the CC Debugger? I tried with just some pin wires but it connects properly.

[LordMyschkin]

@Brandon4466 since my female-male wires did not fit into the debugging holes, but my male-male did, i just connected the Raspberry to a breadboard, than thee breadboard to the debugging holes by male-male wires. They fit very well, hold themself in place. Then I double checked against short-wiring and the correct Pins, connected to Raspberry and the Board to usb an there we go. No cc-debugger needed for this method, so I‘d prefer this one over any other!

[Brandon4466]

@LordMyschkin and you had to use all 5? Thank you for your help also!

The male to male wires that I have for my Raspberry Pi that fit over the GPIO pins are too big for the holes on the debug board, how were you able to use those?

[LordMyschkin]

Am 01.05.2019 um 08:33 schrieb Brandon4466 ***@***.***>: @LordMyschkin and you had to use all 5? Thank you for your help also!

i did not try with fewer, I used all 5.

[Brandon4466]

@LordMyschkin Hm, when I do it, ./cc_chipid just returns ID = 0000, All are connected, did you run into this problem?

[LordMyschkin]

I got cchip_ip=0000 with an error in wiring; it went away after re-checking and correcting the wires.

[Brandon4466]

@LordMyschkin Is there a way you got the male to male wires to stay in place? They don't fit in the holes on the debug ports at all for me.

[zbuh]

I can confirm that flashing zigbee2mqtt was possible (and suprisingly simple) using the above information following the guide on http://www.zigbee2mqtt.io/information/alternative_flashing_methods.html using a raspberry pi zero w.
Although cc_chipid returned b522 - i'll still have to confirm zigbee2mqtt works....

did you test zigbee2mqtt ?

[LordMyschkin]

sorry, it took me a while to set up a testing environment. Yes, I succeeded in connecting the stick to a AMD64 Debian Stretch and to pair an Aquara Temperature/Humidity sensor. It did show some error first "modelID undefined not supported;" but started to work than.

[schmurtzm]

Hi, successfully flashed this one (acrylic case has been removed), just followed GHPS's pinout diagram (first pin with a square shape is ground)

[diagonali]

Hi, successfully flashed this one (acrylic case has been removed), just followed GHPS's pinout diagram (first pin with a square shape is ground)

Where do your wires go to from being attached to the USB debug holes and what do they connect to? I've got the following (CC Debugger out of shot:

Can I just cut one of the cables and use it's wires? Or is soldering required? If it''s messy I might just order a naked one with the debug connectors but hopefully can get this one working...

UPDATE: Figured it out - You do need to (if you're doing it this way) separate out the wires on the thin cable and expose the ends of wires 1,2,3,4 and 7. Then carefully put them through holes 1-5 in order being careful that they don't touch each other on the back (this was very fiddly but worked in the end). If anyone needs any help with this message here and I'll be happy to help.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.