Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

IOT2040 mPCI gpio access

Created by: mmitton at: 2/8/2021 11:45 AM (2 Replies)

Rating (0)

Thanks 0

3 Entries

2/8/2021 11:45 AM	Rate (0)
mmitton Posts: 4 Rating: (0)	Hi, I am trying to get a RAK2247 module integrated into an IOT2040 gateway. I have installed the RAK2247 mPCI module and the lora-gateway software: https://github.com/Lora-net/lora_gateway I can get the packet-logger application to run, but it stops with the error: loragw_pkt_logger: INFO: found global configuration file global_conf.json, trying to parse it loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters loragw_pkt_logger: INFO: lorawan_public 1, clksrc 1 loragw_pkt_logger: INFO: radio 0 enabled (type SX1257), center frequency 867500000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0 loragw_pkt_logger: INFO: radio 1 enabled (type SX1257), center frequency 868500000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0 loragw_pkt_logger: INFO: LoRa multi-SF channel 0 enabled, radio 1 selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 1 enabled, radio 1 selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 2 enabled, radio 1 selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 3 enabled, radio 0 selected, IF -400000 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 4 enabled, radio 0 selected, IF -200000 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 5 enabled, radio 0 selected, IF 0 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 6 enabled, radio 0 selected, IF 200000 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa multi-SF channel 7 enabled, radio 0 selected, IF 400000 Hz, 125 kHz bandwidth, SF 7 to 12 loragw_pkt_logger: INFO: LoRa standard channel enabled, radio 1 selected, IF -200000 Hz, 250000 Hz bandwidth, SF 7 loragw_pkt_logger: INFO: FSK channel enabled, radio 1 selected, IF 300000 Hz, 125000 Hz bandwidth, 50000 bps datarate loragw_pkt_logger: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000000 loragw_pkt_logger: INFO: found local configuration file local_conf.json, trying to parse it loragw_pkt_logger: INFO: local_conf.json does not contain a JSON object named SX1301_conf loragw_pkt_logger: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters loragw_pkt_logger: INFO: gateway MAC address is configured to AA555A0000000101 loragw_pkt_logger: ERROR: failed to start the concentrator There is a rest script that needs the gpio number assigned to pin 22 of the mPCI card in order to reset the concentrator on start. Can anyone please tell me where can I find the mPCI pinout - gpio mapping, or how to access pin 22 of the mPCI interface? Thank you
mmitton Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

2/9/2021 3:18 PM	Rate (0)
bergmanu Platinum Member Joined: 4/28/2015 Last visit: 11/12/2024 Posts: 3345 Rating: (379)	Hi, if your card was recognized then it should appear under /sys/bus/pci/devices. Is there something else as 00:00:00.0? Best regards!
	Not working for IOT2050 support anymore from March 1st, 2024. I really enjoyed the time supporting you! :)
Suggestion To thank Quote Answer

2/10/2021 1:46 PM	Rate (0)
mmitton Posts: 4 Rating: (0)	Hi Bergmanu, Thank you for your response. Here is the listing for PCI devices and ttyUSB* interfaces WITHOUT the card installed. root@iot2000:~# ls -lrth /sys/bus/pci/devices total 0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:15.0 -> ../../../devices/pci0000:00/0000:00:15.0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.7 -> ../../../devices/pci0000:00/0000:00:14.7 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.6 -> ../../../devices/pci0000:00/0000:00:14.6 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.5 -> ../../../devices/pci0000:00/0000:00:14.5 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.4 -> ../../../devices/pci0000:00/0000:00:14.4 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.3 -> ../../../devices/pci0000:00/0000:00:14.3 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.2 -> ../../../devices/pci0000:00/0000:00:14.2 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.1 -> ../../../devices/pci0000:00/0000:00:14.1 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:14.0 -> ../../../devices/pci0000:00/0000:00:14.0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:00.0 -> ../../../devices/pci0000:00/0000:00:00.0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:02:00.0 -> ../../../devices/pci0000:00/0000:00:17.1/0000:02:00.0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:1f.0 -> ../../../devices/pci0000:00/0000:00:1f.0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:17.1 -> ../../../devices/pci0000:00/0000:00:17.1 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:17.0 -> ../../../devices/pci0000:00/0000:00:17.0 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:15.2 -> ../../../devices/pci0000:00/0000:00:15.2 lrwxrwxrwx 1 root root 0 Feb 9 14:36 0000:00:15.1 -> ../../../devices/pci0000:00/0000:00:15.1 root@iot2000:~# ls -lrth /dev/ttyUSB* ls: cannot access '/dev/ttyUSB': No such file or directory Here is the listing for PCI devices and ttyUSB interfaces WITH the card installed. root@iot2000:~# ls -lrth /sys/bus/pci/devices total 0 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:02:00.0 -> ../../../devices/pci0000:00/0000:00:17.1/0000:02:00.0 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:1f.0 -> ../../../devices/pci0000:00/0000:00:1f.0 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:17.1 -> ../../../devices/pci0000:00/0000:00:17.1 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:17.0 -> ../../../devices/pci0000:00/0000:00:17.0 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:15.2 -> ../../../devices/pci0000:00/0000:00:15.2 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:15.1 -> ../../../devices/pci0000:00/0000:00:15.1 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:15.0 -> ../../../devices/pci0000:00/0000:00:15.0 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.7 -> ../../../devices/pci0000:00/0000:00:14.7 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.6 -> ../../../devices/pci0000:00/0000:00:14.6 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.5 -> ../../../devices/pci0000:00/0000:00:14.5 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.4 -> ../../../devices/pci0000:00/0000:00:14.4 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.3 -> ../../../devices/pci0000:00/0000:00:14.3 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.2 -> ../../../devices/pci0000:00/0000:00:14.2 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.1 -> ../../../devices/pci0000:00/0000:00:14.1 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:14.0 -> ../../../devices/pci0000:00/0000:00:14.0 lrwxrwxrwx 1 root root 0 Feb 9 14:30 0000:00:00.0 -> ../../../devices/pci0000:00/0000:00:00.0 root@iot2000:~# ls -lrth /dev/ttyUSB* crw-rw---- 1 root dialout 188, 1 Feb 9 14:30 /dev/ttyUSB1 crw-rw---- 1 root dialout 188, 0 Feb 9 14:30 /dev/ttyUSB0 The card (RAK2247) https://docs.rakwireless.com/Product-Categories/WisLink/RAK2247/Datasheet/ powers up and the OS creates the /dev/ttyUSB interfaces. The manufacturer recommends being able to toggle the PERST# (pin 22) signal in order to communicate with the concentrator card. Is there a way to do this? Thank you
mmitton Posts: 4 Rating: (0)	Last edited by: CS Moderator at: 02/10/2021 13:48:46 Import from private message
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

SIMATIC IOT2000 Hardware

Follow us on