Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question about ti cc1352p-2 #2162

Closed
flower87lucky opened this issue Oct 19, 2019 · 72 comments
Closed

question about ti cc1352p-2 #2162

flower87lucky opened this issue Oct 19, 2019 · 72 comments

Comments

@flower87lucky
Copy link

@flower87lucky flower87lucky commented Oct 19, 2019

)
zigbee2mqtt:info 2019-10-19T12:50:02: Starting zigbee-herdsman...
zigbee2mqtt:error 2019-10-19T12:50:09: Error while starting zigbee-herdsman
zigbee2mqtt:error 2019-10-19T12:50:09: Failed to start zigbee
zigbee2mqtt:error 2019-10-19T12:50:09: Exiting...
zigbee2mqtt:error 2019-10-19T12:50:09: Error: SRSP - SYS - version after 6000ms
at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
npm
ERR! code
ELIFECYCLE
npm
ERR! errno 1
npm
ERR! zigbee2mqtt@1.6.0 start: node index.js
npm
ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.6.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm
ERR! /root/.npm/_logs/2019-10-19T12_50_09_649Z-debug.log
2019-10-19T20:50:09: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-10-19T20:50:09: PM2 log: App [npm:0] starting in -fork mode-
2019-10-19T20:50:09: PM2 log: App

@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 19, 2019

serial:
/dev/ttyACM1
/dev/ttyACM0
/dev/serial/by-id/usb-Texas_Instruments_XDS110__02.03.00.18__Embed_with_CMSIS-DAP_L43000GM-if03
/dev/ttyAMA0
/dev/serial/by-id/usb-Texas_Instruments_XDS110__02.03.00.18__Embed_with_CMSIS-DAP_L43000GM-if00
input:

@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 19, 2019

