This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Z-Stack Linux Gateway BeagleBone 搭配的BBB Debian版本問題.

Other Parts Discussed in Thread: Z-STACK, CC2531, CC2530, CC2652R

HI YK

這幾天試了一下Z-Stack Linux Gateway

再去爬了一下文. 發現你有提到只在Debian 7.8版本( IN BeagleBone Black ) 正常

我現在試了Debian 10.3版( IN BeagleBone Black )執行:

(BeagleBoard.org Debian Buster IoT Image 2020-04-06)

"sudo ./zigbeeHAgw beaglebone"

也是一樣一堆錯( BeagleBone Black 有上網)

"connect: Connection refused
[ZSTACKZNP_SRVR/MAIN] ERROR: ERROR: signal 11 was trigerred:
[ZSTACKZNP_SRVR/MAIN] ERROR:   Fault address: (nil)
[ZSTACKZNP_SRVR/MAIN] ERROR:   Fault reason: address not mapped to object
[ZSTACKZNP_SRVR/MAIN] ERROR: Stack trace unavailable
[ZSTACKZNP_SRVR/MAIN] ERROR: Executing original handler...
./zigbeeHAgw: line 351: 29620 Segmentation fault      $ZLSZNP_CMD
ZLSZNP started (pid 29620) at Mon 07 Sep 2020 02:05:37 PM UTC
[NWK_MGR/MAIN] :  there are 2 args
[NWK_MGR/MAIN] :  argv[0] = ./NWKMGR_SRVR_arm
[NWK_MGR/MAIN] :  argv[1] = 127.0.0.1:2536
connect: Connection refused
[NWK_MGR/MAIN] ERROR: ERROR: signal 11 was trigerred:
[NWK_MGR/MAIN] ERROR:   Fault address: (nil)
[NWK_MGR/MAIN] ERROR:   Fault reason: address not mapped to object
[NWK_MGR/MAIN] ERROR: Stack trace unavailable
[NWK_MGR/MAIN] ERROR: Executing original handler...
./zigbeeHAgw: line 407: 29623 Segmentation fault      $NWKMGR_CMD $NWKMGR_RESTART_FLAG
NETWORK MANAGER started (pid 29623) at Mon 07 Sep 2020 02:05:38 PM UTC
connect: Connection refused
connect: Connection refused
[GATEWAY/MAIN] ERROR: ERROR: signal 11 was trigerred:
[GATEWAY/MAIN] ERROR:   Fault address: (nil)
[GATEWAY/MAIN] ERROR:   Fault reason: address not mapped to object
[GATEWAY/MAIN] ERROR: Stack trace unavailable
[GATEWAY/MAIN] ERROR: Executing original handler...
./zigbeeHAgw: line 378: 29626 Segmentation fault      $GATEWAY_SERVER_CMD
GATEWAY SERVER started (pid 29626) at Mon 07 Sep 2020 02:05:40 PM UTC
connect: Connection refused
connect: Connection refused
[OTASRVR/MAIN] ERROR: ERROR: signal 11 was trigerred:
[OTASRVR/MAIN] ERROR:   Fault address: (nil)
[OTASRVR/MAIN] ERROR:   Fault reason: address not mapped to object
[OTASRVR/MAIN] ERROR: Stack trace unavailable
[OTASRVR/MAIN] ERROR: Executing original handler...
./zigbeeHAgw: line 438: 29629 Segmentation fault      $OTA_SERVER_CMD
OTA SERVER started (pid 29629) at Mon 07 Sep 2020 02:05:42 PM UTC
starting tracker with our pid ./zigbeeHAgw and pid list 29615 29620 29626 29629
"

只能用Debian 7.8版本或是官網的am335x-evm-linux-06.03.00.106.img

( IN BeagleBone Black )了嗎??

