I followed the steps in the Linux Gateway Project Zero example (https://dev.ti.com/tirex/explore/node?node=AIpEfnGDfOZ6k-P9SF11iA__pTTHBmu__LATEST) using a Beagle Bone Black and two LUANCHXL-CC1352P1 dev boards. For the co-processor, the example says to use a prebuilt hex file for the example located at C:\ti\<sdk_path>\examples\rtos\<your_target_board>\ti154stack\hexfiles\coprocessor_<your_target_board>_tirtos_ccs.hex For the CC1352P1 LaunchPad, however, there is no hexfiles directory, so I used the coprocessor_cc1352lp_tirtos_ccs.hex file, which was located in the hexfiles directory for the CC1352R1 LaunchPad. Considering the file name itself contained the P designator, I assumed that this binary would work for both versions. When I ran into the problems described below, I loaded the source for the CC1352P1 LaunchPad co-processor example in the Code Composer Resource Explorer and flashed the co-processor from Code Composer, but I encountered the same results:
When I run ./run_demo.sh on the BBB host, the collector and gateway applications start, but there are two issues:
1) In the terminal, the output of the script says: On your host, launch your browser using: but without indicating a local address to navigate to. I know that the device's ip address is 192.168.1.7, though, so I went to 192.168.1.7:1310 and found the gateway server page was in fact running. I don't know if this is just a parsing bug in the script or if it's related to the next issue below.
2) The example script did not give any complains about not being able to connect to the co-processor, but it doesn't seem to show up as a node in the network. In the example, a dot is shown in the network window, which I assume represents the co-processor, as there are two dots shown in the example after the sensor connects. When I try to connect the sensor, following the instructions in the "Adding sensor device(s) to the network" subsection, the sensor never seems to join. I opened a serial monitor to the sensor and found that each time I attempt to connect it, it immediately goes from Waiting... status to Orphaned status.
Any idea why this might be happening?
