[SC206][Yocto] Add python3-pip package to image results in lack of recoveryfs.img

Cesar_lasec · April 9, 2024, 5:42pm

I was able to build an image without adding any packages. After that, i’ve tried to build new images with some packages, which I added to poky/qti-conf/local.conf.

When I’ve tried to build the image without python3-pip, the building process succeeded. Nevertheless, when I try to add python3-pip and run:

source build.sh
build-qti-robotics-med-image

the building process fails trying to execute the task do_create_recoveryfs_ext4 of the qti-recovery-image.bb recipe.

Then I’ve tried to build the image with:

source build.sh
bitbake qti-robotics-med-image

And the compilation ended successfully, but in the folder build-qti-distro-rb-debug/tmp-glibc/deploy/images/qrbx210-rbx/qti-robotics-med-image there is no recoveryfs.img

keven.wu-Q · April 23, 2024, 8:06am

Please add to this path:
poky/meta-qti-bsp/recipes-products/images/qti-robotics-med-image.bb

Sachin_1296 · December 25, 2024, 12:37pm

Hi @keven.wu-Q,

Like pytohn3 i wants to add openssh-server so that i can connect device over wifi to share files with it. How can i add it?

keven.wu-Q · December 26, 2024, 1:29am

reply:
Our SDK already has openssh service by default, you don’t need to add it. The command to connect to wifi is as follows:

/ # wpa_cli

wpa_cli v2.5-devel

This software may be distributed under the terms of the BSD license.

See README for more details.

Selected interface 'wlan0'

Interactive mode

> scan

OK

<3>CTRL-EVENT-SCAN-STARTED

> wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CN

<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CN

<3>CTRL-EVENT-SCAN-RESULTS

<3>CTRL-EVENT-NETWORK-NOT-FOUND

> scan_results

bssid / frequency / signal level / flags / ssid

7c:d9:a0:0f:9a:32 5260 -53 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

7c:d9:a0:0f:9a:30 5260 -53 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

08:4f:0a:a7:32:90 5260 -60 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

08:4f:0a:a7:32:92 5260 -61 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

10:c1:72:1d:8b:50 5260 -63 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

10:c1:72:1d:8b:52 5260 -64 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

b8:e3:b1:12:72:62 5260 -65 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

b8:e3:b1:12:72:60 5260 -65 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

7c:d9:a0:0f:9a:23 2452 -44 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

7c:d9:a0:0f:9a:22 2452 -44 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF-2.4G

7c:d9:a0:0f:9a:20 2452 -44 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

08:4f:0a:a7:32:82 2432 -47 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF-2.4G

08:4f:0a:a7:32:80 2432 -47 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

48:01:c5:5d:4a:0c 2412 -50 [WPA2-PSK-CCMP][ESS] 12345

b8:e3:b1:12:72:53 2452 -59 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

b8:e3:b1:12:72:52 2452 -59 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF-2.4G

b8:e3:b1:12:72:50 2452 -59 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

10:c1:72:1d:8b:42 2432 -55 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF-2.4G

10:c1:72:1d:8b:40 2432 -55 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

44:6a:2e:13:cc:70 5260 -75 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

44:6a:2e:13:cc:72 5260 -76 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

7c:d9:a0:0f:96:a2 2412 -71 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF-2.4G

7c:d9:a0:0f:96:a3 2412 -72 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

f4:b7:8d:85:d4:b0 5260 -80 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

b8:e3:b1:12:7c:20 5785 -81 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

f4:b7:8d:85:d4:b2 5260 -81 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

10:c1:72:1d:32:c0 2432 -74 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

7c:d9:a0:0f:96:a0 2412 -74 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

b8:e3:b1:12:7c:22 5785 -82 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

b8:e3:b1:12:7a:10 2452 -78 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer-2.4G

f4:b7:8d:85:d4:32 5180 -89 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

f4:b7:8d:85:d4:30 5180 -90 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

44:6a:2e:12:0c:72 5180 -91 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

44:6a:2e:12:0c:70 5180 -91 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][ESS] Quectel-Customer

10:c1:72:1d:32:d2 5785 -93 [WPA-EAP-CCMP][WPA2-EAP-CCMP][ESS] Quectel-HF

> add_network

0

> add_network 1

3

> set_network 3 ssid "Quectel-Customer"

OK

> set_network 3 psk "Customer-Quectel"

OK

> enable_network 3

OK

<3>CTRL-EVENT-SCAN-STARTED

<3>CTRL-EVENT-SCAN-RESULTS

> wlan0: Trying to associate with SSID 'Quectel-Customer'

<3>Trying to associate with SSID 'Quectel-Customer'

> eap_proxy: eap_proxy_notify_config

eap_proxy: eap_proxy_allowed_method

wlan0: Associated with 7c:d9:a0:0f:9a:30

<3>Associated with 7c:d9:a0:0f:9a:30

> wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0

<3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0