"serial": {
"port": "/dev/ttyACM0"
},
"advanced": {
"pan_id": 6758,
"channel": 15,

@hdo

This comment has been minimized.

Copy link

@hdo hdo commented Oct 19, 2019

I got the same error message with my 2652R board :-(
I also tried to change panid and channel in my configuration.

https://pastebin.com/KuNRvwnG

@bertran1

This comment has been minimized.

Copy link

@bertran1 bertran1 commented Oct 20, 2019

@Koenkk

This comment has been minimized.

Copy link
Owner

@Koenkk Koenkk commented Oct 20, 2019

Can you try with

"serial": {
"port": null,
},
@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 20, 2019

Can you try with

"serial": {
"port": null,
},

Thanks.null is not allowed in Zigbee2mqtt Hass.io Add-on .I used Zigbee2mqtt Hass.io Add-on,maybe it may not support at present. I try to install ZigBee 2mqtt directly

@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 21, 2019

Can you try with

"serial": {
"port": null,
},

I'm worried if I flash the firmware in the wrong way?
After cc1352p-2 flashed the firmware, I press reset key and it has no effect.

@Koenkk

This comment has been minimized.

Copy link
Owner

@Koenkk Koenkk commented Oct 21, 2019

@hdo

This comment has been minimized.

Copy link

@hdo hdo commented Oct 21, 2019

@Koenkk

I still have the problem that i need to soft reset first (via button press) to start the firmware.

Do you know how to disable this behaviour?

Little change request:

Let the green LED light up when firmware has loaded for quick check ;-)

@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 21, 2019

Image 2

pi@raspberrypi:~ $ ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Oct 21 14:23 usb-Texas_Instruments_XDS110__02.03.00.18__Embed_with_CMSIS-DAP_L43000GM-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Oct 21 14:23 usb-Texas_Instruments_XDS110__02.03.00.18__Embed_with_CMSIS-DAP_L43000GM-if03 -> ../../ttyACM1
pi@raspberrypi:~ $ test -w /dev/ttyACM0 && echo success || echo failure
success
pi@raspberrypi:~ $ test -w /dev/ttyACM1 && echo success || echo failure
success
pi@raspberrypi:~ $ 
@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 21, 2019

DE2C8A3E876723407674E0E21AA6EAD3
When I connect to raspiberry pi 4b+ ,only the green led on.

@Koenkk

This comment has been minimized.

Copy link
Owner

@Koenkk Koenkk commented Oct 21, 2019

@fredrikgk chip revision C is an older revision, right? Is it binary compatible with the E revision?

@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 21, 2019

@fredrikgk chip revision C is an older revision, right? Is it binary compatible with the E revision?

@Koenkk How to fix binary to compatible,thanks.

@fredrikgk

This comment has been minimized.

Copy link

@fredrikgk fredrikgk commented Oct 21, 2019

@flower87lucky , @Koenkk , IC revision C is deprecated and not supported. SW is not binary compatible between rev. C and rev. E.

The only alternative is to order a new LaunchPad.

@hdo

This comment has been minimized.

Copy link

@hdo hdo commented Oct 21, 2019

@fredrikgk

BTW Do you have an idea why i need to soft reset (via button press) each time after USB plug to start the firmware?

@flower87lucky

This comment has been minimized.

Copy link
Author

@flower87lucky flower87lucky commented Oct 21, 2019

@fredrikgk

BTW Do you have an idea why i need to soft reset (via button press) each time after USB plug to start the firmware?

I agree you.

@Koenkk

This comment has been minimized.

Copy link
Owner

@Koenkk Koenkk commented Oct 21, 2019

@fredrikgk thanks, I will close this.

@Koenkk Koenkk closed this Oct 21, 2019
@james-fry

This comment has been minimized.

Copy link

@james-fry james-fry commented Oct 28, 2019

@fredrikgk

BTW Do you have an idea why i need to soft reset (via button press) each time after USB plug to start the firmware?

I got caught out with the need for soft reset too.
(and thanks for your assistance with this in the z2m issue @hdo)

I agree with your suggestion that either/both of the following would be good:

  • No need for soft reset on plug in of device
  • One of the LEDs on the MCU side will be used to indicate status or "success"

@Koenkk are either of these doable? should I raise an issue on the zstack fw repo?

@hdo

This comment has been minimized.

Copy link

@hdo hdo commented Oct 28, 2019

@james-fry

This is not a simple task.
I compiled a custom firmware version with LED support and that is also not a good indicator for this problem. I learned the firmware is loading correctly. However the culprit is the onbard debugger of the launchpad. On my Intel NUC i need the soft reset but not on my raspberry pi. There seems to be an issue with the usb handshake or something like this. I don't have any issues using the UART so that's why i think it's the usb part. The UART have other issues though (sending leading ZERO in some circumstances).

@james-fry

This comment has been minimized.

Copy link

@james-fry james-fry commented Oct 28, 2019

Thanks for the info @hdo
I am also on intel so maybe that is why I also need the reset, but its not a big deal when you know you need to do this.

@fredrikgk

This comment has been minimized.

Copy link

@fredrikgk fredrikgk commented Oct 29, 2019

@hdo Do you have to press the reset button also when the USB cable has been disconnected for a long time?

@fredrikgk

This comment has been minimized.

Copy link

@fredrikgk fredrikgk commented Oct 29, 2019

I compiled a custom firmware version with LED support and that is also not a good indicator for this problem. I learned the firmware is loading correctly. However the culprit is the onbard debugger of the launchpad. On my Intel NUC i need the soft reset but not on my raspberry pi. There seems to be an issue with the usb handshake or something like this. I don't have any issues using the UART so that's why i think it's the usb part. The UART have other issues though (sending leading ZERO in some circumstances).

This is strange, as the reset button only resets the CC1352P, not the debugger.

How is your LaunchPad configured (jumpers) when you are "using UART"?

@hdo

This comment has been minimized.

Copy link

@hdo hdo commented Oct 29, 2019

@hdo Do you have to press the reset button also when the USB cable has been disconnected for a long time?

I have to soft reset each time i plug in the usb power cable.

This is strange, as the reset button only resets the CC1352P, not the debugger.

I not sure about that.

How is your LaunchPad configured (jumpers) when you are "using UART"?

I removed the TX/RX jumpers.

It could also work without removing those jumpers but i noticed some preceeding '0'-byte which disturbs the communication, at least in my environment.

I'm currently working on a zigbee-herdsmann modification to use my tcp2serial adapter without socat (not working with docker) and this (0-byte) happens with the tcp2serial adapter.

Also see: 0-byte

@a-bailey

This comment has been minimized.

Copy link
Contributor

@a-bailey a-bailey commented Nov 13, 2019

I seem to have a B revision of the launchpad board is this supposed to work?

pi@raspberrypi:~ $ test -w /dev/ttyACM0 && echo success || echo failure
failure
pi@raspberrypi:~ $ test -w /dev/ttyACM1 && echo success || echo failure
failure

getting failure on both write tests.

@dariuszqrek

This comment has been minimized.

Copy link

@dariuszqrek dariuszqrek commented Dec 8, 2019

I have board revision B, chip revision E and have same error - zigbee2mqtt won't start.
what could be a problem ?

@timdonovanuk

This comment has been minimized.

Copy link

@timdonovanuk timdonovanuk commented Dec 22, 2019

How do you know what revision board you've got? Going to be a bit annoyed if I wasted $50 on a board that isn't supported when the z2m docs don't mention that only certain revs work :(

@dariuszqrek

This comment has been minimized.

Copy link

@dariuszqrek dariuszqrek commented Dec 23, 2019

@remkolems

This comment has been minimized.

Copy link

@remkolems remkolems commented Jan 15, 2020

I'm in the middle of a broken setup, too. I was getting the Error: SRSP - SYS - version after 6000ms error until I made the following changes (not sure if all were needed):

  • I'm running in Proxmox, so I changed from USB Vendor Device ID to USB port assignment
  • Rebooted the whole Proxmox computer
  • Hit the reset button on board

Since "null" isn't supported via HA, I'm running with "port": "/dev/ttyACM1" and I got a connection in the end. However, I still haven't managed to get any traffic to show up. I restored the database.db and it looks like they're all getting loaded, but nothing past that yet.

Edit: Well, I tried reconnecting one of my Xiaomi buttons and it started working after I did the reconnect. This won't be fun if I need to reconnect them all (~70 devices).

That is what I had to do also (still doing to be honest). A real pain in the a s s ....

@docBliny

This comment has been minimized.

Copy link

@docBliny docBliny commented Jan 15, 2020

Yup, just spent the evening resetting everything. Found several water sensors that had run out of battery while I was at it, so something positive. Also looked like the Aqara water sensors would connect just by activating them twice (short press). The first connect would fail with Failed to interview 'water_leak_15', device has not successfully been paired but the second attempt would register it (without the long hold to "reset").

Now I just need to get my IKEA remotes to work via groups. I guess I'll need to do the whole network sniffing thing to get them connected again.

Edit: Thank goodness. You can get the group ID by turning on debug logging now instead of building a sniffer USB stick etc...

@jrhansen

This comment has been minimized.

Copy link

@jrhansen jrhansen commented Jan 15, 2020

  1. Powered up an old RPi3 with a fresh Raspbian lite SD card.
  2. Installed Mosquitto.
  3. Followed the Z2M installation instructions.
  4. Setup the correct port (and initially forgot to set a different pan_id than my existing Zigbee network).
  5. On first 'npm start' I got the 'SRSP - SYS - version after 6000ms' error.
  6. Pushed the reset button.
  7. 'npm start' again -> Same error.
  8. Disconnected the CC1352P-2 from the USB port.
  9. Reconnected the board.
  10. 'npm start' again -> Same error.
  11. Pushed the reset button.
  12. 'npm start' -> Error saying that the pan_is already in use!
  13. Changed the pan_id.
  14. 'npm start' -> Z2M now starts up correctly :-)

