Linux Linaro Installation: Connect RK3066 Board with RT5370 WiFi Module and UART Interface

Question

Hi. If not this section, sorry. I would also like to point out right away that I am a very beginner in Linux. I have a board with the RK3066 processor on which I installed the linux system, namely Linaro, downloaded from this website I communicate via the UART interface connected to the laptop...

viaxa · Accepted Answer

Maybe one of these will fit. rt2x00.7z Download (50.11 kB)

PDT · Accepted Answer

The errors are caused by: 1. libncurses5-dev package not installed 2. it is necessary to set the date, e.g. date 20171120 Then the initial configuration (due to missing config file): make multi_v7_defconfig and proper: make menuconfig kisses

PDT · Accepted Answer

I have previously signaled a problem with the time setting. This error is signaled when 'make' finds a file whose modification time is 'in the future'. Signals detection of system time rollback. Boards equipped with hardware RTC read the start time during startup. In this case you have to manually set the 'date'. After installing the network it will not be a problem, 'ntpdate' will be loaded from the net.

md37 · Answer

There should be a Makefile in that folder. Send its content.

Kamil 1 · Answer

Hello.

Thank you for your interest in the topic.
Here is the contents of the makefile

#

# Copyright (c) 2007-2012 Luis R. Rodriguez 
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#
# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

export KMODDIR?= updates
KMODDIR_ARG:= "INSTALL_MOD_DIR=$(KMODDIR)"
ifneq ($(origin KLIB), undefined)
KMODPATH_ARG:= "INSTALL_MOD_PATH=$(KLIB)"
else
export KLIB:= /lib/modules/$(shell uname -r)
endif
export KLIB_BUILD ?=	$(KLIB)/build
export MAKE

DESTDIR?=

ifneq ($(KERNELRELEASE),)

-include $(COMPAT_CONFIG)
include $(COMPAT_CONFIG_CW)

NOSTDINC_FLAGS := -I$(M)/include/ \
	-include $(M)/include/linux/compat-2.6.h \
	$(CFLAGS)

obj-y := compat/

obj-$(CONFIG_COMPAT_RFKILL) += net/rfkill/

ifeq ($(BT),)
obj-$(CONFIG_COMPAT_WIRELESS) += net/wireless/ net/mac80211/
obj-$(CONFIG_COMPAT_WIRELESS_MODULES) += drivers/net/wireless/

obj-$(CONFIG_COMPAT_NET_USB_MODULES) += drivers/net/usb/

obj-$(CONFIG_COMPAT_NETWORK_MODULES) += drivers/net/ethernet/atheros/
obj-$(CONFIG_COMPAT_NETWORK_MODULES) += drivers/net/ethernet/broadcom/

obj-$(CONFIG_COMPAT_VAR_MODULES) += drivers/ssb/
obj-$(CONFIG_COMPAT_VAR_MODULES) += drivers/bcma/
obj-$(CONFIG_COMPAT_VAR_MODULES) += drivers/misc/eeprom/

ifeq ($(CONFIG_STAGING_EXCLUDE_BUILD),)
endif

endif

obj-$(CONFIG_COMPAT_BLUETOOTH) += net/bluetooth/
obj-$(CONFIG_COMPAT_BLUETOOTH_MODULES) += drivers/bluetooth/

else

export PWD :=	$(shell pwd)

# The build will fail if there is any space in PWD.
ifneq (,$(findstring $() ,$(PWD)))
$(error "The path to this compat-drivers directory has spaces in it." \
	"Please put it somewhere where there is no space")
endif

export CFLAGS += \
-DCOMPAT_BASE="\"$(shell cat $(PWD)/.compat_base)\"" \
-DCOMPAT_BASE_TREE="\"$(shell cat $(PWD)/.compat_base_tree)\"" \
-DCOMPAT_BASE_TREE_VERSION="\"$(shell cat $(PWD)/.compat_base_tree_version)\"" \
-DCOMPAT_PROJECT="\"Compat-drivers\"" \
-DCOMPAT_VERSION="\"$(shell cat $(PWD)/.compat_version)\""