謝謝.

  • 好像7.8是OK的,以下是Debian 7.8版本執行
    "sudo ./zigbeeHAgw beaglebone"
    出來的訊息:

    running zigbeegw.scr on an ARM
    resetting beaglebone black
    sleeping 6 seconds after reset... Using serial port: /dev/ttyACM0
    zbSocProcessRpc: CMD0:41, CMD1:80, not handled
    Received System version.
    Transport Protocol Version: 2
    Product ID: 0
    Software Release: 2.6.1
    Software Revision: 38724
    done
    Starting the ZigBee gateway subsystem
    deviceKey = 0 (0 )
    devPath = '/dev/ttyACM0'
    logPath = './NpiLnxLog.txt'
    ... freeing memory (ret 0)
    Port: 2533
    Following IP addresses are available:

    IPv4: interface: lo IP Address 127.0.0.1
    IPv4: interface: usb0 IP Address 192.168.7.2
    IPv6: interface: lo IP Address ::1
    IPv6: interface: eth0 IP Address 2001:b400:e2d3:4c40:6a3:16ff:feba:7b39
    IPv6: interface: eth0 IP Address 2001:b400:e254:68d4:6a3:16ff:feba:7b39
    IPv6: interface: eth0 IP Address fe80::6a3:16ff:feba:7b39
    IPv6: interface: usb0 IP Address fe80::7811:8aff:feae:488a
    The socket will listen on the following IP addresses:

    IPv4: 0.0.0.0
    IPv6: ::
    0.0.0.0 means it will listen to all available IP address

    waiting for first connection on #3...
    NPI started (pid 2074) at Sun Mar 1 21:12:27 UTC 2015
    Connected to #5.(127.0.0.1 / ::b8b3:cbbe:b4:cbbe)
    ZLSZNP started (pid 2080) at Sun Mar 1 21:12:31 UTC 2015
    [NWK_MGR/MAIN] : there are 2 args
    [NWK_MGR/MAIN] : argv[0] = ./NWKMGR_SRVR_arm
    [NWK_MGR/MAIN] : argv[1] = 127.0.0.1:2536
    [NWK_MGR/MAIN] : ************************************************
    [NWK_MGR/MAIN] : * Network Manager Server v1.0.1 *
    [NWK_MGR/MAIN] : * The following are the avaible key commands: *
    [NWK_MGR/MAIN] : * Exit Program. - q *
    [NWK_MGR/MAIN] : ************************************************

    NETWORK MANAGER started (pid 2086) at Sun Mar 1 21:12:32 UTC 2015
    [GATEWAY/MAIN] :
    [GATEWAY/MAIN] : ************************************************
    [GATEWAY/MAIN] : * Gateway Server v1.0.1 *
    [GATEWAY/MAIN] : * The following are the avaible key commands: *
    [GATEWAY/MAIN] : * Exit Program. - q *
    [GATEWAY/MAIN] : ************************************************

    GATEWAY SERVER started (pid 2093) at Sun Mar 1 21:12:34 UTC 2015
    [OTASRVR/MAIN] :
    [OTASRVR/MAIN] : ************************************************
    [OTASRVR/MAIN] : * OTA Upgrade Server 1.0.1 *
    [OTASRVR/MAIN] : * The following are the avaible key commands: *
    [OTASRVR/MAIN] : * Exit Program. - q *
    [OTASRVR/MAIN] : ************************************************

    OTA SERVER started (pid 2101) at Sun Mar 1 21:12:36 UTC 2015
    starting tracker with our pid ./zigbeeHAgw and pid list 2074 2080 2093 2101
    ===================================================
    tracking 4 pids, 2074 2080 2093 2101
    when we see something missing we will send a SIGUSR2 to pid 2009
  • 我沒有在Debian 10.3版上測試過、建議還是用7.8
  • 建议按照这里的版本,其他没有验证过:dev.ti.com/.../node
  • HI YK

    這是我測LINUX GATEWAY按了大O要嘗試OTA的LOG

    好像前面都對,後面出現了一個什麼未註冊的狀態機器??這個是錯誤嗎??

    (ZED用的是2652R開發板加SDK 的 zed_sw_ota_client 專案)

    謝謝

     


  • 沒遇過這樣的問題,你有照使用手冊的步驟測試嗎?你的Zigbee GW是自己build的還是預編譯好的?
  • HI YK

    LINUX GW 都是用原來的,沒有再BUILD過.

    用BBB+CC2531做LINUX GW

    就照說明把PC上SDK解出來的 z-stack_linux_gateway_arm_binaries_<version>.tar SCP到BBB裡
    解壓縮.

    做了cp protobuf/libprotobuf-c.so.0 /usr/lib/
    再把sample_app_ota.cfg放到/root/下

    執行./zigbeeHAgw beaglebone
    和 ./start_application

    再照說明選擇剛加入 zed_sw_ota_client 裝置的按下大O做OTA
    就變這樣子.

    謝謝.
  • 你sample_app_ota.cfg的內容有沒有設置好?

  • HI YK

    有啊,sample_app_ota.cfg裡面

    第一個是要OTA的.ZIGBEE檔案的路徑嘛
    第二個是要更新的個數就照原來寫1
    第三個是要更新的裝置的IEEE ADDRESS.
    都有改好.

    手冊是這樣寫的.

    另外有參考別人的錯誤,有COPY一份丟到/BOOT下面.

    謝謝.
  • 但是user guide 有提到說

    "To initiate an “OTA Upgrade” you will need to do the following:
    Program up a SmartRF + CC2530 as an example OTA client."

    所以一定要SmartRF + CC2530 , cc2652r + zed_sw_ota_client不行??
  • 沒有一定要CC2530、cc2652r + zed_sw_ota_client應該要可以

  • HI YK

    那就奇怪了,因為我有拿ZED_LIGHT來試連到 Linux Gateway 看看.
    發現 Linux Gateway 的 ACTION --> ON/OFF 跟LVL的動作
    好像是針對ZED LIGHT這裡專案的.
    因為確實看ZED_LIGHT的板子上的LED是有動作的.

    但是也有試試看對 ZED_LIGHT 下 OTA 看看,
    結果出來的LOG是和ZED_SW_OTA_CLIENT專案一模一樣的.

    都是最後出現一個 "未註冊的狀態機器"
    那可能是 Linux Gateway OTA那邊沒有處理好.這個要再試下.......

    該不會是 Linux Gateway 內建的.ZIGBEE檔案不能用吧??
    因為我試 OTA 時 .ZIGBEE檔案 是用內建的,不是用自己的.

    謝謝.
  • .ZIGBEE檔案不能用內建的啊,你應該要用自己的

  • HI YK

    有了, .ZIGBEE檔案換成自己的就有了.

    但是也太奇怪了, LOG訊息完全一模一樣,還是停在"未註冊的狀態機器"

    以為又失敗了,

    是想說沒事等一下,等了大概十分鐘後才跳出OTA成功的LOG訊息出來.

    完全沒有進度可看呀??完全搞不懂它 OTA 有沒有在跑.

  • 跳出OTA成功的LOG訊息出來不就是成功了

  • HI YK

    是成功了,但完全沒提示在進行中.....
    最後還是停在未註冊的狀態機器上.....
    我以為不行了, 是等一陣子後才出現的......

    我以為會有提示或進度條之類的.
    都沒有.
  • 我記得是不會有提示或進度條之類的
  • HI YK

    剛剛注意到一件事情就是
    LINUX GATEWAY OTA完之後
    ZED的UART丟出來的CUI訊息
    有提示檔案版本,確實OTA完之後的

    "Current File Version" 變 000003 了

    奇怪的是之前用OTA SERVER(PC上面做OTA的軟體)
    也是同一個.ZIGBEE檔哦. 更新完"Current File Version"還是不變.
    不過硬體動作發現 ZED 還是有OTA到.
    這樣子是....??
  • 可能OTA SERVER(PC上面做OTA的軟體)有bug吧
  • HI YK

    這個也要再試下.
    因為說"有OTA到"是因為OTA前
    的ZED_SW_OTA_Client我都燒錄原始專案的版本

    然後更新過去的0003版是有驅動OLED的FW.

    有時用OTA_SERVER丟完後, ZED_SW_OTA_Client板上的
    OLED是點亮了.
    但是UART CUI顯示的檔案版本還是停在
    0001我就很納悶.

    所以那個ZED入網未顯示也許也是OTA SERVER的BUG ??

    就是有時候試一試ZED_SW_OTA_Client入網後看UART CUI
    顯示確實是"IN THE NETWORK"了

    PID也拿到了,確實是OTA SERVER上的那個PID

    也有ZED短位址了.這樣應該有入網了吧.

    但是OTA SERVER那邊就是不會
    顯示這個ZED出來,所以也無法OTA.

    謝謝.

  • 其實TI提供的這些軟件工具是給你開發參考的,要真的商品化,你還是得自行花力氣去修改才行