@mpous I have re-pushed and now works, few weeks back I had this same issue with RAK2245 runnin on a RPI4, great work.
Now I got a new RAK2287, and the repository balenalabs/basicstation is specifically made for RAK2245.
I had a chat with Jose Marcelino, and tried to build using “corecell” as platform without luck, also tried doing other code changes and it worked up to have the similar error reported on this thread. Any ideas will be appreciated, here is the log, and I forked the repo for reference is GitHub - rony-vargas/basicstation: LoRa Basics™ Station - The LoRaWAN Gateway Software
2020-09-14 15:40:00.515 [any:INFO] ./lns-ttn/tc.trust:
14.09.20 10:40:00 (-0500) main cert. version : 3
14.09.20 10:40:00 (-0500) main serial number : 0A:01:41:42:00:00:01:53:85:73:6A:0B:85:EC:A7:08
14.09.20 10:40:00 (-0500) main issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
14.09.20 10:40:00 (-0500) main subject name : C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
14.09.20 10:40:00 (-0500) main issued on : 2016-03-17 16:40:46
14.09.20 10:40:00 (-0500) main expires on : 2021-03-17 16:40:46
14.09.20 10:40:00 (-0500) main signed using : RSA with SHA-256
14.09.20 10:40:00 (-0500) main RSA key size : 2048 bits
14.09.20 10:40:00 (-0500) main basic constraints : CA=true, max_pathlen=0
14.09.20 10:40:00 (-0500) main key usage : Digital Signa2020-09-14 15:40:00.515 [AIO:INFO] tc has no key+cert configured - running server auth only
14.09.20 10:40:00 (-0500) main 2020-09-14 15:40:00.661 [TCE:INFO] Connecting to INFOS: wss://lns.us.thethings.network:443
14.09.20 10:40:01 (-0500) main 2020-09-14 15:40:01.441 [TCE:INFO] Infos: dca6:32ff:fe36:5aa2 muxs-::0 wss://lns.us.thethings.network:443/traffic/eui-DCA632FFFE365AA2
14.09.20 10:40:01 (-0500) main 2020-09-14 15:40:01.441 [AIO:DEBU] [3] ws_close reason=1000
14.09.20 10:40:01 (-0500) main 2020-09-14 15:40:01.441 [AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed
14.09.20 10:40:01 (-0500) main 2020-09-14 15:40:01.441 [AIO:DEBU] [3] WS connection shutdown…
14.09.20 10:40:01 (-0500) main 2020-09-14 15:40:01.442 [any:INFO] ./lns-ttn/tc.trust:
14.09.20 10:40:01 (-0500) main cert. version : 3
14.09.20 10:40:01 (-0500) main serial number : 0A:01:41:42:00:00:01:53:85:73:6A:0B:85:EC:A7:08
14.09.20 10:40:01 (-0500) main issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
14.09.20 10:40:01 (-0500) main subject name : C=US, O=Let’s Encrypt, CN=Let’s Encrypt Authority X3
14.09.20 10:40:01 (-0500) main issued on : 2016-03-17 16:40:46
14.09.20 10:40:01 (-0500) main expires on : 2021-03-17 16:40:46
14.09.20 10:40:01 (-0500) main signed using : RSA with SHA-256
14.09.20 10:40:01 (-0500) main RSA key size : 2048 bits
14.09.20 10:40:01 (-0500) main basic constraints : CA=true, max_pathlen=0
14.09.20 10:40:01 (-0500) main key usage : Digital Signa2020-09-14 15:40:01.442 [AIO:INFO] tc has no key+cert configured - running server auth only
14.09.20 10:40:01 (-0500) main 2020-09-14 15:40:01.581 [TCE:VERB] Connecting to MUXS…
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.222 [TCE:VERB] Connected to MUXS.
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.356 [RAL:WARN] Ignoring unsupported/unknown field: antenna_gain
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.357 [SYS:VERB] rinit.sh: Forked, waiting…
14.09.20 10:40:02 (-0500) main SX1302 reset through GPIO25…
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.890 [SYS:INFO] Process rinit.sh (pid=178) completed
14.09.20 10:40:02 (-0500) main ERROR: Failed to stop TX trigger
14.09.20 10:40:02 (-0500) main ERROR: Failed to stop TX trigger
14.09.20 10:40:02 (-0500) main ERROR: failed to close I2C device (err=-1)
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.891 [RAL:INFO] Lora gateway library version: Version: 1.0.5;
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.891 [RAL:VERB] Connecting to device: /dev/spidev0.0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.891 [RAL:DEBU] SX130x txlut table (16 entries)
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.891 [RAL:VERB] SX1302 txlut 0: rf_power=12 pa_gain=0 pwr_idx=15
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 1: rf_power=13 pa_gain=0 pwr_idx=16
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 2: rf_power=14 pa_gain=0 pwr_idx=17
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 3: rf_power=15 pa_gain=0 pwr_idx=19
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 4: rf_power=16 pa_gain=0 pwr_idx=20
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 5: rf_power=17 pa_gain=0 pwr_idx=22
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 6: rf_power=18 pa_gain=1 pwr_idx=1
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 7: rf_power=19 pa_gain=1 pwr_idx=2
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 8: rf_power=20 pa_gain=1 pwr_idx=3
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 9: rf_power=21 pa_gain=1 pwr_idx=4
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 10: rf_power=22 pa_gain=1 pwr_idx=5
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 11: rf_power=23 pa_gain=1 pwr_idx=6
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 12: rf_power=24 pa_gain=1 pwr_idx=7
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 13: rf_power=25 pa_gain=1 pwr_idx=9
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 14: rf_power=26 pa_gain=1 pwr_idx=11
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 txlut 15: rf_power=27 pa_gain=1 pwr_idx=14
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 rssi_tcomp: coeff_a=0.000 coeff_b=0.000 coeff_c=20.410 coeff_d=2162.560 coeff_e=0.000
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 rxrfchain 0: enable=1 freq=904.3MHz rssi_offset=-166.000000 type=5 tx_enable=1
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 rxrfchain 1: enable=1 freq=905.0MHz rssi_offset=-166.000000 type=5 tx_enable=0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 0: enable=1 rf_chain=0 freq=-400000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 1: enable=1 rf_chain=0 freq=-200000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 2: enable=1 rf_chain=0 freq=0 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 3: enable=1 rf_chain=0 freq=200000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 4: enable=1 rf_chain=1 freq=-300000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 5: enable=1 rf_chain=1 freq=-100000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 6: enable=1 rf_chain=1 freq=100000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 7: enable=1 rf_chain=1 freq=300000 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 8: enable=1 rf_chain=0 freq=300000 bw=6 SF=8 sync_word=0/0 [STD] Explicit header
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] SX1302 ifchain 9: enable=0 rf_chain=0 freq=0 bw=0 SF=0 sync_word=0/0
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:VERB] Station device: /dev/spidev0.0 (PPS capture disabled)
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:ERRO] Concentrator start failed: lgw_start
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.892 [RAL:ERRO] ral_config failed with status 0x08
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.893 [any:ERRO] Closing connection to muxs - error in s2e_onMsg
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.893 [AIO:DEBU] [3] ws_close reason=1000
14.09.20 10:40:02 (-0500) main 2020-09-14 15:40:02.893 [AIO:DEBU] Echoing close - reason=1000
14.09.20 10:40:03 (-0500) main 2020-09-14 15:40:03.025 [AIO:DEBU] [3|WS] Server sent close: reason=1000
14.09.20 10:40:03 (-0500) main 2020-09-14 15:40:03.025 [AIO:DEBU] [3] WS connection shutdown…
14.09.20 10:40:03 (-0500) main 2020-09-14 15:40:03.026 [TCE:VERB] Connection to MUXS closed in state -1
14.09.20 10:40:03 (-0500) main 2020-09-14 15:40:03.026 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
Today i receive my RAK 2287 so we will work on the newest balena Basics Station application compatible with the newest LoRa chip. I will keep you updated @ronyvargas
Meanwhile @ronyvargas as an idea the library sx1302 on the 2287 is completely different, could you please check how to change it on the repository? Keep me updated if you succeed!
I validated that SX1302 on RAK2287 has two SX1250 front ends, I initially changed the repository to match this config using the https://github.com/Lora-net/sx1302_hal, but this didn’t start concentrator, it reported the error I sent above, so I am reading the development reference from Semtech/Basicstation and see if I need to change something else. The balena part works fine after I made the changes, it is the core SX1302 still on going work.
I’ll keep you posted if succeed
Hey @ronyvargas i’m trying to change the platform to corecell. Actually changing the Dockerfile.template platform doesn’t work because there is no rpi tooling available, so i’m changing the setup.gmk, but i get this error:
[main] [arm-linux-gnueabihf] CC …/bin/station
[main] …/lib/liblgw1302.a(loragw_debug.o): In function dbg_generate_random_payload': [main] loragw_debug.c:(.text+0x260): undefined reference to tinymt32_init’
[main] collect2: error: ld returned 1 exit status
[main] make[1]: * […/bin/station] Error 1
[main] make: * [s-all] Error 2
[main]
[main] …/…/makefile.s2core:44: recipe for target ‘…/bin/station’ failed
[main] make[1]: Leaving directory ‘/usr/src/app/build-rpi-std/s2core’
[main] makefile:39: recipe for target ‘s-all’ failed
Hi @mpous, I got that same error, and it is because of a missing reference, the way around I found to pass this error, and not to stuck with other debugging was to add this line:
CFLAGS += -DNODEBUG
I added this in the Patch file to be applied for RPI platform, at the end it looked like this:
Hi @mpous
Here’s what I found from the start, just to put them in order:
When the container starts [start.sh], it call for files in this directory examples/live-s2.sm.tc/ , and so for the RAK2287, since procedure is different, some changes also need to happen in the following files/directories:
move the files rinit.sh, start-station.sh, reset_gw.sh from examples/corecell/ and the folder lns-ttn to examples/live-s2.sm.tc/ - I know this can be better done, but I made this at the very beginning.
Modify the reset_gw.sh to introduce the changes I mentioned in the previous post. reset_gw.sh
Modify the start.sh to remove the reset procedure that was specific to RAK2245 and doesn’t work same way in RAK2287.
Modify the start.sh to update tc.uri and tc.trust inside folder lns-ttn instead of current dir. -This shouldn’t make big difference because is just setting the certs, and the lns-ttn folder already have these files.
Modify start.sh to call the correct radio start procedure ./start-station.sh -l ./lns-ttn
I found this necessary because the station.conf in the examples/live-s2.sm.tc folder is made specific to SX1301, and folder lns-ttn has the right one for SX1302
See this file: start.sh
Modify the setup.gmk to change rpi platform to use lgw1302, see this file: setup.gmk
Create a V1.0.5-rpi.patch in folder deps/lgw1302 . This file: V1.0.5-rpi.patch
balena push [app]
I believe I didn’t miss any step, I tried to compile them from my previous notes.
Let me know if this works.
Rony V.
Hello! the HHRs team plus @ronyvargas helped to made it possible to merge the code of the Basics Station LoRa gateway with balena for RAK 2245 and RAK2287.
Hi @mpous, to set all this up I had to use 2 apps one for the RAK2245 and one for RAK2287, do you believe I can now switch with a Single APP running both versions, just by overriding the MODEL variable to the target device?
So I wanted to provide an update. I managed to get datadog & basicstation successfully running on my RPI4. Getting very close to that ideal gateway we discussed.
Datadog works like a charm, but strangely l seem to be encountering the same certs problem as mentioned at the very top of this thread.
@ronyvargas@mpous presumably you guys didn’t get this error with the updated repo? Could it be related to multi-container? I doubt it personally…
25.09.20 14:08:21 (-0400) basicstation 2020-09-25 18:08:20.969 [AIO:INFO] tc has no key+cert configured - running server auth only
25.09.20 14:08:21 (-0400) basicstation 2020-09-25 18:08:21.516 [TCE:INFO] Connecting to INFOS: wss://lns.us.thethings.network:443
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [TCE:INFO] Infos: 242:acff:fe11:2 muxs-::0 wss://lns.us.thethings.network:443/traffic/eui-0242ACFFFE110002
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [AIO:DEBU] [3] ws_close reason=1000
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [AIO:DEBU] Echoing close - reason=1000
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [AIO:DEBU] [3] WS connection shutdown...
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [any:INFO] ./tc.trust:
25.09.20 14:08:22 (-0400) basicstation cert. version : 3
25.09.20 14:08:22 (-0400) basicstation serial number : 44:AF:B0:80:D6:A3:27:BA:89:30:39:86:2E:F8:40:6B
25.09.20 14:08:22 (-0400) basicstation issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
25.09.20 14:08:22 (-0400) basicstation subject name : O=Digital Signature Trust Co., CN=DST Root CA X3
25.09.20 14:08:22 (-0400) basicstation issued on : 2000-09-30 21:12:19
25.09.20 14:08:22 (-0400) basicstation expires on : 2021-09-30 14:01:15
25.09.20 14:08:22 (-0400) basicstation signed using : RSA with SHA1
25.09.20 14:08:22 (-0400) basicstation RSA key size : 2048 bits
25.09.20 14:08:22 (-0400) basicstation basic constraints : CA=true
25.09.20 14:08:22 (-0400) basicstation key usage : Key Cert Sign, CRL Sign
25.09.20 14:08:22 (-0400) basicstation 2020-09-25 18:08:22.055 [AIO:INFO] tc has no key+cert configured - running server auth only
Hi @barryjump is that the first time that you launch the Container or everytime is sending those messages?
In my case I see those messages just once, when the container starts, (either after stop or restart), I also see a lot of Time sync error messages, same as your first posts, but still it works just fine.
I read the documentation from Semtech, and I believe this feature is to do a Client-Side Certificate authentication, but I am not sure that TTN supports it, so I guess it will show that messages.
Here is sample from my logs showing the same, but after that it works just fine:
25.09.20 14:13:41 (-0500) main 2020-09-25 19:13:41.494 [any:INFO] ./tc.trust:
25.09.20 14:13:41 (-0500) main cert. version : 3
25.09.20 14:13:41 (-0500) main serial number : 44:AF:B0:80:D6:A3:27:BA:89:30:39:86:2E:F8:40:6B
25.09.20 14:13:41 (-0500) main issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
25.09.20 14:13:41 (-0500) main subject name : O=Digital Signature Trust Co., CN=DST Root CA X3
25.09.20 14:13:41 (-0500) main issued on : 2000-09-30 21:12:19
25.09.20 14:13:41 (-0500) main expires on : 2021-09-30 14:01:15
25.09.20 14:13:41 (-0500) main signed using : RSA with SHA1
25.09.20 14:13:41 (-0500) main RSA key size : 2048 bits
25.09.20 14:13:41 (-0500) main basic constraints : CA=true
25.09.20 14:13:41 (-0500) main key usage : Key Cert Sign, CRL Sign
25.09.20 14:13:41 (-0500) main 2020-09-25 19:13:41.494 [AIO:INFO] tc has no key+cert configured - running server auth only
25.09.20 14:13:41 (-0500) main 2020-09-25 19:13:41.913 [TCE:INFO] Connecting to INFOS: wss://lns.us.thethings.network:443
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.811 [TCE:INFO] Infos: dca6:32ff:fe36:fb6d muxs-::0 wss://lns.us.thethings.network:443/traffic/eui-DCA632FFFE36FB6D
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.811 [AIO:DEBU] [3] ws_close reason=1000
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.811 [AIO:DEBU] Echoing close - reason=1000
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.811 [AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.811 [AIO:DEBU] [3] WS connection shutdown…
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.812 [any:INFO] ./tc.trust:
25.09.20 14:13:42 (-0500) main cert. version : 3
25.09.20 14:13:42 (-0500) main serial number : 44:AF:B0:80:D6:A3:27:BA:89:30:39:86:2E:F8:40:6B
25.09.20 14:13:42 (-0500) main issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
25.09.20 14:13:42 (-0500) main subject name : O=Digital Signature Trust Co., CN=DST Root CA X3
25.09.20 14:13:42 (-0500) main issued on : 2000-09-30 21:12:19
25.09.20 14:13:42 (-0500) main expires on : 2021-09-30 14:01:15
25.09.20 14:13:42 (-0500) main signed using : RSA with SHA1
25.09.20 14:13:42 (-0500) main RSA key size : 2048 bits
25.09.20 14:13:42 (-0500) main basic constraints : CA=true
25.09.20 14:13:42 (-0500) main key usage : Key Cert Sign, CRL Sign
25.09.20 14:13:42 (-0500) main 2020-09-25 19:13:42.812 [AIO:INFO] tc has no key+cert configured - running server auth only
@ronyvargas you’re absolutely right, I didn’t look hard enough. I can’t completely confirm it however I think my problem is on TTN, not balena.
I was having a bit of trouble a while back so I deleted the gateway from TTN assuming that it would let me start from scratch, but every time I add it back it shows some old config. I’ll bet TTN doesn’t actually remove the gateway record from their database when you do that in the UI, so there may be some crossed wires now.
The balena device has been online for hours and properly configured, but TTN is not seeing it most likely because of the above reason.
I’m not planning on using TTN anyway, rather a private Chirpstack install, but I was hoping to test the new repo here quickly on TTN.
Another quick question, is there any specific reason the containers are built using the stretch image instead of the newer buster the one I have in the App that I started to modify is running buster without issues, but wanted to validate if there is any specific reason like a known issue/bug before going and put both devices within the same app.
@mpous Unfortunately a restart did not fix. @ronyvargas had mentioned he thinks its because of the folder structure, specifically for tc file, when I tried multiple container build. In fact I’m almost certain (even if unrelated to above) that my compose file is incorrect. It builds & deploys fine, but there were some deps folders that someone else had mentioned are likely getting screwy during the process.
I’d image there would be quite a few people who’d like basicstation multi-container with device variables available for a chirpstack connection. Maybe we can make a group effort?