# These exported as they are used by the scripts
# to check config and compat autoconf
export COMPAT_CONFIG_CW=$(PWD)/config.mk
export COMPAT_CONFIG=$(PWD)/.config
export CONFIG_CHECK=$(PWD)/.config.mk_md5sum.txt
export COMPAT_AUTOCONF=include/linux/compat_autoconf.h
export CREL=$(shell cat $(PWD)/.compat_version)
export CREL_PRE:=.compat_autoconf_
export CREL_CHECK:=$(PWD)/$(CREL_PRE)$(CREL)

all: modules

$(COMPAT_CONFIG): ;

modules: $(CREL_CHECK)
	$(MAKE) -C $(KLIB_BUILD) M=$(PWD) modules
	@touch $@

bt: $(CREL_CHECK)
	+@./scripts/check_config.sh
	$(MAKE) -C $(KLIB_BUILD) M=$(PWD) BT=TRUE modules
	@touch $@

# We use a CREL_CHECK variable which will depend on the environment used to
# build. If the environment requirements change it forces a reconfiguration
# check. This means we force a new reconfiguration check if a the user gets a
# new updates of compat-drivers or when the user updates the $(COMPAT_CONFIG)
# file.
# XXX: add kernel target to the CREL_CHECK mix, this would ensure we also
# reconfigure and build again fresh if we detect a new target kernel is
# being used.
$(CREL_CHECK):
	@# Force to regenerate compat autoconf
	+@./compat/scripts/gen-compat-config.sh > $(COMPAT_CONFIG)
	@rm -f $(CONFIG_CHECK)
	+@./scripts/check_config.sh
	@md5sum $(COMPAT_CONFIG_CW) > $(CONFIG_CHECK)
	@touch $@

btinstall: btuninstall bt-install-modules

bt-install-modules: bt
	$(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) BT=TRUE \
		modules_install
	@/sbin/depmod -ae
	@echo
	@echo Now run:
	@echo
	@echo sudo make btunload:
	@echo
	@echo And then load the needed bluetooth modules. If unsure reboot.
	@echo

btuninstall:
	@# New location, matches upstream
	@rm -rf $(KLIB)/$(KMODDIR)/net/bluetooth/
	@rm -rf $(KLIB)/$(KMODDIR)/drivers/bluetooth/
	@# Lets only remove the stuff we are sure we are providing
	@# on the misc directory.
	@/sbin/depmod -ae
	@echo

btclean:
	$(MAKE) -C /lib/modules/$(shell uname -r)/build M=$(PWD) BT=TRUE clean
	@rm -f $(CREL_PRE)*

install: uninstall install-modules install-scripts

