ATTENTION NEW USERS: Due to bot traffic, we are forced to manually approve registrations. We get thousands of bots trying to register, causing us to delete registrations in bulk with little ability to filter what is real or not. If you're having trouble getting approved, then send an email to ptrworkmails@gmail.com explaining that you are a real user. Use the same email you're trying to register with. Thank you.

Configuring Miyoo CFW buildroot make to enable TCP/IP networking and links browser with graphics

Windows CE, Android, Miyoo CFW, and other ARM systems discussions.
Post Reply
admin
Site Admin
Posts: 148
Joined: Wed Feb 22, 2023 6:51 am

Configuring Miyoo CFW buildroot make to enable TCP/IP networking and links browser with graphics

Post by admin »

*** The following notes are available as a text document download in the attachments ***

Configuring Miyoo CFW buildroot make to enable
TCP/IP networking and links browser with graphics

notes by Gemino Smothers
version 1

--------------------------------------------------

Note...

The order in which some things are checked sometimes matters.
Some things in this list may be already checked.
I may have forgotten some things.
Feel free to ask questions.

--------------------------------------------------

Getting started...

create a build dir and run the following:

Code: Select all

	git clone https://github.com/MiyooCFW/buildroot.git
	make miyoo_uclibc_defconfig
--------------------------------------------------

Configuring menuconfig...

Code: Select all

Target Packages -> Libraries -> Networking -> -*- libcurl -> SSL/TLS library to use ->

	(X) OpenSSL

Target Packages -> Networking Applications ->

	[*] links -> [*] use graphics
	[*] lynx

Target Packages -> Graphic Libraries and applications (graphic/text) -> [ ] X.org X Window System

	[ ] mudpdf

Target Packages -> Miyoo Packages -> Apps ->

	[ ] sdlbook

Target Packages -> Hardware handling ->

	[*] gpm
FOR WIFI:

Code: Select all

Target Packages -> Networking Applications ->

	[*] wireless-regdb
	[*] wireless tools

Target Packages -> Networking Applications -> [*] wpa_supplicant ->

	[*] Enable WPA3 support
	[*] Install wpa_cli binary

Target packages -> Hardware handling -> Firmware ->

	[*] linux-firmware -> WiFi firmware -> select  all options for MediaTek, Ralink, Realtek, etc
--------------------------------------------------

Configuring linux-menuconfig...

Code: Select all

[*] Networking Support -> Networking Options ->

	<*> Packet socket
	<*> Unix Socket Domains
	<*> Transport Layer Security support
	<*> PF_KEY sockets
	[*] TCP/IP networking
FOR RNDIS HOTSPOT TETHERING (TESTED + WORKING):

Code: Select all

File Systems -> [*] Pseudo filesystems ->

	{*} Userspace-driven configuration filesystem

Device Drivers -> [*] Network device support -> [*] USB Network adapters

	<*> Multi-Purpose USB Networking Framework
	<*> CDC Ethernet Support (smart devices such as cable modems)
	<*> Host for RNDIS and ActiveSync devices

Device Drivers -> [*] USB Support -> <*> USB Gadget Support ->

	<*> USB Gadget functions configurable though configfs
	[*] Abstract Control Model (CDC ACM)
	[*] Network Control Model (CDC NCM)
	[*] Ethernet Control Model (CDC ECM)
	[*] RNDIS
FOR WIFI:

Code: Select all

[*] Networking Support -> [*] Wireless ->

	<*> cfg80211 - wireless configuration API
	[*] cfg80211 wireless extensions compatiility
	<*> Generic IEEE 802.11 Networking Stack (mac80211)
	[*] Minstrel

Device Drivers -> [*] Network device support -> [*] Wireless LAN ->

	MediaTek, Ralink, etc 
	(only MediaTek and Ralink are tested as working,
	I had trouble with newer Realtek drivers)
--------------------------------------------------

Once compiled, create a file under mnt/apps/rndis.sh with the following:

Code: Select all

	mount -o remount,rw /
	udhcpc -i usb0 -p /tmp/udhcpc.pid
	sleep 2
	mount -o remount,ro /
Then create another called wifi.sh:

Code: Select all

	mount -o remount,rw /
	killall wpa_supplicant
	#echo -e 'network={\n ssid=""\n key_mgmt=NONE\n}' > /root/wpa_supplicant.conf
	#echo -e 'network={\n ssid=""\n psk=""\n}' > /root/wpa_supplicant.conf
	ifconfig wlan0 up
	wpa_supplicant -B -i wlan0 -D nl80211 -c /root/wpa_supplicant.conf
	udhcpc -i wlan0
	ping -c 4 8.8.8.8
	sleep 2
	mount -o remount,ro /
For open networks uncomment the line with key_mgmt=NONE and add networks SSID.
For closed networks uncomment the line with psk= and add your SSID and password.

Only wpa psk passwords are currently enabled.
Make links to both scrips with Gmenu2x and set "Terminal" to on to inspect the connection process.

--------------------------------------------------

Using RNDIS tethering...

Enable USB Host
Using a y cable and power source, connect your RNDIS enabled hotspot
Run rndis.sh

Code: Select all

	fail... you will see udhcpc: SIOCGIFINDEX: No such device

	success... you will see the connection establish
If everything is correct, you can now run telnet, wget, links, annd lynx.

Using WIFI...

***note we have only tested with MediaTek adapters, but Ralink should work too.
it's just the newer Realtek stuff that's problematic***

Enable USB Host
Using a y cable and power source, connect your WIFI adapter
Run wifi.sh

Code: Select all

	fail... you will see udhcpc: SIOCGIFINDEX: No such device

	success... you will see udhcpc start broadcasting until it connects
--------------------------------------------------

Creating shortcuts and running links...

For console programs like lynx, links, nano, etc you can create shell scripts with
the following edited to the name of the program you're making a shortcut to:

Code: Select all

	exec st -e links "$@"
Make one link this way for text based links. Then another called links-g.sh for graphical links.
You can put the scripts in /apps and make shortcuts to these with Gmenu2x.

For telnet and lynx, you must pass a default parameter from the gmenu2x or they will close.

For links-g.sh, (with graphics enabled) you must run the following:

Code: Select all

	killall -STOP gmenu2x
	openvt -w -c 1 -f -s links -g
	killall -CONT gmenu2x
This setup is picky about the mouse and keyboard used.

On an unpowered hub, the hid adapter must be placed before the wifi.
If the wifi is closer to the wire, it will not work.

A wired keyboard or mouse will work fine on their own, but not together with the wifi.
Same with a 2.4g mouse and keyboard on a shared dongle.

So far the only exception has been with the Rii style mini mouse and keyboard handhelds.
That works perfectly with the mouse and keyboard. The one I tested is a Miritz RT-MWK02.

Otherwise, hotswapping the mosue and keyboard works to move the mouse out of the way.

Another thing that worked if you don't have that specific rii style keyboard mentioned:

Hide the mouse cursor in the links source.

Edit arrow.inc in the compressed tar file for Links in the /dl directory.
Edit every hex value to 00000000. Then run sha256sum on the archive to get a new hash.
Then update package/links/links.hash. Once you have updted links, run:

make links-dirclean

make links
make
Attachments
Configuring Miyoo CFW buildroot make to enable TCPIP networking and links browser with graphics.txt
(6.09 KiB) Downloaded 1 time
Top
Post Reply

Return to “ARM (Advanced RISC Machine)”