NEWS
[Verkauft] CC2652P Zigbee Stick
-
@sauerm
Welche Fehlermeldungen?
Da sind keine.@thomas-braun stimmt, das meiste sind Warnungen.
Ich habe die 8 Errors mal zusammenkopiert:
../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’: ../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’: ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’: ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);Ach sorry, das sind prints :see_no_evil:
Aber sollte so die Installation über die Konsole aussehen?Fehlermeldungen beim Adapterstart bekomme ich nach wie vor. Entweder ist der Stick kaputt (firmware habe ich schon 4-mal neu geflashed) oder irgendwas stimmt mit dem ioBroker Master nicht... :/
-
@thomas-braun stimmt, das meiste sind Warnungen.
Ich habe die 8 Errors mal zusammenkopiert:
../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’: ../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’: ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path); ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’: ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=] snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path); ^~~~~~~~~~~~~~~~~~~~~~~~~~~ ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024 snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);Ach sorry, das sind prints :see_no_evil:
Aber sollte so die Installation über die Konsole aussehen?Fehlermeldungen beim Adapterstart bekomme ich nach wie vor. Entweder ist der Stick kaputt (firmware habe ich schon 4-mal neu geflashed) oder irgendwas stimmt mit dem ioBroker Master nicht... :/
@sauerm sagte in [Verkaufe] Neueste Entwicklung: CC2652P Zigbee Stick:
Aber sollte so die Installation über die Konsole aussehen?
Ja, so sieht das aus, wenn der serialport gebaut wird.
-
@sauerm sagte in [Verkaufe] Neueste Entwicklung: CC2652P Zigbee Stick:
Aber sollte so die Installation über die Konsole aussehen?
Ja, so sieht das aus, wenn der serialport gebaut wird.
@thomas-braun Ah, okay. Wieder was gelernt :blush:
Hast du denn noch eine Idee was man machen könnte? Ich finde schon keine neuen Suchergebnisse mehr bei Google :see_no_evil:
Der Adapter startet immer noch nicht. Ich erhalte immer die selben Fehlermeldungen...
zigbee.0 2021-09-01 22:14:25.448 error Error herdsman start zigbee.0 2021-09-01 22:14:25.447 error Failed to start Zigbee zigbee.0 2021-09-01 22:14:25.445 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" zigbee.0 2021-09-01 22:14:25.240 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:14:25.181 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:14:25.179 info Try to reconnect. 1 attempts left zigbee.0 2021-09-01 22:14:15.176 error Error herdsman start zigbee.0 2021-09-01 22:14:15.175 error Failed to start Zigbee zigbee.0 2021-09-01 22:14:15.173 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" zigbee.0 2021-09-01 22:13:55.693 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:13:55.077 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:13:55.011 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.15 zigbee.0 2021-09-01 22:13:47.009 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-09-01 22:13:47.006 info terminating zigbee.0 2021-09-01 22:13:47.005 warn Failed to stop zigbee during startup zigbee.0 2021-09-01 22:13:46.999 info cleaned everything up... zigbee.0 2021-09-01 22:13:46.996 info Got terminate signal TERMINATE_YOURSELF zigbee.0 2021-09-01 22:13:09.311 error getGroups: caught error: TypeError: Cannot read property 'getGroups' of undefined zigbee.0 2021-09-01 22:10:16.665 error Error herdsman start zigbee.0 2021-09-01 22:10:16.664 error Failed to start Zigbee zigbee.0 2021-09-01 22:10:16.662 error Starting zigbee-herdsman problem : "No path provided and failed to auto detect path" zigbee.0 2021-09-01 22:10:16.486 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:10:16.458 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:10:16.456 info Try to reconnect. 1 attempts left zigbee.0 2021-09-01 22:10:06.453 error Error herdsman start zigbee.0 2021-09-01 22:10:06.452 error Failed to start Zigbee zigbee.0 2021-09-01 22:10:06.450 error Starting zigbee-herdsman problem : "No path provided and failed to auto detect path" zigbee.0 2021-09-01 22:10:06.267 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:10:05.708 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:10:05.698 error Serial port not selected! Go to settings page. zigbee.0 2021-09-01 22:10:05.642 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.15 zigbee.0 2021-09-01 21:47:13.299 error Cannot read property 'getEntries' of null zigbee.0 2021-09-01 21:47:13.298 error TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41) at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-09-01 21:47:13.295 error unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-09-01 21:47:13.294 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-01 21:47:13.292 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-09-01 21:47:13.290 info terminating zigbee.0 2021-09-01 21:47:13.289 warn Failed to stop zigbee during startup zigbee.0 2021-09-01 21:47:13.286 info Zigbee: disabling joining new devices. zigbee.0 2021-09-01 21:47:13.281 info cleaned everything up... zigbee.0 2021-09-01 21:47:13.278 info Got terminate signal TERMINATE_YOURSELF -
@thomas-braun Ah, okay. Wieder was gelernt :blush:
Hast du denn noch eine Idee was man machen könnte? Ich finde schon keine neuen Suchergebnisse mehr bei Google :see_no_evil:
Der Adapter startet immer noch nicht. Ich erhalte immer die selben Fehlermeldungen...
zigbee.0 2021-09-01 22:14:25.448 error Error herdsman start zigbee.0 2021-09-01 22:14:25.447 error Failed to start Zigbee zigbee.0 2021-09-01 22:14:25.445 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" zigbee.0 2021-09-01 22:14:25.240 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:14:25.181 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:14:25.179 info Try to reconnect. 1 attempts left zigbee.0 2021-09-01 22:14:15.176 error Error herdsman start zigbee.0 2021-09-01 22:14:15.175 error Failed to start Zigbee zigbee.0 2021-09-01 22:14:15.173 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" zigbee.0 2021-09-01 22:13:55.693 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:13:55.077 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:13:55.011 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.15 zigbee.0 2021-09-01 22:13:47.009 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-09-01 22:13:47.006 info terminating zigbee.0 2021-09-01 22:13:47.005 warn Failed to stop zigbee during startup zigbee.0 2021-09-01 22:13:46.999 info cleaned everything up... zigbee.0 2021-09-01 22:13:46.996 info Got terminate signal TERMINATE_YOURSELF zigbee.0 2021-09-01 22:13:09.311 error getGroups: caught error: TypeError: Cannot read property 'getGroups' of undefined zigbee.0 2021-09-01 22:10:16.665 error Error herdsman start zigbee.0 2021-09-01 22:10:16.664 error Failed to start Zigbee zigbee.0 2021-09-01 22:10:16.662 error Starting zigbee-herdsman problem : "No path provided and failed to auto detect path" zigbee.0 2021-09-01 22:10:16.486 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:10:16.458 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:10:16.456 info Try to reconnect. 1 attempts left zigbee.0 2021-09-01 22:10:06.453 error Error herdsman start zigbee.0 2021-09-01 22:10:06.452 error Failed to start Zigbee zigbee.0 2021-09-01 22:10:06.450 error Starting zigbee-herdsman problem : "No path provided and failed to auto detect path" zigbee.0 2021-09-01 22:10:06.267 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-01 22:10:05.708 info Starting Zigbee npm ... zigbee.0 2021-09-01 22:10:05.698 error Serial port not selected! Go to settings page. zigbee.0 2021-09-01 22:10:05.642 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.15 zigbee.0 2021-09-01 21:47:13.299 error Cannot read property 'getEntries' of null zigbee.0 2021-09-01 21:47:13.298 error TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41) at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-09-01 21:47:13.295 error unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-09-01 21:47:13.294 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-01 21:47:13.292 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-09-01 21:47:13.290 info terminating zigbee.0 2021-09-01 21:47:13.289 warn Failed to stop zigbee during startup zigbee.0 2021-09-01 21:47:13.286 info Zigbee: disabling joining new devices. zigbee.0 2021-09-01 21:47:13.281 info cleaned everything up... zigbee.0 2021-09-01 21:47:13.278 info Got terminate signal TERMINATE_YOURSELF@sauerm
Mach mal einen eigenen Thread dafür auf.
Hat ja mit dem Thema 'Verkaufe neueste Entwicklung... ' nix zu tun. -
@sauerm
Mach mal einen eigenen Thread dafür auf.
Hat ja mit dem Thema 'Verkaufe neueste Entwicklung... ' nix zu tun.@thomas-braun ja stimmt :relieved:
-
Falls jemand Probleme hat die Firware für den CC2652P zu finden:
Unter der Repository die auch oben verlinkt ist die FW "CC1352P2_CC2652P_launchpad_coordinator_[datum].zip" nehmen :) :+1: -
Falls jemand Probleme hat die Firware für den CC2652P zu finden:
Unter der Repository die auch oben verlinkt ist die FW "CC1352P2_CC2652P_launchpad_coordinator_[datum].zip" nehmen :) :+1: -
@earl80 Also, ich musste meine Geräte neu pairen, aber die IDs waren alle noch vorhanden. Ich musste also die Skripte nicht anpassen. Nach dem erneuten pairen lief direkt wieder alles :) :+1:
-> Allerdings hatte ich auch vergessen ein Backup vom Zigbee Adapter zu machen. Wenn man das einspielen kann, ist das natürlich noch besser :) -
@earl80 Also, ich musste meine Geräte neu pairen, aber die IDs waren alle noch vorhanden. Ich musste also die Skripte nicht anpassen. Nach dem erneuten pairen lief direkt wieder alles :) :+1:
-> Allerdings hatte ich auch vergessen ein Backup vom Zigbee Adapter zu machen. Wenn man das einspielen kann, ist das natürlich noch besser :) -
Ist das FW Update empfehlenswert? Was bringt es und was verpasse ich, wenn ich nicht update?
-
Frage bzgl. neuem Zigbee-Standard "Matter/Thread"
Hallo.
Ich bin etwas verwirrt, was den neuen, im nächsten Jahr kommenden "Zigbee-Standard" (
Chip/Matter/Thread) angeht.Bevor ich den Stick kaufe würde mich interessieren, wie es mit der Kompatibilität des Sticks dazu aussieht. Hier wurde ja schon öfters danach gefragt, aber leider gab es dazu bisher noch keine Kommentare.
Ist der Stick nun Kompatibel zu Matter/Thread, bzw. ist die Kompatibilität in Form eines Updates via USB möglich?
Oder spielt der neue Standard keine Rolle?
Sonst würde ich mit dem Kauf lieber abwarten und schauen, was sich da im nächsten Jahr so tut.
-
Frage bzgl. neuem Zigbee-Standard "Matter/Thread"
Hallo.
Ich bin etwas verwirrt, was den neuen, im nächsten Jahr kommenden "Zigbee-Standard" (
Chip/Matter/Thread) angeht.Bevor ich den Stick kaufe würde mich interessieren, wie es mit der Kompatibilität des Sticks dazu aussieht. Hier wurde ja schon öfters danach gefragt, aber leider gab es dazu bisher noch keine Kommentare.
Ist der Stick nun Kompatibel zu Matter/Thread, bzw. ist die Kompatibilität in Form eines Updates via USB möglich?
Oder spielt der neue Standard keine Rolle?
Sonst würde ich mit dem Kauf lieber abwarten und schauen, was sich da im nächsten Jahr so tut.
@w00dy sagte in [Verkaufe] Neueste Entwicklung: CC2652P Zigbee Stick:
Hallo.
Ich bin etwas verwirrt, was den neuen, im nächsten Jahr kommenden "Zigebee-Standard" (
Chip/Matter/Thread) angeht.Bevor ich den Stick kaufe würde mich interessieren, wie es mit der Kompatibilität des Sticks dazu aussieht. Hier wurde ja schon öfters danach gefragt, aber leider gab es dazu bisher noch keine Kommentare.
Ist der Stick nun Kompatibel zu Matter/Thread, bzw. ist die Kompatibilität in Form eines Updates via USB möglich?
Oder spielt der neue Standard keine Rolle?
Sonst würde ich mit dem Kauf lieber abwarten und schauen, was sich da im nächsten Jahr so tut.
Ja, der Stick ist laut TI mit Thread kompatibel.
Ja, sobald man passende Firmware hat, kann es via USB aufgespielt werden.
Ja, der neue Standard spielt noch keine Rolle.P.S.: Bitte für weiteren Diskussionen eine neue Thema aufmachen.
-
Mein Stick lässt sich nicht flashen.
Nach längerem Suchen bin ich drauf gekommen dass beide Taster auf dem PCB nicht funktionieren (schalten nicht durch). Ich hab dann die Kontakte gebrückt und schon hats geklappt..
Also falls jemand ähnliche Probleme hat, dann mal die Taster prüfen.. -
Mein Stick lässt sich nicht flashen.
Nach längerem Suchen bin ich drauf gekommen dass beide Taster auf dem PCB nicht funktionieren (schalten nicht durch). Ich hab dann die Kontakte gebrückt und schon hats geklappt..
Also falls jemand ähnliche Probleme hat, dann mal die Taster prüfen.. -
Mein Stick lässt sich nicht flashen.
Nach längerem Suchen bin ich drauf gekommen dass beide Taster auf dem PCB nicht funktionieren (schalten nicht durch). Ich hab dann die Kontakte gebrückt und schon hats geklappt..
Also falls jemand ähnliche Probleme hat, dann mal die Taster prüfen.. -
@tobi-0 alle Sticks werden von mir zusammen gebaut und geprüft und geflasht mit über die Taster, mehrmals.
Nur ein Taster muss gedrückt werden...Hi, ich versuche gerade die letzte Firmware aufzuspielen habe aber leider kein Erfolg. Ich erhalte nur die Meldung "Failed".
>Initiate access to target: COM3 using 2-pin cJTAG. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >ACK/NAK not received. Expected 0x00 0xCC or 0x00 0x33, received 0x42 0xF3. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >ACK/NAK not received. Expected 0x00 0xCC or 0x00 0x33, received 0x00 0xE1. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object.Kann mir wer helfen und mir sagen was ich falsch mache?
Die Buttons habe ich mehrfach gedrückt. Leider ohne Erfolg.Besten Dank.
-
Hi, ich versuche gerade die letzte Firmware aufzuspielen habe aber leider kein Erfolg. Ich erhalte nur die Meldung "Failed".
>Initiate access to target: COM3 using 2-pin cJTAG. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >ACK/NAK not received. Expected 0x00 0xCC or 0x00 0x33, received 0x42 0xF3. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object. >Initiate access to target: COM3 using 2-pin cJTAG. >ACK/NAK not received. Expected 0x00 0xCC or 0x00 0x33, received 0x00 0xE1. >Reading file: C:/Users/LaKl/Downloads/Zigbee Firmware Update/Firmware/CC1352P2_CC2652P_launchpad_coordinator_20221102/CC1352P2_CC2652P_launchpad_coordinator_20221102.hex. >Unknown record type: 3. >Reset target ... >Reset of target successful. >Initiate access to target: COM3 using 2-pin cJTAG. >No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again. If problem persists, check connection and baud rate. >Failed to create device object.Kann mir wer helfen und mir sagen was ich falsch mache?
Die Buttons habe ich mehrfach gedrückt. Leider ohne Erfolg.Besten Dank.
Support us
410
Online32.7k
Users82.3k
Topics1.3m
Posts