So, it seems that things have started to work now even though I tried the reset button and all kinds of other stuff yesterday to no avail. I tried to break it again by reconnecting the board (in different USB ports), rebooting, pressing the reset button, changing the pan_id, going from '/dev/ACM0' to 'null' in the port setup, but it seems unbreakable now. I can join new devices without trouble, and I don't have to press the reset button again - even after a power cycle (??).

Now, I will go back to implementing the board in my existing setup with the risk of having the rejoin everything.

When I did experiments yesterday with my existing network, when the CC1352P-2 failed I had to go back to the CC2531, and I had to rejoin all devices even though I had backed up the 'data' folder. So...

Should I backup other folders than the 'data' folder? The entire Z2M folder, or something else in the system?

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Jan 20, 2020

@jrhansen IMHO, the data directory is sufficient. But going forward and backward between z stack versions (1.2 vs 3) can be tricky / may require re-pairing (regardless of a backup).

My CC1352P-2 is now running as my daily driver for a few days now with Z2M 1.9.0 from HassIO and everything's working fine so far. No issues and (re-) pairing of all my devices was SO smooth (I did not even try w/o re-pairing as I wanted a fresh install), it even made kinda fun. 😂

@TheStigh

This comment has been minimized.

Copy link

@TheStigh TheStigh commented Jan 26, 2020