> wlan0: WPA: Key negotiation completed with 7c:d9:a0:0f:9a:30 [PTK=CCMP GTK=TKIP]

<3>WPA: Key negotiation completed with 7c:d9:a0:0f:9a:30 [PTK=CCMP GTK=TKIP]

> wlan0: CTRL-EVENT-CONNECTED - Connection to 7c:d9:a0:0f:9a:30 completed [id=3 id_str=]

<3>CTRL-EVENT-CONNECTED - Connection to 7c:d9:a0:0f:9a:30 completed [id=3 id_str=]

> wlan0: WPA: Group rekeying completed with 7c:d9:a0:0f:9a:30 [GTK=TKIP]

<3>WPA: Group rekeying completed with 7c:d9:a0:0f:9a:30 [GTK=TKIP]

> wlan0: WPA: Group rekeying completed with 7c:d9:a0:0f:9a:30 [GTK=TKIP]

<3>WPA: Group rekeying completed with 7c:d9:a0:0f:9a:30 [GTK=TKIP]

> status

bssid=7c:d9:a0:0f:9a:30

freq=5260

ssid=Quectel-Customer

id=3

mode=station

pairwise_cipher=CCMP

group_cipher=TKIP

key_mgmt=WPA2-PSK

wpa_state=COMPLETED

ip_address=10.66.178.122

p2p_device_address=00:0a:f5:43:11:6c

address=00:0a:f5:43:11:6c

uuid =97b2bdeb-80a7-559c-8d76-b0f0ac40a881
> quit

/ # ifconfig

bridge0 Link encap:Ethernet HWaddr 4E:5E:D0:B3:7B:6F

inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0

inet6 addr: fe80::4c5e:d0ff:feb0:786c/64 Scope:Link

UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:192 errors:0 dropped:0 overruns:0 frame:0

TX packets:192 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1

RX bytes:12368 (12.0 KiB) TX bytes:12368 (12.0 KiB)

rmnet_data0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

inet addr:10.64.88.16 Mask:255.255.255.224

UP RUNNING MTU:1500 Metric:1

RX packets:19815 errors:0 dropped:0 overruns:0 frame:0

TX packets:92682 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:3163833 (3.0 MiB) TX bytes:24623631 (23.4 MiB)

rmnet_ipa0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

UP RUNNING MTU:2000 Metric:1

RX packets:16798 errors:0 dropped:0 overruns:0 frame:0

TX packets:92682 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:3401613 (3.2 MiB) TX bytes:25365087 (24.1 MiB)

wlan0 Link encap:Ethernet HWaddr 00:0A:F5:43:11:6C

inet addr:10.66.178.122 Bcast:10.66.183.255 Mask:255.255.248.0

inet6 addr: fe80::20a:f5ff:fe43:116c/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:58 errors:0 dropped:0 overruns:0 frame:0

TX packets:25 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:16580 (16.1 KiB) TX bytes:2776 (2.7 KiB)

/ # ping baidu.com

PING baidu.com (110.242.68.66) 56(84) bytes of data.

64 bytes from 110.242.68.66: icmp_req=1 ttl=53 time =70.6 ms

64 bytes from 110.242.68.66: icmp_req=2 ttl=53 time =70.1 ms

64 bytes from 110.242.68.66: icmp_req=3 ttl=53 time =70.1 ms

64 bytes from 110.242.68.66: icmp_req=4 ttl=53 time =69.3 ms

Sachin_1296 · December 26, 2024, 4:53am

Hi @keven.wu-Q

Thanks for your quick response.

I am able to connect wifi as per steps suggested by you.

But my aim is to connect device over ssh so that i can access files of device(like sftp) so for that in my host PC i use filezilla(ssh client).

I got device IP address using “ifconfig”.
r