install-modules: modules
	$(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \
		modules_install
	@./scripts/update-initramfs

install-scripts:
	@# All the scripts we can use
	@mkdir -p $(DESTDIR)/usr/lib/compat-drivers/
	@install scripts/modlib.sh	$(DESTDIR)/usr/lib/compat-drivers/
	@install scripts/madwifi-unload	$(DESTDIR)/usr/sbin/
	@# This is to allow switching between drivers without blacklisting
	@install scripts/athenable	$(DESTDIR)/usr/sbin/
	@install scripts/b43enable	$(DESTDIR)/usr/sbin/
	@install scripts/iwl-enable	$(DESTDIR)/usr/sbin/
	@install scripts/athload	$(DESTDIR)/usr/sbin/
	@install scripts/b43load	$(DESTDIR)/usr/sbin/
	@install scripts/iwl-load	$(DESTDIR)/usr/sbin/
	@if [ $(shell modinfo ath_pci > /dev/null 2>&1 && echo 1) ]; then \
		echo -n "Note: madwifi detected, we're going to disable it. " ;\
		echo "If you would like to enable it later you can run:" ;\
		echo " sudo athenable madwifi" ;\
		echo ;\
		echo Running athenable ath5k...;\
		$(DESTDIR)/usr/sbin/athenable ath5k ;\
	fi
	@if [ $(shell modinfo iwl4965 > /dev/null 2>&1 && echo 1) ]; then \
		echo ;\
		echo -n "Note: iwl4965 detected, we're going to disable it. " ;\
		echo "If you would like to enable it later you can run:" ;\
		echo " sudo iwl-load iwl4965" ;\
		echo ;\
		echo Running iwl-enable iwlagn...;\
		$(DESTDIR)/usr/sbin/iwl-enable iwlagn ;\
	fi
	@if [ $(shell modinfo iwlagn > /dev/null 2>&1 && echo 1) ] \
	 && [ $(shell modinfo iwlwifi > /dev/null 2>&1 && echo 1) ]; then \
		echo ;\
		echo -n "Note: iwlagn detected, we're going to disable it. " ;\
		echo "If you would like to enable it later you can run:" ;\
		echo " sudo iwl-load iwlagn" ;\
		echo ;\
		echo Running iwl-enable iwlwifi...;\
		$(DESTDIR)/usr/sbin/iwl-enable iwlwifi ;\
	fi
	@# If on distributions like Mandriva which like to
	@# compress their modules this will find out and do
	@# it for you. Reason is some old version of modutils
	@# won't know mac80211.ko should be used instead of
	@# mac80211.ko.gz
	@./scripts/compress_modules
	@# Mandrake doesn't have a depmod.d/ conf file to prefer
	@# the updates/ dir which is what we use so we add one for it
	@# (or any other distribution that doens't have this).
	@./scripts/check_depmod
	@# Udev stuff needed for the new compat_firmware_class.
	@./compat/scripts/compat_firmware_install
	@/sbin/depmod -a
	@echo 
	@echo Now run:
	@echo 
	@echo sudo make unload to unload all: wireless, bluetooth and ethernet modules
	@echo sudo make wlunload to unload wireless modules
	@echo sudo make btunload to unload bluetooth modules
	@echo
	@echo Run sudo modprobe 'driver-name' to load your desired driver. 
	@echo If unsure reboot.
	@echo

uninstall:
	@# New location, matches upstream
	@rm -rf $(KLIB)/$(KMODDIR)/compat/
	@rm -rf $(KLIB)/$(KMODDIR)/net/mac80211/
	@rm -rf $(KLIB)/$(KMODDIR)/net/rfkill/
	@rm -rf $(KLIB)/$(KMODDIR)/net/wireless/
	@rm -rf $(KLIB)/$(KMODDIR)/drivers/ssb/
	@rm -rf $(KLIB)/$(KMODDIR)/drivers/net/usb/
	@rm -rf $(KLIB)/$(KMODDIR)/drivers/net/wireless/
	@rm -rf $(KLIB)/$(KMODDIR)/drivers/staging/
	@rm -rf $(KLIB)/$(KMODDIR)/drivers/net/atl*
	@find $(KLIB)/$(KMODDIR)/drivers/net/ -name "alx*.ko" -o -name "atl*.ko" 2>/dev/null |xargs rm -f
	@# Lets only remove the stuff we are sure we are providing
	@# on the misc directory.
	@rm -f $(KLIB)/$(KMODDIR)/drivers/misc/eeprom/eeprom_93cx6.ko*
	@rm -f $(KLIB)/$(KMODDIR)/drivers/misc/eeprom_93cx6.ko*
	@rm -f $(KLIB)/$(KMODDIR)/drivers/net/b44.ko*
	@/sbin/depmod -a
	@./scripts/update-initramfs
	@echo 

clean:
	@if [ -d net -a -d $(KLIB_BUILD) ]; then \
		$(MAKE) -C $(KLIB_BUILD) M=$(PWD) clean ;\
	fi
	@rm -f $(CREL_PRE)*
unload:
	@./scripts/unload.sh

btunload:
	@./scripts/btunload.sh

wlunload:
	@./scripts/wlunload.sh


.PHONY: all clean install uninstall unload btunload wlunload modules bt Makefile

endif

clean-files += Module.symvers Module.markers modules modules.order
clean-files += $(CREL_CHECK) $(CONFIG_CHECK) $(COMPAT_CONFIG)

md37 · Answer

There is no load in the file, so this error pops up. Send the contents of /etc/apt/sources.list Do you have an Ethernet socket?

Kamil 1 · Answer

This is about the ect folder on the system drive? Because if it is to be a folder where this makefile is (so in this folder with drivers, there is no such folder there).

md37 · Answer

If you have a / in front of any path, it means it's in the root of your system drive.

Kamil 1 · Answer

I do not have an Ethernet socket, so I would probably deal with it. Here is the content of the file that a colleague mentioned, there is not much of it:

deb http://ports.ubuntu.com/ubuntu-ports/ trusty main universe
deb-src http://ports.ubuntu.com/ubuntu-ports/ trusty main universe

PDT · Answer

Kernel 3.0.36+ Sneaky Weasel is too old. Current versions of many programs will not work on it due to the lack of some new system functions (e.g. memfd). It is best to compile the latest stable kernel longterm from www.kernel.org. For a marsboard it shouldn't be difficult, at least the dts is ready. There is a WiFi driver in 4.x kernels: CONFIG_RT2800USB_RT53XX rt2800usb.c: {USB_DEVICE (0x148f, 0x5370)}

Kamil 1 · Answer

Thank you for your message and advice Unfortunately, I have never dealt with the Linux kernel replacement, so it probably won't work out very well. But I will read out of curiosity how it is done

Kamil 1 · Answer

I am trying to compile the kernel in the newest version, 4.9.63. I use this guide: http://www.linuxportal.pl/wpisy/prosta-kompilacja-jadra-id182976
So I downloaded the kernel archive from https://www.kernel.org/, unpacked it, and placed it in the / usr / src / directory. Then I follow step 6 of this tutorial and that's where the problems start. I skip the "make clean" and "make mrproper" commands (I also executed them the first time, but it started to warn, so I uploaded a fresh system image and on the second attempt to replace the kernel I skipped these commands).
The problem appears already with the command "cp / boot / config-`uname -r` ./.config" because I do not have any configuration file in the boot directory.
And running "make menuconfig" only gives me this:

Kamil 1 · Answer

In fact, the date was not set, but it is a bit of a surprise to me that one of the mistakes was something so trivial

As far as installing libncurses5-dev is concerned, I am not able to install this package automatically because I don't have internet, so I'm at the starting point ...

Kamil 1 · Answer

I am still tired of this topic. I am currently in the process of manually reinstalling the "libncurses5-dev" mentioned by my colleague PDT. I downloaded the libncurses5-dev.deb package on a computer from some Debian website. Installing it with the command "dpkg" caused an error related to the lack of another package - libtinfo5. This one needs something else etc. etc. I skipped this installation on foot and downloaded the whole ncurses package (5.9-10) and if I understand correctly it should contain everything that is needed for this "libncurses5-dev", with him. The package is in the form of an archive that I unpacked.
I found a guide on the Internet on how to install something like this - first the file or the "configure" command is called, then "make" at the end of "make install". When I gave the make command, everything went fine, beautiful, flooding the consoles with successive steps for a few minutes. Unfortunately, an error finally appeared:

make [1]: warning: Clock skew detected. Your build may be incomplete.
make [1]: Leaving directory `/mnt/karta/ncurses-5.9/c++ '
make: warning: Clock skew detected. Your build may be incomplete.

Anyone know what this means?

Kamil 1 · Answer

Yes, I know my friend mentioned it before and I took it to heart, I set the time with the date command. It is nice that the error I wrote about appeared, so it probably won't be a problem of clock settings.

Added after 3 [hours] 23 [minutes]:

Ok, success. Once again I uploaded a fresh system to this board and I did everything in order, including setting the time and installing the ncurses-5.9 package and this time it worked - after issuing the command "make menuconfig" this kernel configuration window appeared

I have such a question now, my colleague PDT mentioned the preconfiguration with the command "make multi_v7_defconfig", resulting in a .config file
If now in this kernel configuration window, I load this generated configuration using the "load" option, will I not have to modify this kernel? However, would it be appropriate to change something? If you do without modifications, it's better for me because I can spoil something

Added after 27 [minutes]:

I am trying to compile the kernel without modifying the kernel configuration.
In some tutorial I read that you should give the command " make all "to compile the kernel. I do so too, except that I redirect the result of the compilation to the file" result.txt "- I think that it will speed up the process a bit because the processor takes care of the compilation itself and not an additional push of the entire compilation run through the terminal the physical UART) Unfortunately, an error appeared on the good morning ... here it is:

Forgive me for not dealing with these errors myself, but I do not have such knowledge, unfortunately ...

PDT · Answer

I can see that you are making some progress and that for the first time there are also mistakes.
NOTE: Many tips available on the net concern cross-compilation of the kernel (compile on PC and run on ARM). This is not the case.

But shortly to the point, instead of make multi_v7_defconfig, you 'd better create a .config file with the contents:
https://raw.githubusercontent.com/powermcu/ro...arm/configs/marsboard_rk3066_sdcard_defconfig
This is the kernel 3.0.8+ configuration customized for this marsboard . Most of the settings have not changed.

We compile with commands:
make zImage fixed kernel, you need to copy it from arch / arm / boot / zImage to / boot (this is my case, the place depends on the loader)
make modules loadable modules
make modules_install install modules to target / lib / modules / ...

Kamil 1 · Answer

I have a question, after creating this .config file with this content from the link, should I run "make menuconfig" and load this file there using the load option?

If I do so, that I use the command "make menuconfig" and load the .config file with the load option, then exiting this configuration window by double pressing ESC, the question appears whether I want to save the current configuration, so I save. Then I run "make zImage" and get errors

However, if I create this .config file with this content from the link and no longer use the "make menuconfig" command, I just run "make zImage" immediately then I have some additional configuration process in the terminal which looks like this:

The question is which method is correct?

PDT · Answer

From kernel 3.0.8 to 4.xx a few options have been added / changed, the first way takes them to default values, usually good ones.

These two lines need to be removed from .config, they are for cross-compiling:
CONFIG_CROSS_COMPILE = "arm-linux-gnueabi-"
CONFIG_LOCALVERSION = "+"

Kamil 1 · Answer

Thanks for your involvement and help, I deleted these two entries from the .config file, however I still have a problem with this: /

Maybe I will write again how I do it - I created a .config file with the content that is in the link posted by my friend. By the way, this file has the header:
#
# Automatically generated make config: don't edit
# Linux / arm 3.0.8 Kernel Configuration
#
Then I execute the command "make menuconfig" and immediately load this file. Without modifying anything, I exit this editor and confirm that I want to save the changes.
Now the file header looks like this:
#
# Automatically generated file; DO NOT EDIT.
# Linux / arm 4.9.63 Kernel Configuration
#
So you can see that the file has been overwritten, so probably some new entries have been added to the file related to this kernel version 4.9.63
Then I remove from the resulting .config file, these two entries related to cross-compilation. And compile with "make zImage" command.

As a result, I get

At first it throws ngcc bugs, but goes on and asks ... what I deleted ...

Or maybe it will be easier to do cross compilation on PC?

Linux Linaro Installation: Connect RK3066 Board with RT5370 WiFi Module and UART Interface

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Topic summary