@jrhansen IMHO, the data directory is sufficient. But going forward and backward between z stack versions (1.2 vs 3) can be tricky / may require re-pairing (regardless of a backup).

My CC1352P-2 is now running as my daily driver for a few days now with Z2M 1.9.0 from HassIO and everything's working fine so far. No issues and (re-) pairing of all my devices was SO smooth (I did not even try w/o re-pairing as I wanted a fresh install), it even made kinda fun. 😂

@CodeFinder2
I've just started playing with z2m and installed a standalone docker installation on a RPi4 with the CC2531. Currently I'm waiting for my CC1352P-2, and when it arrives I would like to move my z2m to my HA hardware running on a NUC i7.

My question to you would be; should I run the z2m HA addon or would I benefit from running z2m as a docker install on the same hardware?

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Jan 26, 2020

[...]
My question to you would be; should I run the z2m HA addon or would I benefit from running z2m as a docker install on the same hardware?

The advantage of the hassio addon is it's simplicity in installing / managing it (single web instance: HA). Behind the scenes, it's a docker container as well (you might want to take a look at the "Portrainer" addon).

I am using the hassio addon and I'm quite happy with it. Also having features like 'secrets' and accessing the log in HA should be taken into consideration.

The disadvantage is mainly that you are depending on the release cycle of the addon (although this is normally the same as for Z2M). Also switching between stable/dev might be a bit more complicated sometimes.

So, as usual: it depends. 🙈 I would suggest that you start using the hassio addon first. By the way, you can also use somewhat both: install both, do all the pairing and configuration you require in the addon. Then you should be fine in copying the config over to the docker instance. Of cause you shouldn't run both simultaneously. (Going the other way round is also possible but requires YAML > JSON converting and a bit care.) But this way, switching between both should be just a 'stop one, start the other' (possibly updating / copying config first).

Hope this helps!

@james-fry

This comment has been minimized.

Copy link

@james-fry james-fry commented Jan 26, 2020

The disadvantage is mainly that you are depending on the release cycle of the addon (although this is normally the same as for Z2M).

There is an edge version of the addon that installs the latest dev z2m.
Downside is that to upgrade you need to delete the addon and reinstall. (Needing to copy/paste the config ofc)

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Jan 26, 2020

The disadvantage is mainly that you are depending on the release cycle of the addon (although this is normally the same as for Z2M).

There is an edge version of the addon that installs the latest dev z2m.
Downside is that to upgrade you need to delete the addon and reinstall. (Needing to copy/paste the config ofc)

Yes, but (although this is solved now): danielwelch/hassio-zigbee2mqtt#284

I wrote that because one should consider that there's the "addon in between", adding an additional/potential source of errors.

@TheStigh

This comment has been minimized.

Copy link

@TheStigh TheStigh commented Jan 27, 2020

@CodeFinder2 @james-fry

Thanks to both of you for the answers!
I already use Portainer on my RPi4 running the test-installation of z2m together with z2m-assistant.

May I ask another question;
My house do have several floors and there is no way my Coordinator (or any powered zigbee devices) will reach one particular floor as it is concrete in all walls. The only thing I have there that reaches the rest of the house are cabled Cat6 network. My plan was to set my RPi4 on this floor with a CC2531, but the question is then, what firmware should I use on this so it communicates correct with HA/z2m (with CC1352P-2) on the main floor? Or am I totally off understanding how z2m works?