root@qrbx210-rbx:~# ifconfig
bridge0   Link encap:Ethernet  HWaddr 5A:D6:BF:3D:EF:99  
          inet addr:192.168.225.1  Bcast:192.168.225.255  Mask:255.255.255.0
          inet6 addr: fe80::58d6:bfff:fe3a:ec96/64 Scope:Link
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:164 (164.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:164 errors:0 dropped:0 overruns:0 frame:0
          TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:14760 (14.4 KiB)  TX bytes:14760 (14.4 KiB)

wlan0     Link encap:Ethernet  HWaddr 58:DB:09:14:67:BD  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::5adb:9ff:fe14:67bd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2833 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2385 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:109125 (106.5 KiB)  TX bytes:122342 (119.4 KiB)

But i am not able to connect filezilla(ssh client) with below configuration.

i am also facing issue with “apt” command. can you please suggest how to add support of “apt” command.

root@qrbx210-rbx:~# 
root@qrbx210-rbx:~# apt
-sh: apt: not found
root@qrbx210-rbx:~#

Can you please help resolve this?

keven.wu-Q · December 26, 2024, 5:17am

Reply：It is not recommended to install apt. Since sc206e is not an Ubuntu system, using the apt tool to pull the Ubuntu source will cause many package dependency issues. This will lead to more and more problems in the future.
Regarding ssh, you must ensure that your PC and the SC206E LAN are in the same network segment before you can log in.

Sachin_1296 · December 26, 2024, 5:47am

Hi @keven.wu-Q

Thanks for your response.

My device and my host pc are in same LAN still i am facing this issue.

my device IP.

root@qrbx210-rbx:/# ifconfig                                                    
bridge0   Link encap:Ethernet  HWaddr 5A:D6:BF:3D:EF:99                         
          inet addr:192.168.225.1  Bcast:192.168.225.255  Mask:255.255.255.0    
          inet6 addr: fe80::58d6:bfff:fe3a:ec96/64 Scope:Link                   
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1                    
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0                    
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0                  
          collisions:0 txqueuelen:1000                                          
          RX bytes:0 (0.0 B)  TX bytes:164 (164.0 B)                            
                                                                                
lo        Link encap:Local Loopback                                             
          inet addr:127.0.0.1  Mask:255.0.0.0                                   
          inet6 addr: ::1/128 Scope:Host                                        
          UP LOOPBACK RUNNING  MTU:65536  Metric:1                              
          RX packets:170 errors:0 dropped:0 overruns:0 frame:0                  
          TX packets:170 errors:0 dropped:0 overruns:0 carrier:0                
          collisions:0 txqueuelen:1000                                          
          RX bytes:15300 (14.9 KiB)  TX bytes:15300 (14.9 KiB)                  
                                                                                
wlan0     Link encap:Ethernet  HWaddr 58:DB:09:14:67:BD                         
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0      
          inet6 addr: fe80::5adb:9ff:fe14:67bd/64 Scope:Link                    
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                    
          RX packets:3299 errors:0 dropped:0 overruns:0 frame:0                 
          TX packets:2841 errors:0 dropped:1 overruns:0 carrier:0               
          collisions:0 txqueuelen:3000                                          
          RX bytes:159779 (156.0 KiB)  TX bytes:172635 (168.5 KiB)

My host PC ip.

sachin@sachin-ThinkCentre-M70t-Gen-4:~$ ifconfig

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.102  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::eaca:c4df:a21:2f2d  prefixlen 64  scopeid 0x20<link>
        ether b0:47:e9:18:40:84  txqueuelen 1000  (Ethernet)
        RX packets 552846  bytes 390775886 (390.7 MB)
        RX errors 0  dropped 2718  overruns 0  frame 0
        TX packets 262118  bytes 80334630 (80.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Then what could be possible reasone.

keven.wu-Q · December 26, 2024, 7:15am

Check if port 22 is in listening state.
netstat -anptul query shows 127.0.0.1:22, indicating that it is being listened.

image954×268 84.7 KB
Find the sshd.socket file and delete 127.0.0.1:

image1166×274 20.7 KB

Sachin_1296 · December 26, 2024, 12:37pm

Hi @keven.wu-Q

Thanks for your quick response.

After doing the above changes should i need to rebuild SDK?

One new thing that I observed is that the file system(rootfs) is currently read only so how can I change it to read-write mode?

keven.wu-Q · December 27, 2024, 1:08am

Yes, you need to recompile
File permission modification path: poky/meta-qti-bsp/conf/machine/qrbx210-rbx.conf
Add noinitrd rw attribute

Sachin_1296 · December 27, 2024, 8:12am

Hi @keven.wu-Q ,

Thanks for your quick response.

The SSH server is working but I had to add a password in the device for my user.

I am also able to read and write files on the device.

Can you share a guide or document that can i follow for quectel yocto development?

keven.wu-Q · December 27, 2024, 8:36am

For example, add the root user and change the root password to 123456:

Sachin_1296 · December 27, 2024, 9:19am

Hi @keven.wu-Q

Thanks for your response.

Is there any guide or document that I can refer for the development of quectel device in yocto?

keven.wu-Q · December 27, 2024, 9:31am

We have official documents, you can log in to our FTP to get.

Sachin_1296 · December 30, 2024, 5:12am

Hi @keven.wu-Q

Thanks for your quick response.

Can you share how I can add support for SPI because I did not find the SPI driver and test utility.

keven.wu-Q · December 30, 2024, 6:06am

SPI documentation is in the peripheral documentation

Sachin_1296 · December 30, 2024, 6:35am

Hi @keven.wu-Q
Thanks for your quick response.

Sachin_1296 · December 30, 2024, 11:03am

Hi @keven.wu-Q

How can i map gpio385 to an actual gpio number like gpio ?

keven.wu-Q · December 31, 2024, 2:25am

There is also an introduction to GPIO in the peripheral documentation, you can refer to it.

Sachin_1296 · January 2, 2025, 5:41am

Hi @keven.wu-Q

How can i add libgpiod support?