PS; my CC1352P-2 arrives next week - is there any difference in setting it up on z2m addon vs z2m standalone? Anything I should be aware of (hoping I don't get a deprecated revision, but it is coming directly from TI).

@TheStigh

This comment has been minimized.

Copy link

@TheStigh TheStigh commented Jan 27, 2020

[...]
So a nice little bit of improvement there, I should get an SMA antenna to increase that even more, anyone can recommend me one? [...]

I bought this one (because it was also labeled "Zigbee") and it works good, see my post above: https://www.digikey.de/product-detail/de/linx-technologies-inc/ANT-2.4-CW-HW-SMA/ANT-2.4-CW-HW-SMA-ND/2391322 (8€)

Don't know if any similar (Cheap Chinese 😂) SMA 2.4 GHz antenna would do the same job. 😁

If you already have paired devices to the CC1352P-2 and then do the mod/add the external antenna, do you have to re-pair afterwards? Or is that part 'plug-and-play' after re-soldering the capacitor?

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Jan 28, 2020

@CodeFinder2 @james-fry

Thanks to both of you for the answers!
I already use Portainer on my RPi4 running the test-installation of z2m together with z2m-assistant.

May I ask another question;
My house do have several floors and there is no way my Coordinator (or any powered zigbee devices) will reach one particular floor as it is concrete in all walls. The only thing I have there that reaches the rest of the house are cabled Cat6 network. My plan was to set my RPi4 on this floor with a CC2531, but the question is then, what firmware should I use on this so it communicates correct with HA/z2m (with CC1352P-2) on the main floor? Or am I totally off understanding how z2m works?

If you are sure that it's impossible to get any Zigbee signal to that floor, you can surely use your RPi (connected via Ethernet) and create a separate Zigbee network (in addition to the one created by your CC1352P-2 coordinator). On the RPi would then run Z2M as well, publishing messages to the same MQTT broker (via Ethernet). The CC2531 would then be a coordinator as well (but spawning a DIFFERENT network). Although I have never used this kind of setup myself but you are welcome to report your experiences here! :-)

PS; my CC1352P-2 arrives next week - is there any difference in setting it up on z2m addon vs z2m standalone? Anything I should be aware of (hoping I don't get a deprecated revision, but it is coming directly from TI).

Not really. Except that the addon requires JSON and Z2M requires YAML configuration. Also "port: null" does not work in the Hassio addon. According to my knowledge, TI only sends the recent revisions so no need to worry.

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Jan 28, 2020

[...]
So a nice little bit of improvement there, I should get an SMA antenna to increase that even more, anyone can recommend me one? [...]

I bought this one (because it was also labeled "Zigbee") and it works good, see my post above: https://www.digikey.de/product-detail/de/linx-technologies-inc/ANT-2.4-CW-HW-SMA/ANT-2.4-CW-HW-SMA-ND/2391322 (8€)
Don't know if any similar (Cheap Chinese 😂) SMA 2.4 GHz antenna would do the same job. 😁

If you already have paired devices to the CC1352P-2 and then do the mod/add the external antenna, do you have to re-pair afterwards? Or is that part 'plug-and-play' after re-soldering the capacitor?

I have started the pairing (re-pairing because I used a CC2531 previously) after I did the mod but if you do the pairing before the mod, no re-pairing should be required. You may want to keep in mind that IF you damage the board during the re-soldering (which is VERY unlikely), you have to go back to the CC2531 (= repairing). However, it's virtually impossible to destroy the board although it can happen that you destroy the capacitor because its very tiny and it depends on your soldering skills. Nonetheless, this isn't a real problem as well since they are really cheap. ;-)

@remkolems

This comment has been minimized.

Copy link

@remkolems remkolems commented Feb 7, 2020

I did the the capacitor mod and was not successful. I destroyed the capacitor completely. Signal with the antenna became half of CC2531 (oops to say the least), So watch out! I had to buy a new board to continue my journey.... The bloody cap is tiny! You will need a magnifying glass.

Planning to repair my board, once I have the correct soldering station and miscellaneous required tools. I will keep this thread up to date.

See also (specs of capacitor and where to buy):

(https://zigbee2mqtt.discourse.group/t/cc1352p-switch-to-external-antenna-instead-of-pcb/681/6?u=rlems)
and
https://zigbee2mqtt.discourse.group/t/cc1352p-switch-to-external-antenna-instead-of-pcb/681/7?u=rlems

@timdonovanuk

This comment has been minimized.

Copy link

@timdonovanuk timdonovanuk commented Feb 7, 2020

I really don't understand the design. Why even bother putting a SMA connector on...but then require phsyical modification to the board to actually support it. facepalm.

@james-fry

This comment has been minimized.

Copy link

@james-fry james-fry commented Feb 7, 2020

I really don't understand the design. Why even bother putting a SMA connector on...but then require phsyical modification to the board to actually support it. facepalm.

Because its a hardware dev kit not an "end user" device.
TI are expecting this to be used to develop new devices - hence assumption there will be support engineers well able to resolder a SMD device.

@timdonovanuk

This comment has been minimized.

Copy link

@timdonovanuk timdonovanuk commented Feb 7, 2020

I understand that, but thats not really a good justification, IMO. They also could have just shipped the entire board as a bag of parts and expect Ikea style self assembly? 😆

There are various jumpers on the board that allow changes, rather than having to solder a trace on..same principle.

@james-fry

This comment has been minimized.

Copy link

@james-fry james-fry commented Feb 7, 2020

I understand that, but thats not really a good justification, IMO. They also could have just shipped the entire board as a bag of parts and expect Ikea style self assembly? 😆

There are various jumpers on the board that allow changes, rather than having to solder a trace on..same principle.

I thought on this too when I 1st saw the design.
I'm no RF engineer, but I think the losses and EMC issues from adding a jumper in the signal path would be unacceptable.

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Feb 7, 2020

@remkolems Sorry to hear that and thanks for sharing your insights with us! That's why I warned about the mod/resoldering. 😑

Hope you can finally repair it!

@fredrikgk

This comment has been minimized.

Copy link

@fredrikgk fredrikgk commented Feb 7, 2020

I really don't understand the design. Why even bother putting a SMA connector on...but then require phsyical modification to the board to actually support it. facepalm.

You cannot use a conventional jumper for RF signals, that will introduce impedance mismatch and RF signal loss.

Similarly, you cannot simply split the RF path in two. Even when using a proper RF design splitter, which can be implemented on PCB, you would get 3 dB loss. That is not acceptable.

The design is made for TI´s customers to easily be able to evaluate the radiated performance out of the box. Thus, the PCB antennas are connected by default. The SMA is intended primarily for customers who want to do advanced RF testing by connecting the radio directly to RF instruments (spectrum analyser, RF signal generator, etc.). These are typically fully capable of soldering a 0402 component.

@remkolems , the simplest way to solder the capacitor is to use a hot-air soldering iron. Combine with generous amounts of liquid flux and a good microscope and it is quite easy.

@patrickharris

This comment has been minimized.

Copy link

@patrickharris patrickharris commented Mar 6, 2020

Thanks guys for the clue to press the soft reset button next to the USB connector. So happy it's working now.

@valepe

This comment has been minimized.

Copy link

@valepe valepe commented Mar 25, 2020

I flashed my CC1352P-2 and I'm ready to change the panID and the channel (avoid wifi interferences) so I must repair my devices (no problem).
But I have a question: after paired the devices z2m will change the actual ID (eg 0x....) of my devices?

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Mar 25, 2020

@valepe No, those IDs won't change.

@valepe

This comment has been minimized.

Copy link

@valepe valepe commented Mar 28, 2020

@TASSDevon: no, it does not auto-detect an external antenna. You have to resolder a tiny capacitor on the board (CC1352P-2) to use the external antenna...unfortunately.

Can you tell me how you move this capacitor? Did you use a hot air station or a solder tip?
Thanks

@CodeFinder2

This comment has been minimized.

Copy link

@CodeFinder2 CodeFinder2 commented Mar 28, 2020

With a fine solder tip ;-)

@valepe

This comment has been minimized.

Copy link

@valepe valepe commented Mar 28, 2020

With a fine solder tip ;-)

Did it in a breaveheart moment. :)
I used and edge tip but wtf these 0402 components are too small for my tastes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.