Olimex - User contributions [en]

LIMA

2019-08-29T07:57:21Z

StefanM: /* Building */

= LIMA driver =

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

Depending on distribution, your meson version may be outdated. You can use pip
to install the latest version
* Update meson
# apt install -y python3-pip
# pip3 install meson

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build and install the sources
# ninja -C build
# ninja -C build install

== Usage ==
=== Without X ===

You can test the driver with kmscube
# apt-get install -y kmscube

Run and test
# kmscube
......

=== With X ===

LIMA

2019-08-29T07:57:00Z

StefanM: /* Building */

= LIMA driver =

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

Depending on distribution, your meson version may be outdated. You can use pip
to install the latest version
* Update meson
# apt install -y pip3
# pip3 install meson

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build and install the sources
# ninja -C build
# ninja -C build install

== Usage ==
=== Without X ===

You can test the driver with kmscube
# apt-get install -y kmscube

Run and test
# kmscube
......

=== With X ===

LIMA

2019-08-29T07:55:07Z

StefanM: /* FAQ */

= LIMA driver =

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build and install the sources
# ninja -C build
# ninja -C build install

== Usage ==
=== Without X ===

You can test the driver with kmscube
# apt-get install -y kmscube

Run and test
# kmscube
......

=== With X ===

LIMA

2019-08-29T07:47:22Z

StefanM: /* LIMA driver */

= LIMA driver =

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build and install the sources
# ninja -C build
# ninja -C build install

== Usage ==
=== Without X ===

You can test the driver with kmscube
# apt-get install -y kmscube

Run and test
# kmscube
......

=== With X ===

== FAQ ==
=== Compilation fail with ===

# update-alternatives --config gcc

LIMA

2019-08-29T06:18:28Z

StefanM: /* Usage */

= LIMA driver =

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build and install the sources
# ninja -C build
# ninja -C build install

== Usage ==
=== Without X ===

You can test the driver with kmscube
# apt-get install -y kmscube

Run and test
# kmscube
......

=== With X ===

LIMA

2019-08-29T06:16:25Z

StefanM: /* Building */

= LIMA driver =

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build and install the sources
# ninja -C build
# ninja -C build install

== Usage ==
adasd

LIMA

2019-08-29T06:15:45Z

StefanM: /* LIMA driver */

LIMA

2019-08-29T06:15:26Z

StefanM: /* LIMA driver = */

= LIMA driver =
== Description ==
== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build the sources
# ninja -C build

== Usage ==
adasd

LIMA

2019-08-29T06:15:14Z

StefanM:

= LIMA driver ==
== Description ==
== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build the sources
# ninja -C build

== Usage ==
adasd

LIMA

2019-08-29T06:14:32Z

StefanM:

== Description ==
== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Clone the sources
# git clone --depth=1 --branch 19.1 https://gitlab.freedesktop.org/mesa/mesa

* Configure meson
# cd mesa
# meson build -Dvulkan-drivers=[] -Dplatforms=drm,x11 -Ddri-drivers=[] -Dgallium-drivers=lima,kmsro

* Build the sources
# ninja -C build

== Usage ==
adasd

LIMA

2019-08-29T06:12:15Z

StefanM: Created page with " == Building == * Install requirements # apt-get update # apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-de..."

== Building ==
* Install requirements
# apt-get update
# apt-get install -y bison g++ gcc gettext flex libdrm-dev libexpat1-dev libx11-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxdamage-dev libxrandr-dev libxshmfence-dev libxext-dev libxxf86vm-dev meson pkg-config python3-mako python3-pip python3-setuptools python3-wheel zlib1g-dev

* Install

USB-gLINK

2019-07-16T13:22:47Z

StefanM: /* Software */

== Software ==
=== Connecting ===
Install packages:
sudo apt install libqmi-utils udhcpc

Create new file ''/etc/qmi-network.conf''.
sudo vi /etc/qmi-network.conf

Inside type your APN settings:
APN=internet.xxx.xxx
APN_USER=xxxxx APN_PASS=xxxxx

Start network and check status
sudo qmi-network /dev/cdc-wdm0 start
sudo qmi-network /dev/cdc-wdm0 status
......
Status: connected

Check interface name
dmesg | grep "wwan0"
....
qmi_wwan 3-1:1.4 wwp8s0u1i4: renamed from wwan0

Obtain ip address:
sudo udhcpc -q -f -n -i wwp8s0u1i4

Check interface
ifconfig wwp8s0u1i4
wwp8s0u1i4: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.167.84.92 netmask 255.255.255.248 destination 10.167.84.92
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 47 bytes 16255 (16.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 163 bytes 16212 (16.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

=== Enabling serial port ===
By default when you connect the USB-gLINK to PC, qmi_wwan module is used. This is because the VID/PIN is not listed in ''drivers/usb/serial/option.c''.

Login as root user
su -

Probe usbserial module
modprobe usbserial

Bind device VID/PID to usbserial
echo 2c7c 0125 > /sys/bus/usb-serial/drivers/generic/new_id

Check result
dmesg
.....
usb 3-1: new high-speed USB device number 36 using xhci_hcd
usb 3-1: New USB device found, idVendor=2c7c, idProduct=0125
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: EG25-G
usb 3-1: Manufacturer: Quectel
usbserial_generic 3-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.0: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.0: generic converter detected
usb 3-1: generic converter now attached to ttyUSB0
usbserial_generic 3-1:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.1: generic converter detected
usb 3-1: generic converter now attached to ttyUSB1
usbserial_generic 3-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.2: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.2: generic converter detected
usb 3-1: generic converter now attached to ttyUSB2
usbserial_generic 3-1:1.3: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.3: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.3: generic converter detected
usb 3-1: generic converter now attached to ttyUSB3

== Hardware ==

USB-gLINK

2019-07-16T13:22:21Z

StefanM: /* Software support */

USB-gLINK

2019-07-16T13:20:25Z

StefanM: /* Connecting */

= Software support =
== Connecting ==
Install packages:
sudo apt install libqmi-utils udhcpc

Create new file ''/etc/qmi-network.conf''.
sudo vi /etc/qmi-network.conf

Inside type your APN settings:
APN=internet.xxx.xxx
APN_USER=xxxxx APN_PASS=xxxxx

Start network and check status
sudo qmi-network /dev/cdc-wdm0 start
sudo qmi-network /dev/cdc-wdm0 status
......
Status: connected

Check interface name
dmesg | grep "wwan0"
....
qmi_wwan 3-1:1.4 wwp8s0u1i4: renamed from wwan0

Obtain ip address:
sudo udhcpc -q -f -n -i wwp8s0u1i4

Check interface
ifconfig wwp8s0u1i4
wwp8s0u1i4: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.167.84.92 netmask 255.255.255.248 destination 10.167.84.92
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 47 bytes 16255 (16.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 163 bytes 16212 (16.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

== Enabling serial port ==
By default when you connect the USB-gLINK to PC, qmi_wwan module is used. This is because the VID/PIN is not listed in ''drivers/usb/serial/option.c''.

Login as root user
su -

Probe usbserial module
modprobe usbserial

Bind device VID/PID to usbserial
echo 2c7c 0125 > /sys/bus/usb-serial/drivers/generic/new_id

Check result
dmesg
.....
usb 3-1: new high-speed USB device number 36 using xhci_hcd
usb 3-1: New USB device found, idVendor=2c7c, idProduct=0125
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: EG25-G
usb 3-1: Manufacturer: Quectel
usbserial_generic 3-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.0: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.0: generic converter detected
usb 3-1: generic converter now attached to ttyUSB0
usbserial_generic 3-1:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.1: generic converter detected
usb 3-1: generic converter now attached to ttyUSB1
usbserial_generic 3-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.2: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.2: generic converter detected
usb 3-1: generic converter now attached to ttyUSB2
usbserial_generic 3-1:1.3: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.3: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.3: generic converter detected
usb 3-1: generic converter now attached to ttyUSB3

USB-gLINK

2019-07-16T13:19:22Z

StefanM: Created page with "== Connecting == Install packages: sudo apt install libqmi-utils udhcpc Create new file ''/etc/qmi-network.conf''. sudo vi /etc/qmi-network.conf Inside type your APN set..."

== Connecting ==
Install packages:
sudo apt install libqmi-utils udhcpc

Create new file ''/etc/qmi-network.conf''.
sudo vi /etc/qmi-network.conf

Inside type your APN settings:
APN=internet.xxx.xxx
APN_USER=xxxxx APN_PASS=xxxxx

Start network and check status
sudo qmi-network /dev/cdc-wdm0 start
sudo qmi-network /dev/cdc-wdm0 status
......
Status: connected

Check interface name
dmesg | grep "wwan0"
....
qmi_wwan 3-1:1.4 wwp8s0u1i4: renamed from wwan0

Obtain ip address:
sudo udhcpc -q -f -n -i wwp8s0u1i4

Check interface
ifconfig wwp8s0u1i4
wwp8s0u1i4: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.167.84.92 netmask 255.255.255.248 destination 10.167.84.92
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 47 bytes 16255 (16.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 163 bytes 16212 (16.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

== Enabling serial port ==
By default when you connect the USB-gLINK to PC, qmi_wwan module is used. This is because the VID/PIN is not listed in ''drivers/usb/serial/option.c''.

Login as root user
su -

Probe usbserial module
modprobe usbserial

Bind device VID/PID to usbserial
echo 2c7c 0125 > /sys/bus/usb-serial/drivers/generic/new_id

Check result
dmesg
.....
usb 3-1: new high-speed USB device number 36 using xhci_hcd
usb 3-1: New USB device found, idVendor=2c7c, idProduct=0125
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: EG25-G
usb 3-1: Manufacturer: Quectel
usbserial_generic 3-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.0: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.0: generic converter detected
usb 3-1: generic converter now attached to ttyUSB0
usbserial_generic 3-1:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.1: generic converter detected
usb 3-1: generic converter now attached to ttyUSB1
usbserial_generic 3-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.2: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.2: generic converter detected
usb 3-1: generic converter now attached to ttyUSB2
usbserial_generic 3-1:1.3: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 3-1:1.3: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 3-1:1.3: generic converter detected
usb 3-1: generic converter now attached to ttyUSB3

RK3328-SOM204

2019-06-17T06:25:43Z

StefanM: /* Flash image */

== Software ==
=== Armbian ===
== FAQ ==
=== Use alarm clock ===

You can schedule power-on event using alarm clock.

Set the alarm 1 minute in the future
echo $(date '+%s' -d '+ 1 minutes') > /sys/class/rtc/rtc0/wakealarm

Now power-off the board and wait for the wake-up alarm:
poweroff

=== Flash image to eMMC via USB ===

==== Prepare rkdeveloptool ====

Get sources:
git clone https://github.com/rockchip-linux/rkdeveloptool

Install requirements:
sudo apt-get install libudev-dev libusb-1.0-0-dev dh-autoreconf

Build rkdeveloptool
cd rkdeveloptool
autoreconf -i
./configure
make

==== Prepare loader ====

Get rkbin:
git clone https://github.com/rockchip-linux/rkbin

Edit configuration:
cd rkbin
cat > RKBOOT/RK3328MINIALL.ini << __EOF__
[CHIP_NAME]
NAME=RK322H
[VERSION]
MAJOR=2
MINOR=49
[CODE471_OPTION]
NUM=1
Path1=bin/rk33/rk3328_ddr_333MHz_v1.14.bin
Sleep=1
[CODE472_OPTION]
NUM=1
Path1=bin/rk33/rk322xh_usbplug_v2.49.bin
[LOADER_OPTION]
NUM=2
LOADER1=FlashData
LOADER2=FlashBoot
FlashData=bin/rk33/rk3328_ddr_333MHz_v1.14.bin
FlashBoot=bin/rk33/rk322xh_miniloader_v2.49.bin
[OUTPUT]
PATH=rk3328_loader_v1.14.249.bin
__EOF__

Generate loader image:
./tools/boot_merger RKBOOT/RK3328MINIALL.ini

==== Flash image ====
Put device into loader mode. Plug USB-mini cable, hold '''recovery''' button and
press '''reset'''. Check the with:
lsusb

You should see:
Bus 002 Device 035: ID 2207:330a

Go to rkdevelop folder:
cd /path/to/rkdeveloptool

Check devices:
sudo rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330a,LocationID=208 Maskrom

Upload loader:
sudo rkdeveloptool db /path/to/rk3328_loader_v1.14.249.bin

In the terminal you should see (baudrate is '''1500000'''):
DDR version 1.14 20190328
ID:0x805 N
In
LPDDR3
333MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB
ddrconfig:6
OUT
Boot1 Release Time: Sep 7 2018 15:48:25, version: 2.49
SdmmcInit=0 NOT PRESENT
mmc Ext_csd, ret=0 ,
Ext[226]=20, bootSize=2000,
Ext[215]=1, Ext[214]=d1, Ext[213]=f0, Ext[212]=0,cap=1d1f000 REL=1f
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=14910MB
FwPartOffset=2000 , 2000
UsbHook 736999
powerOn 737075

Erase the flash:
sudo rkdeveloptool ef

Flash a new image:
sudo rkdeveloptool wl 0 /path/to/some/image.img

RK3328-SOM204

2019-06-17T06:22:48Z

StefanM: /* Flash image */

RK3328-SOM204

2019-06-17T06:20:25Z

StefanM: /* Flash image */

== Software ==
=== Armbian ===
== FAQ ==
=== Use alarm clock ===

You can schedule power-on event using alarm clock.

Set the alarm 1 minute in the future
echo $(date '+%s' -d '+ 1 minutes') > /sys/class/rtc/rtc0/wakealarm

Now power-off the board and wait for the wake-up alarm:
poweroff

=== Flash image to eMMC via USB ===

==== Prepare rkdeveloptool ====

Get sources:
git clone https://github.com/rockchip-linux/rkdeveloptool

Install requirements:
sudo apt-get install libudev-dev libusb-1.0-0-dev dh-autoreconf

Build rkdeveloptool
cd rkdeveloptool
autoreconf -i
./configure
make

==== Prepare loader ====

Get rkbin:
git clone https://github.com/rockchip-linux/rkbin

Edit configuration:
cd rkbin
cat > RKBOOT/RK3328MINIALL.ini << __EOF__
[CHIP_NAME]
NAME=RK322H
[VERSION]
MAJOR=2
MINOR=49
[CODE471_OPTION]
NUM=1
Path1=bin/rk33/rk3328_ddr_333MHz_v1.14.bin
Sleep=1
[CODE472_OPTION]
NUM=1
Path1=bin/rk33/rk322xh_usbplug_v2.49.bin
[LOADER_OPTION]
NUM=2
LOADER1=FlashData
LOADER2=FlashBoot
FlashData=bin/rk33/rk3328_ddr_333MHz_v1.14.bin
FlashBoot=bin/rk33/rk322xh_miniloader_v2.49.bin
[OUTPUT]
PATH=rk3328_loader_v1.14.249.bin
__EOF__

Generate loader image:
./tools/boot_merger RKBOOT/RK3328MINIALL.ini

==== Flash image ====
Put device into loader mode. Plug USB-mini cable, hold '''recovery''' button and
press '''reset'''. Check the with:
lsusb

You should see:
Bus 002 Device 035: ID 2207:330a

Go to rkdevelop folder:
cd /path/to/rkdeveloptool

Check devices:
sudo rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330a,LocationID=208 Maskrom

Upload loader:
sudo rkdeveloptool db ../rkbin/rk3328_loader_v1.14.249.bin
DDR version 1.14 20190328
ID:0x805 N
In
LPDDR3
333MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB
ddrconfig:6
OUT
Boot1 Release Time: Sep 7 2018 15:48:25, version: 2.49
SdmmcInit=0 NOT PRESENT
mmc Ext_csd, ret=0 ,
Ext[226]=20, bootSize=2000,
Ext[215]=1, Ext[214]=d1, Ext[213]=f0, Ext[212]=0,cap =1d1f000 REL=1f
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=14910MB
FwPartOffset=2000 , 2000
UsbHook 736999
powerOn 737075

RK3328-SOM204

2019-06-13T09:53:45Z

StefanM: /* Flash image */

RK3328-SOM204

2019-06-13T07:42:51Z

StefanM: /* Flash image to eMMC via USB */

RK3328-SOM204

2019-06-13T06:43:59Z

StefanM: /* FAQ */

RK3328-SOM204

2019-06-04T08:18:25Z

StefanM: /* Flash image to eMMC via USB */

== Software ==
=== Armbian ===
== FAQ ==
=== Flash image to eMMC via USB ===

Get sources:
git clone https://github.com/rockchip-linux/rkdeveloptool

Install requirements:
sudo apt-get install libudev-dev libusb-1.0-0-dev dh-autoreconf

Build rkdeveloptool
cd rkdeveloptool
autoreconf -i
./configure
make

Put device into loader mode. Plug USB-mini cable, hold '''recovery''' button and
press '''reset'''. Check the with:
lsusb

You should see:
Bus 002 Device 035: ID 2207:330a

RK3328-SOM204

2019-06-04T08:12:31Z

StefanM: /* FAQ */

RK3328-SOM204

2019-06-04T05:09:56Z

StefanM: Created page with "== Software == === Armbian === == FAQ =="

== Software ==
=== Armbian ===
== FAQ ==

RT5350F-OLinuXino

2019-04-05T06:27:01Z

StefanM: /* OpenWRT 18.06 */

=RT5350F-OLinuXino official images build instructions=

==Overview==

==Quick-start==

1. Connect USB<->serial cable between the UART0 pins of the board and your personal computer.

2. Open your favourite serial terminal software on the COM port, created by your USB<->serial cable.

3. Set the baud rate for the connection to 57600.

4. Power on RT5350F-OLinuXino-EVB.

==Prebuilt files and system restore==

RT5350F-OLinuXino comes with an image loaded into the SPI flash memory. If something goes wrong you can restore the original image.

Two of the prebuilt files (bootloader.img and openwrt.bin) can be uploaded to the board via the built-in uboot. If your uboot is damaged beyond repair you might need a programmer to recover the software of the board. The other two files (that contain uboot) require a programming tool (uboot+factory.bin and uboot+factory+openwrt.bin). The board comes programmed with the image called uboot+factory+openwrt.bin. See [[#Upload prebuilt images using uboot]] or [[#Upload prebuilt images using programmer tool]].

'''All prebuilt binary files are available for download at our GitHub page. Direct link to the location: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images]'''

The four prebuilt files available are:
* bootloader.img - this is only the bootloader
* openwrt.bin - this is only prebuilt openwrt
The above two can be uploaded using uboot.

* uboot+factory.bin - this is the uboot + factory wifi settings
* uboot+factory+openwrt.bin - this is the uboot + factory wifi settings + openwrt
These two binaries can be uploaded '''only''' via programmer tool (with flashrom).

===Upload prebuilt images using uboot===
Reboot the board and you'll see:
U-Boot 1.1.3 (Apr 20 2015 - 13:25:55)

Board: RT5350F-OLinuXino DRAM: 32 MB
relocate_code Pointer at: 81fb4000
spi_wait_nsec: 42
spi device id: 1c 30 17 1c 30 (30171c30)
find flash: EN25Q64
raspi_read: from:30000 len:1000
.*** Warning - bad CRC, using default environment

=============================================================
RT5350F-OLinuXino UBoot Version: 4.0.0.0
--------------------------------------------------------------
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_TYPE: SDRAM
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
DRAM_TOTAL_WIDTH: 16 bits
TOTAL_MEMORY_SIZE: 32 MBytes
Flash component: SPI Flash
Date:Apr 20 2015 Time:13:25:55
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

##### The CPU freq = 360 MHZ ####
estimate memory size =32 Mbytes

Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.

===Upload prebuilt OpenWRT using uboot===

Press 2, then y and enter some values for ip, server ip and filename:

You choosed 2
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (10.10.10.123) ==:10.10.10.123
Input server IP (10.10.10.3) ==:10.10.10.3
Input Linux Kernel filename () ==:file.bin

Then your new system will boot.

===Upload prebuilt uboot===

Press 9, then again enter ip address, server ip and filename to upload:

You choosed 9

0
raspi_read: from:40028 len:6
.

9: System Load Boot Loader then write to Flash via TFTP.
Warning!! Erase Boot Loader in Flash then burn new one. Are you sure?(Y/N)

Press '''Y''' and continue:

Input device IP (10.10.10.123) ==:10.10.10.123
Enter some static address for the device, for example ''192.168.0.201''.

Next enter server address, for example ''192.168.0.15'':

Input server IP (10.10.10.3) ==:192.168.0.15

Finally enter filename:

Input Uboot filename () ==:bootloader.img

'''Don't forget to plug LAN cable.''' You should see something like that:

Got it
#####################
done
Bytes transferred = 106976 (1a1e0 hex)
NetBootFileXferSize= 0001a1e0
raspi_erase_write: offs:0, count:1a1e0
raspi_erase: offs:0 len:10000
.
raspi_write: to:0 len:10000
.
raspi_read: from:0 len:10000
.raspi_read: from:10000 len:10000
.raspi_erase: offs:10000 len:10000
.
raspi_write: to:10000 len:10000
.
raspi_read: from:10000 len:10000
.Done!

===Upload prebuilt images using programmer tool===

We will use [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD/ ARM-USB-OCD]. It has FT2232 chip which can be used to in SPI master mode. You can also use ARM-USB-TINY; ARM-USB-TINY-H; ARM-USB-OCD-H or any FT2232-based debugger.

Connect ARM-USB-OCD with RT5350F-OLinuXino-EVB according the schematic below (for the blue wire GND you can also use other GND pins available at the board; the GND is common):

[[File:Arm-usb-ocd.png|480px]]

'''RST_RT''' jumper MUST be closed. Then power the board to become ready writing.

Download flashrom software and build it using instructions on the site.

To program the SPI flash run:
flashrom -p ft2232_spi:type=arm-usb-ocd -w file.bin

Then wait some minutes for process to complete.

==Building uboot==

Get the sources from:
git clone https://github.com/OLIMEX/u-boot_RT5350F-OLinuXino
cd u-boot_RT5350F-OLinuXino

Target must be build with gcc3.4! This is very important because with another versions of GCC the build process will fail. You can find that version from '''Ralink SDK'''. Use Google to find it.

Run
make menuconfig

You'll see that the default location is /opt/buildroot-gcc342/bin. Change that with your path.

To actually build u-boot run:
make

At the end of the process you'll see something like this

===============<<IMPORTANT>>==================
Notes:Uboot firmware in flash is uboot.img NOT uboot.bin
================================================

./tools/mkimage -A mips -T standalone -C none \
-a 0x80200000 -e 0x80200000 \
-n "SPI Flash Image" \
-r SDR -s 16 -t 32 -u 16 \
-y 0x0 -z 0x0 -w 0xFF -d uboot.bin uboot.img
Image Name: SPI Flash Image
Created: Thu May 14 08:23:19 2015
Image Type: MIPS Linux Standalone Program (uncompressed)
Data Size: 106912 Bytes = 104.41 kB = 0.10 MB
Load Address: 0x80200000
Entry Point: 0x80200000
DRAM Parameter: 6 (Parm0=0 Parm1=0)

The image '''uboot.img''' can be uploaded via tftp.

==Building OpenWRT==

=== OpenWRT 18.06 ===

Download sources:
git clone https://github.com/OLIMEX/openwrt -b evb+/18.06

Go into openwrt directory:
cd openwrt

Update and install feeds:
./scripts/feeds update -a
./scripts/feeds install -a

Apply config:
cat > .config << __EOF__
CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_rt305x=y
CONFIG_TARGET_MULTI_PROFILE=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb-plus=y
# CONFIG_FEED_luci is not set
# CONFIG_FEED_packages is not set
# CONFIG_FEED_routing is not set
# CONFIG_FEED_telephony is not set
CONFIG_PACKAGE_block-mount=y
CONFIG_PACKAGE_i2c-tools=y
CONFIG_PACKAGE_kmod-crypto-crc32c=y
CONFIG_PACKAGE_kmod-crypto-hash=y
CONFIG_PACKAGE_kmod-fs-ext4=y
CONFIG_PACKAGE_kmod-fs-ntfs=y
CONFIG_PACKAGE_kmod-fs-vfat=y
CONFIG_PACKAGE_kmod-lib-crc16=y
CONFIG_PACKAGE_kmod-nls-cp437=y
CONFIG_PACKAGE_kmod-nls-iso8859-1=y
CONFIG_PACKAGE_kmod-nls-utf8=y
CONFIG_PACKAGE_kmod-scsi-core=y
CONFIG_PACKAGE_kmod-usb-storage=y
CONFIG_PACKAGE_libiwinfo-lua=y
CONFIG_PACKAGE_liblua=y
CONFIG_PACKAGE_liblucihttp=y
CONFIG_PACKAGE_liblucihttp-lua=y
CONFIG_PACKAGE_libubus-lua=y
CONFIG_PACKAGE_lua=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-app-firewall=y
CONFIG_PACKAGE_luci-base=y
CONFIG_PACKAGE_luci-lib-ip=y
CONFIG_PACKAGE_luci-lib-jsonc=y
CONFIG_PACKAGE_luci-lib-nixio=y
CONFIG_PACKAGE_luci-mod-admin-full=y
CONFIG_PACKAGE_luci-proto-ipv6=y
CONFIG_PACKAGE_luci-proto-ppp=y
CONFIG_PACKAGE_luci-theme-bootstrap=y
CONFIG_PACKAGE_rpcd=y
CONFIG_PACKAGE_rpcd-mod-rrdns=y
CONFIG_PACKAGE_uhttpd=y
__EOF__

Expand to full config:
make defconfig

Make some modifications with:
make menuconfig

Build the images:
make

Target images can be found in '''bin/targets/ramips/rt305x/''':
tree bin/targets/ramips/rt305x/
bin/targets/ramips/rt305x/
|-- config.seed
|-- openwrt-ramips-rt305x-device-rt5350f-olinuxino-evb-plus.manifest
|-- openwrt-ramips-rt305x.manifest
|-- openwrt-ramips-rt305x-root.squashfs
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-uImage.bin
|-- openwrt-ramips-rt305x-uImage-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux.bin
|-- openwrt-ramips-rt305x-vmlinux.elf
|-- openwrt-ramips-rt305x-vmlinux-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux-initramfs.elf

=== OpenWRT ===
Make a directory:
# mkdir some_dir
# cd some_dir

Download sources:
# git clone https://github.com/OLIMEX/openwrt -b rt5350f

Go into openwrt directory:
# cd openwrt

You can use our config:
# make

or if you want to change something:
# make menuconfig
# make

After some time build will finish. The image is found under:
'''build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_rt305x/\'''
'''openwrt-ramips-rt305x-olinuxino-rt5350f-squashfs-sysupgrade.bin'''

Place that file on some tftp server and then upload it to the board.

=Demo projects=

*First steps video with RT5350F-OLinuXino-EVB by Leon Anavi: [https://www.youtube.com/watch?v=-MsywWtN79c https://www.youtube.com/watch?v=-MsywWtN79c]

= Images changelog =

== Release-3 (03 APR 2019) ==
* Upgrade OpenWRT to 18.06
* Added support for RT5350-OLinuXino-EVB+

== Release-2 (06 JUL 2015) ==
* Upgraded kernel version to 3.18.17
* Inverted wlan led polarity - this way it blink when WiFi is on
* Fixed firmware partition size - https://github.com/OLIMEX/openwrt/issues/1

RT5350F-OLinuXino

2019-04-03T13:27:01Z

StefanM: /* Release-2 (06 JUL 2015) */

=RT5350F-OLinuXino official images build instructions=

==Overview==

==Quick-start==

1. Connect USB<->serial cable between the UART0 pins of the board and your personal computer.

2. Open your favourite serial terminal software on the COM port, created by your USB<->serial cable.

3. Set the baud rate for the connection to 57600.

4. Power on RT5350F-OLinuXino-EVB.

==Prebuilt files and system restore==

RT5350F-OLinuXino comes with an image loaded into the SPI flash memory. If something goes wrong you can restore the original image.

Two of the prebuilt files (bootloader.img and openwrt.bin) can be uploaded to the board via the built-in uboot. If your uboot is damaged beyond repair you might need a programmer to recover the software of the board. The other two files (that contain uboot) require a programming tool (uboot+factory.bin and uboot+factory+openwrt.bin). The board comes programmed with the image called uboot+factory+openwrt.bin. See [[#Upload prebuilt images using uboot]] or [[#Upload prebuilt images using programmer tool]].

'''All prebuilt binary files are available for download at our GitHub page. Direct link to the location: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images]'''

The four prebuilt files available are:
* bootloader.img - this is only the bootloader
* openwrt.bin - this is only prebuilt openwrt
The above two can be uploaded using uboot.

* uboot+factory.bin - this is the uboot + factory wifi settings
* uboot+factory+openwrt.bin - this is the uboot + factory wifi settings + openwrt
These two binaries can be uploaded '''only''' via programmer tool (with flashrom).

===Upload prebuilt images using uboot===
Reboot the board and you'll see:
U-Boot 1.1.3 (Apr 20 2015 - 13:25:55)

Board: RT5350F-OLinuXino DRAM: 32 MB
relocate_code Pointer at: 81fb4000
spi_wait_nsec: 42
spi device id: 1c 30 17 1c 30 (30171c30)
find flash: EN25Q64
raspi_read: from:30000 len:1000
.*** Warning - bad CRC, using default environment

=============================================================
RT5350F-OLinuXino UBoot Version: 4.0.0.0
--------------------------------------------------------------
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_TYPE: SDRAM
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
DRAM_TOTAL_WIDTH: 16 bits
TOTAL_MEMORY_SIZE: 32 MBytes
Flash component: SPI Flash
Date:Apr 20 2015 Time:13:25:55
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

##### The CPU freq = 360 MHZ ####
estimate memory size =32 Mbytes

Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.

===Upload prebuilt OpenWRT using uboot===

Press 2, then y and enter some values for ip, server ip and filename:

You choosed 2
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (10.10.10.123) ==:10.10.10.123
Input server IP (10.10.10.3) ==:10.10.10.3
Input Linux Kernel filename () ==:file.bin

Then your new system will boot.

===Upload prebuilt uboot===

Press 9, then again enter ip address, server ip and filename to upload:

You choosed 9

0
raspi_read: from:40028 len:6
.

9: System Load Boot Loader then write to Flash via TFTP.
Warning!! Erase Boot Loader in Flash then burn new one. Are you sure?(Y/N)

Press '''Y''' and continue:

Input device IP (10.10.10.123) ==:10.10.10.123
Enter some static address for the device, for example ''192.168.0.201''.

Next enter server address, for example ''192.168.0.15'':

Input server IP (10.10.10.3) ==:192.168.0.15

Finally enter filename:

Input Uboot filename () ==:bootloader.img

'''Don't forget to plug LAN cable.''' You should see something like that:

Got it
#####################
done
Bytes transferred = 106976 (1a1e0 hex)
NetBootFileXferSize= 0001a1e0
raspi_erase_write: offs:0, count:1a1e0
raspi_erase: offs:0 len:10000
.
raspi_write: to:0 len:10000
.
raspi_read: from:0 len:10000
.raspi_read: from:10000 len:10000
.raspi_erase: offs:10000 len:10000
.
raspi_write: to:10000 len:10000
.
raspi_read: from:10000 len:10000
.Done!

===Upload prebuilt images using programmer tool===

We will use [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD/ ARM-USB-OCD]. It has FT2232 chip which can be used to in SPI master mode. You can also use ARM-USB-TINY; ARM-USB-TINY-H; ARM-USB-OCD-H or any FT2232-based debugger.

Connect ARM-USB-OCD with RT5350F-OLinuXino-EVB according the schematic below (for the blue wire GND you can also use other GND pins available at the board; the GND is common):

[[File:Arm-usb-ocd.png|480px]]

'''RST_RT''' jumper MUST be closed. Then power the board to become ready writing.

Download flashrom software and build it using instructions on the site.

To program the SPI flash run:
flashrom -p ft2232_spi:type=arm-usb-ocd -w file.bin

Then wait some minutes for process to complete.

==Building uboot==

Get the sources from:
git clone https://github.com/OLIMEX/u-boot_RT5350F-OLinuXino
cd u-boot_RT5350F-OLinuXino

Target must be build with gcc3.4! This is very important because with another versions of GCC the build process will fail. You can find that version from '''Ralink SDK'''. Use Google to find it.

Run
make menuconfig

You'll see that the default location is /opt/buildroot-gcc342/bin. Change that with your path.

To actually build u-boot run:
make

At the end of the process you'll see something like this

===============<<IMPORTANT>>==================
Notes:Uboot firmware in flash is uboot.img NOT uboot.bin
================================================

./tools/mkimage -A mips -T standalone -C none \
-a 0x80200000 -e 0x80200000 \
-n "SPI Flash Image" \
-r SDR -s 16 -t 32 -u 16 \
-y 0x0 -z 0x0 -w 0xFF -d uboot.bin uboot.img
Image Name: SPI Flash Image
Created: Thu May 14 08:23:19 2015
Image Type: MIPS Linux Standalone Program (uncompressed)
Data Size: 106912 Bytes = 104.41 kB = 0.10 MB
Load Address: 0x80200000
Entry Point: 0x80200000
DRAM Parameter: 6 (Parm0=0 Parm1=0)

The image '''uboot.img''' can be uploaded via tftp.

==Building OpenWRT==

=== OpenWRT 18.06 ===

Download sources:
git clone https://github.com/OLIMEX/openwrt -b evb+/18.06

Go into openwrt directory:
cd openwrt

Apply config:
cat > .config << __EOF__
CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_rt305x=y
CONFIG_TARGET_MULTI_PROFILE=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb-plus=y
# CONFIG_FEED_luci is not set
# CONFIG_FEED_packages is not set
# CONFIG_FEED_routing is not set
# CONFIG_FEED_telephony is not set
CONFIG_PACKAGE_block-mount=y
CONFIG_PACKAGE_i2c-tools=y
CONFIG_PACKAGE_kmod-crypto-crc32c=y
CONFIG_PACKAGE_kmod-crypto-hash=y
CONFIG_PACKAGE_kmod-fs-ext4=y
CONFIG_PACKAGE_kmod-fs-ntfs=y
CONFIG_PACKAGE_kmod-fs-vfat=y
CONFIG_PACKAGE_kmod-lib-crc16=y
CONFIG_PACKAGE_kmod-nls-cp437=y
CONFIG_PACKAGE_kmod-nls-iso8859-1=y
CONFIG_PACKAGE_kmod-nls-utf8=y
CONFIG_PACKAGE_kmod-scsi-core=y
CONFIG_PACKAGE_kmod-usb-storage=y
CONFIG_PACKAGE_libiwinfo-lua=y
CONFIG_PACKAGE_liblua=y
CONFIG_PACKAGE_liblucihttp=y
CONFIG_PACKAGE_liblucihttp-lua=y
CONFIG_PACKAGE_libubus-lua=y
CONFIG_PACKAGE_lua=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-app-firewall=y
CONFIG_PACKAGE_luci-base=y
CONFIG_PACKAGE_luci-lib-ip=y
CONFIG_PACKAGE_luci-lib-jsonc=y
CONFIG_PACKAGE_luci-lib-nixio=y
CONFIG_PACKAGE_luci-mod-admin-full=y
CONFIG_PACKAGE_luci-proto-ipv6=y
CONFIG_PACKAGE_luci-proto-ppp=y
CONFIG_PACKAGE_luci-theme-bootstrap=y
CONFIG_PACKAGE_rpcd=y
CONFIG_PACKAGE_rpcd-mod-rrdns=y
CONFIG_PACKAGE_uhttpd=y
__EOF__

Expand to full config:
make defconfig

Make some modifications with:
make menuconfig

Build the images:
make

Target images can be found in '''bin/targets/ramips/rt305x/''':
tree bin/targets/ramips/rt305x/
bin/targets/ramips/rt305x/
|-- config.seed
|-- openwrt-ramips-rt305x-device-rt5350f-olinuxino-evb-plus.manifest
|-- openwrt-ramips-rt305x.manifest
|-- openwrt-ramips-rt305x-root.squashfs
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-uImage.bin
|-- openwrt-ramips-rt305x-uImage-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux.bin
|-- openwrt-ramips-rt305x-vmlinux.elf
|-- openwrt-ramips-rt305x-vmlinux-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux-initramfs.elf

=== OpenWRT ===
Make a directory:
# mkdir some_dir
# cd some_dir

Download sources:
# git clone https://github.com/OLIMEX/openwrt -b rt5350f

Go into openwrt directory:
# cd openwrt

You can use our config:
# make

or if you want to change something:
# make menuconfig
# make

After some time build will finish. The image is found under:
'''build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_rt305x/\'''
'''openwrt-ramips-rt305x-olinuxino-rt5350f-squashfs-sysupgrade.bin'''

Place that file on some tftp server and then upload it to the board.

=Demo projects=

*First steps video with RT5350F-OLinuXino-EVB by Leon Anavi: [https://www.youtube.com/watch?v=-MsywWtN79c https://www.youtube.com/watch?v=-MsywWtN79c]

= Images changelog =

== Release-3 (03 APR 2019) ==
* Upgrade OpenWRT to 18.06
* Added support for RT5350-OLinuXino-EVB+

== Release-2 (06 JUL 2015) ==
* Upgraded kernel version to 3.18.17
* Inverted wlan led polarity - this way it blink when WiFi is on
* Fixed firmware partition size - https://github.com/OLIMEX/openwrt/issues/1

RT5350F-OLinuXino

2019-04-03T13:24:20Z

StefanM: /* Building OpenWRT */

=RT5350F-OLinuXino official images build instructions=

==Overview==

==Quick-start==

1. Connect USB<->serial cable between the UART0 pins of the board and your personal computer.

2. Open your favourite serial terminal software on the COM port, created by your USB<->serial cable.

3. Set the baud rate for the connection to 57600.

4. Power on RT5350F-OLinuXino-EVB.

==Prebuilt files and system restore==

RT5350F-OLinuXino comes with an image loaded into the SPI flash memory. If something goes wrong you can restore the original image.

Two of the prebuilt files (bootloader.img and openwrt.bin) can be uploaded to the board via the built-in uboot. If your uboot is damaged beyond repair you might need a programmer to recover the software of the board. The other two files (that contain uboot) require a programming tool (uboot+factory.bin and uboot+factory+openwrt.bin). The board comes programmed with the image called uboot+factory+openwrt.bin. See [[#Upload prebuilt images using uboot]] or [[#Upload prebuilt images using programmer tool]].

'''All prebuilt binary files are available for download at our GitHub page. Direct link to the location: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images]'''

The four prebuilt files available are:
* bootloader.img - this is only the bootloader
* openwrt.bin - this is only prebuilt openwrt
The above two can be uploaded using uboot.

* uboot+factory.bin - this is the uboot + factory wifi settings
* uboot+factory+openwrt.bin - this is the uboot + factory wifi settings + openwrt
These two binaries can be uploaded '''only''' via programmer tool (with flashrom).

===Upload prebuilt images using uboot===
Reboot the board and you'll see:
U-Boot 1.1.3 (Apr 20 2015 - 13:25:55)

Board: RT5350F-OLinuXino DRAM: 32 MB
relocate_code Pointer at: 81fb4000
spi_wait_nsec: 42
spi device id: 1c 30 17 1c 30 (30171c30)
find flash: EN25Q64
raspi_read: from:30000 len:1000
.*** Warning - bad CRC, using default environment

=============================================================
RT5350F-OLinuXino UBoot Version: 4.0.0.0
--------------------------------------------------------------
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_TYPE: SDRAM
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
DRAM_TOTAL_WIDTH: 16 bits
TOTAL_MEMORY_SIZE: 32 MBytes
Flash component: SPI Flash
Date:Apr 20 2015 Time:13:25:55
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

##### The CPU freq = 360 MHZ ####
estimate memory size =32 Mbytes

Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.

===Upload prebuilt OpenWRT using uboot===

Press 2, then y and enter some values for ip, server ip and filename:

You choosed 2
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (10.10.10.123) ==:10.10.10.123
Input server IP (10.10.10.3) ==:10.10.10.3
Input Linux Kernel filename () ==:file.bin

Then your new system will boot.

===Upload prebuilt uboot===

Press 9, then again enter ip address, server ip and filename to upload:

You choosed 9

0
raspi_read: from:40028 len:6
.

9: System Load Boot Loader then write to Flash via TFTP.
Warning!! Erase Boot Loader in Flash then burn new one. Are you sure?(Y/N)

Press '''Y''' and continue:

Input device IP (10.10.10.123) ==:10.10.10.123
Enter some static address for the device, for example ''192.168.0.201''.

Next enter server address, for example ''192.168.0.15'':

Input server IP (10.10.10.3) ==:192.168.0.15

Finally enter filename:

Input Uboot filename () ==:bootloader.img

'''Don't forget to plug LAN cable.''' You should see something like that:

Got it
#####################
done
Bytes transferred = 106976 (1a1e0 hex)
NetBootFileXferSize= 0001a1e0
raspi_erase_write: offs:0, count:1a1e0
raspi_erase: offs:0 len:10000
.
raspi_write: to:0 len:10000
.
raspi_read: from:0 len:10000
.raspi_read: from:10000 len:10000
.raspi_erase: offs:10000 len:10000
.
raspi_write: to:10000 len:10000
.
raspi_read: from:10000 len:10000
.Done!

===Upload prebuilt images using programmer tool===

We will use [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD/ ARM-USB-OCD]. It has FT2232 chip which can be used to in SPI master mode. You can also use ARM-USB-TINY; ARM-USB-TINY-H; ARM-USB-OCD-H or any FT2232-based debugger.

Connect ARM-USB-OCD with RT5350F-OLinuXino-EVB according the schematic below (for the blue wire GND you can also use other GND pins available at the board; the GND is common):

[[File:Arm-usb-ocd.png|480px]]

'''RST_RT''' jumper MUST be closed. Then power the board to become ready writing.

Download flashrom software and build it using instructions on the site.

To program the SPI flash run:
flashrom -p ft2232_spi:type=arm-usb-ocd -w file.bin

Then wait some minutes for process to complete.

==Building uboot==

Get the sources from:
git clone https://github.com/OLIMEX/u-boot_RT5350F-OLinuXino
cd u-boot_RT5350F-OLinuXino

Target must be build with gcc3.4! This is very important because with another versions of GCC the build process will fail. You can find that version from '''Ralink SDK'''. Use Google to find it.

Run
make menuconfig

You'll see that the default location is /opt/buildroot-gcc342/bin. Change that with your path.

To actually build u-boot run:
make

At the end of the process you'll see something like this

===============<<IMPORTANT>>==================
Notes:Uboot firmware in flash is uboot.img NOT uboot.bin
================================================

./tools/mkimage -A mips -T standalone -C none \
-a 0x80200000 -e 0x80200000 \
-n "SPI Flash Image" \
-r SDR -s 16 -t 32 -u 16 \
-y 0x0 -z 0x0 -w 0xFF -d uboot.bin uboot.img
Image Name: SPI Flash Image
Created: Thu May 14 08:23:19 2015
Image Type: MIPS Linux Standalone Program (uncompressed)
Data Size: 106912 Bytes = 104.41 kB = 0.10 MB
Load Address: 0x80200000
Entry Point: 0x80200000
DRAM Parameter: 6 (Parm0=0 Parm1=0)

The image '''uboot.img''' can be uploaded via tftp.

==Building OpenWRT==

=== OpenWRT 18.06 ===

Download sources:
git clone https://github.com/OLIMEX/openwrt -b evb+/18.06

Go into openwrt directory:
cd openwrt

Apply config:
cat > .config << __EOF__
CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_rt305x=y
CONFIG_TARGET_MULTI_PROFILE=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb-plus=y
# CONFIG_FEED_luci is not set
# CONFIG_FEED_packages is not set
# CONFIG_FEED_routing is not set
# CONFIG_FEED_telephony is not set
CONFIG_PACKAGE_block-mount=y
CONFIG_PACKAGE_i2c-tools=y
CONFIG_PACKAGE_kmod-crypto-crc32c=y
CONFIG_PACKAGE_kmod-crypto-hash=y
CONFIG_PACKAGE_kmod-fs-ext4=y
CONFIG_PACKAGE_kmod-fs-ntfs=y
CONFIG_PACKAGE_kmod-fs-vfat=y
CONFIG_PACKAGE_kmod-lib-crc16=y
CONFIG_PACKAGE_kmod-nls-cp437=y
CONFIG_PACKAGE_kmod-nls-iso8859-1=y
CONFIG_PACKAGE_kmod-nls-utf8=y
CONFIG_PACKAGE_kmod-scsi-core=y
CONFIG_PACKAGE_kmod-usb-storage=y
CONFIG_PACKAGE_libiwinfo-lua=y
CONFIG_PACKAGE_liblua=y
CONFIG_PACKAGE_liblucihttp=y
CONFIG_PACKAGE_liblucihttp-lua=y
CONFIG_PACKAGE_libubus-lua=y
CONFIG_PACKAGE_lua=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-app-firewall=y
CONFIG_PACKAGE_luci-base=y
CONFIG_PACKAGE_luci-lib-ip=y
CONFIG_PACKAGE_luci-lib-jsonc=y
CONFIG_PACKAGE_luci-lib-nixio=y
CONFIG_PACKAGE_luci-mod-admin-full=y
CONFIG_PACKAGE_luci-proto-ipv6=y
CONFIG_PACKAGE_luci-proto-ppp=y
CONFIG_PACKAGE_luci-theme-bootstrap=y
CONFIG_PACKAGE_rpcd=y
CONFIG_PACKAGE_rpcd-mod-rrdns=y
CONFIG_PACKAGE_uhttpd=y
__EOF__

Expand to full config:
make defconfig

Make some modifications with:
make menuconfig

Build the images:
make

Target images can be found in '''bin/targets/ramips/rt305x/''':
tree bin/targets/ramips/rt305x/
bin/targets/ramips/rt305x/
|-- config.seed
|-- openwrt-ramips-rt305x-device-rt5350f-olinuxino-evb-plus.manifest
|-- openwrt-ramips-rt305x.manifest
|-- openwrt-ramips-rt305x-root.squashfs
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-uImage.bin
|-- openwrt-ramips-rt305x-uImage-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux.bin
|-- openwrt-ramips-rt305x-vmlinux.elf
|-- openwrt-ramips-rt305x-vmlinux-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux-initramfs.elf

=== OpenWRT ===
Make a directory:
# mkdir some_dir
# cd some_dir

Download sources:
# git clone https://github.com/OLIMEX/openwrt -b rt5350f

Go into openwrt directory:
# cd openwrt

You can use our config:
# make

or if you want to change something:
# make menuconfig
# make

After some time build will finish. The image is found under:
'''build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_rt305x/\'''
'''openwrt-ramips-rt305x-olinuxino-rt5350f-squashfs-sysupgrade.bin'''

Place that file on some tftp server and then upload it to the board.

=Demo projects=

*First steps video with RT5350F-OLinuXino-EVB by Leon Anavi: [https://www.youtube.com/watch?v=-MsywWtN79c https://www.youtube.com/watch?v=-MsywWtN79c]

= Images changelog =

== Release-2 (06 JUL 2015) ==
The following changes were made:

* Upgraded kernel version to 3.18.17
* Inverted wlan led polarity - this way it blink when WiFi is on
* Fixed firmware partition size - https://github.com/OLIMEX/openwrt/issues/1

RT5350F-OLinuXino

2019-04-03T13:16:40Z

StefanM: /* Building OpenWRT */

=RT5350F-OLinuXino official images build instructions=

==Overview==

==Quick-start==

1. Connect USB<->serial cable between the UART0 pins of the board and your personal computer.

2. Open your favourite serial terminal software on the COM port, created by your USB<->serial cable.

3. Set the baud rate for the connection to 57600.

4. Power on RT5350F-OLinuXino-EVB.

==Prebuilt files and system restore==

RT5350F-OLinuXino comes with an image loaded into the SPI flash memory. If something goes wrong you can restore the original image.

Two of the prebuilt files (bootloader.img and openwrt.bin) can be uploaded to the board via the built-in uboot. If your uboot is damaged beyond repair you might need a programmer to recover the software of the board. The other two files (that contain uboot) require a programming tool (uboot+factory.bin and uboot+factory+openwrt.bin). The board comes programmed with the image called uboot+factory+openwrt.bin. See [[#Upload prebuilt images using uboot]] or [[#Upload prebuilt images using programmer tool]].

'''All prebuilt binary files are available for download at our GitHub page. Direct link to the location: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images]'''

The four prebuilt files available are:
* bootloader.img - this is only the bootloader
* openwrt.bin - this is only prebuilt openwrt
The above two can be uploaded using uboot.

* uboot+factory.bin - this is the uboot + factory wifi settings
* uboot+factory+openwrt.bin - this is the uboot + factory wifi settings + openwrt
These two binaries can be uploaded '''only''' via programmer tool (with flashrom).

===Upload prebuilt images using uboot===
Reboot the board and you'll see:
U-Boot 1.1.3 (Apr 20 2015 - 13:25:55)

Board: RT5350F-OLinuXino DRAM: 32 MB
relocate_code Pointer at: 81fb4000
spi_wait_nsec: 42
spi device id: 1c 30 17 1c 30 (30171c30)
find flash: EN25Q64
raspi_read: from:30000 len:1000
.*** Warning - bad CRC, using default environment

=============================================================
RT5350F-OLinuXino UBoot Version: 4.0.0.0
--------------------------------------------------------------
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_TYPE: SDRAM
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
DRAM_TOTAL_WIDTH: 16 bits
TOTAL_MEMORY_SIZE: 32 MBytes
Flash component: SPI Flash
Date:Apr 20 2015 Time:13:25:55
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

##### The CPU freq = 360 MHZ ####
estimate memory size =32 Mbytes

Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.

===Upload prebuilt OpenWRT using uboot===

Press 2, then y and enter some values for ip, server ip and filename:

You choosed 2
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (10.10.10.123) ==:10.10.10.123
Input server IP (10.10.10.3) ==:10.10.10.3
Input Linux Kernel filename () ==:file.bin

Then your new system will boot.

===Upload prebuilt uboot===

Press 9, then again enter ip address, server ip and filename to upload:

You choosed 9

0
raspi_read: from:40028 len:6
.

9: System Load Boot Loader then write to Flash via TFTP.
Warning!! Erase Boot Loader in Flash then burn new one. Are you sure?(Y/N)

Press '''Y''' and continue:

Input device IP (10.10.10.123) ==:10.10.10.123
Enter some static address for the device, for example ''192.168.0.201''.

Next enter server address, for example ''192.168.0.15'':

Input server IP (10.10.10.3) ==:192.168.0.15

Finally enter filename:

Input Uboot filename () ==:bootloader.img

'''Don't forget to plug LAN cable.''' You should see something like that:

Got it
#####################
done
Bytes transferred = 106976 (1a1e0 hex)
NetBootFileXferSize= 0001a1e0
raspi_erase_write: offs:0, count:1a1e0
raspi_erase: offs:0 len:10000
.
raspi_write: to:0 len:10000
.
raspi_read: from:0 len:10000
.raspi_read: from:10000 len:10000
.raspi_erase: offs:10000 len:10000
.
raspi_write: to:10000 len:10000
.
raspi_read: from:10000 len:10000
.Done!

===Upload prebuilt images using programmer tool===

We will use [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD/ ARM-USB-OCD]. It has FT2232 chip which can be used to in SPI master mode. You can also use ARM-USB-TINY; ARM-USB-TINY-H; ARM-USB-OCD-H or any FT2232-based debugger.

Connect ARM-USB-OCD with RT5350F-OLinuXino-EVB according the schematic below (for the blue wire GND you can also use other GND pins available at the board; the GND is common):

[[File:Arm-usb-ocd.png|480px]]

'''RST_RT''' jumper MUST be closed. Then power the board to become ready writing.

Download flashrom software and build it using instructions on the site.

To program the SPI flash run:
flashrom -p ft2232_spi:type=arm-usb-ocd -w file.bin

Then wait some minutes for process to complete.

==Building uboot==

Get the sources from:
git clone https://github.com/OLIMEX/u-boot_RT5350F-OLinuXino
cd u-boot_RT5350F-OLinuXino

Target must be build with gcc3.4! This is very important because with another versions of GCC the build process will fail. You can find that version from '''Ralink SDK'''. Use Google to find it.

Run
make menuconfig

You'll see that the default location is /opt/buildroot-gcc342/bin. Change that with your path.

To actually build u-boot run:
make

At the end of the process you'll see something like this

===============<<IMPORTANT>>==================
Notes:Uboot firmware in flash is uboot.img NOT uboot.bin
================================================

./tools/mkimage -A mips -T standalone -C none \
-a 0x80200000 -e 0x80200000 \
-n "SPI Flash Image" \
-r SDR -s 16 -t 32 -u 16 \
-y 0x0 -z 0x0 -w 0xFF -d uboot.bin uboot.img
Image Name: SPI Flash Image
Created: Thu May 14 08:23:19 2015
Image Type: MIPS Linux Standalone Program (uncompressed)
Data Size: 106912 Bytes = 104.41 kB = 0.10 MB
Load Address: 0x80200000
Entry Point: 0x80200000
DRAM Parameter: 6 (Parm0=0 Parm1=0)

The image '''uboot.img''' can be uploaded via tftp.

==Building OpenWRT==

=== OpenWRT 18.06 ===
=== OpenWRT ===
Make a directory:
# mkdir some_dir
# cd some_dir

Download sources:
# git clone https://github.com/OLIMEX/openwrt -b rt5350f

Go into openwrt directory:
# cd openwrt

You can use our config:
# make

or if you want to change something:
# make menuconfig
# make

After some time build will finish. The image is found under:
'''build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_rt305x/\'''
'''openwrt-ramips-rt305x-olinuxino-rt5350f-squashfs-sysupgrade.bin'''

Place that file on some tftp server and then upload it to the board.

=Demo projects=

*First steps video with RT5350F-OLinuXino-EVB by Leon Anavi: [https://www.youtube.com/watch?v=-MsywWtN79c https://www.youtube.com/watch?v=-MsywWtN79c]

= Images changelog =

== Release-2 (06 JUL 2015) ==
The following changes were made:

* Upgraded kernel version to 3.18.17
* Inverted wlan led polarity - this way it blink when WiFi is on
* Fixed firmware partition size - https://github.com/OLIMEX/openwrt/issues/1

SAM9-L9260

2019-03-22T14:48:48Z

StefanM: /* Preparing rootfs */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:
git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Get the patches:
cd linux
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0001-Update-SAM9-L9260-dts.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0002-Add-Olimex-SAM9-L9260-defconfig.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0003-Fix-subpage-writes-and-cs-deselect.patch | git am

Compile kernel and dtb:
make ARCH=arm olimex_sam9_l9260_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage dtbs

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 124KiB (126976)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 2048
* '''LEB count''' -> Number of LEBs in the rootfs mtd partition, default: 4031

Create ubifs volume:

sudo mkfs.ubifs -d armel-lenny -o lenny.ubifs -m 2048 -e 126976 -c 4024

Generate ubifs image:

cat > ubinize.ini << __EOF__
[rootfs_volume]
mode=ubi
image=lenny.ubifs
vol_id=1
vol_type=dynamic
vol_name=rootfs
vol_alignment=1
vol_flags=autoresize
__EOF__
ubinize -vv -o lenny.img -m 2048 -p 128KiB ubinize.ini -s 512

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-22T07:27:55Z

StefanM: /* Building kernel */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:
git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Get the patches:
cd linux
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0001-Update-SAM9-L9260-dts.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0002-Add-Olimex-SAM9-L9260-defconfig.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0003-Fix-subpage-writes-and-cs-deselect.patch | git am

Compile kernel and dtb:
make ARCH=arm olimex_sam9_l9260_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage dtbs

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 126KiB (131072)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 512
* '''LEB count''' -> Number of LEBs in the rootfs mtd partition, default: 4031

Create ubifs volume:

sudo mkfs.ubifs -d armel-lenny -o lenny.ubifs -m 2048 -e 129024

Generate ubifs image:

cat > ubinize.ini << __EOF__
[rootfs_volume]
mode=ubi
image=lenny.ubifs
vol_id=1
vol_type=dynamic
vol_name=rootfs
vol_alignment=1
vol_flags=autoresize
__EOF__
ubinize -vv -o lenny.img -m 2048 -p 128KiB ubinize.ini -s 512

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-22T07:26:52Z

StefanM: /* Building kernel */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:
git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Get the patches:
cd linux
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0001-Update-SAM9-L9260-dts.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0002-Add-Olimex-SAM9-L9260-defconfig.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0003-Fix-subpage-writes-and-cs-deselect.patch | git am

Compile kernel and dtb:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage dtbs

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 126KiB (131072)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 512
* '''LEB count''' -> Number of LEBs in the rootfs mtd partition, default: 4031

Create ubifs volume:

sudo mkfs.ubifs -d armel-lenny -o lenny.ubifs -m 2048 -e 129024

Generate ubifs image:

cat > ubinize.ini << __EOF__
[rootfs_volume]
mode=ubi
image=lenny.ubifs
vol_id=1
vol_type=dynamic
vol_name=rootfs
vol_alignment=1
vol_flags=autoresize
__EOF__
ubinize -vv -o lenny.img -m 2048 -p 128KiB ubinize.ini -s 512

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-22T07:25:58Z

StefanM: /* Building kernel */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:

git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Get the patches:
cd linux
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0001-Update-SAM9-L9260-dts.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0002-Add-Olimex-SAM9-L9260-defconfig.patch | git am
wget -O- https://raw.githubusercontent.com/OLIMEX/SAM9-L9260-Linux/master/0003-Fix-subpage-writes-and-cs-deselect.patch | git am

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 126KiB (131072)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 512
* '''LEB count''' -> Number of LEBs in the rootfs mtd partition, default: 4031

Create ubifs volume:

sudo mkfs.ubifs -d armel-lenny -o lenny.ubifs -m 2048 -e 129024

Generate ubifs image:

cat > ubinize.ini << __EOF__
[rootfs_volume]
mode=ubi
image=lenny.ubifs
vol_id=1
vol_type=dynamic
vol_name=rootfs
vol_alignment=1
vol_flags=autoresize
__EOF__
ubinize -vv -o lenny.img -m 2048 -p 128KiB ubinize.ini -s 512

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-20T12:09:32Z

StefanM: /* Generate UBIFS image */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:

git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 126KiB (131072)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 512
* '''LEB count''' -> Number of LEBs in the rootfs mtd partition, default: 4031

Create ubifs volume:

sudo mkfs.ubifs -d armel-lenny -o lenny.ubifs -m 2048 -e 129024

Generate ubifs image:

cat > ubinize.ini << __EOF__
[rootfs_volume]
mode=ubi
image=lenny.ubifs
vol_id=1
vol_type=dynamic
vol_name=rootfs
vol_alignment=1
vol_flags=autoresize
__EOF__
ubinize -vv -o lenny.img -m 2048 -p 128KiB ubinize.ini -s 512

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-20T12:07:33Z

StefanM: /* Generate UBIFS image */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:

git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 126KiB (131072)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 512
* '''LEB count''' -> Number of LEBs in the rootfs mtd partition, default: 4031

Create ubifs volume:

sudo mkfs.ubifs -d armel-lenny -o lenny.ubifs -m 2048 -e 129024

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-20T12:03:10Z

StefanM: /* Generate UBIFS image */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==

=== Building at91bootstrap ===

Get the sources with:

git clone -b olimex https://github.com/OLIMEX/at91bootstrap.git

Go to the cloned folder and select SAM9-L9260 configuration:

cd at91bootstrap
make sam9_l9260_uboot_defconfig

Compile the sources with:

make CROSS_COMPILE=arm-linux-gnueabi-

The bootstrap file can be found at:

binaries/sam9_l9260-dataflashcardboot--3.8.11.bin

=== Building kernel ===

Get the sources:

git clone --depth 1 --branch linux-5.0.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

=== Preparing rootfs ===

In this tutorial [https://wiki.debian.org/DebianLenny Debian Lenny] will be used. The build process may vary, depending on host PC system. The following instructions are tested on '''Ubuntu 18.04'''.

Install required packages:

sudo apt-get update
sudo apt install -y debootstrap qemu-arm-static mtd-utils

Create empty directory, which will contain the new rootfs:

mkdir armel-lenny

Run debootstrap and wait to finish:

sudo qemu-debootstrap --arch armel lenny ./armel-lenny

Login into the new rootfs with:

sudo chroot ./armel-lenny

Set hostname and password:

echo 'sam9-l9260' > /etc/hostname
passwd

Set locales:

apt-get install locales
dpkg-reconfigure locales

Configure login console:

sed -i "s/.*T0:.*/T0:2345:respawn:\/sbin\/getty\ -L\ ttyS0\ 115200\ vt100/g" /etc/inittab

Install some additional packages:
apt-get install autoconf autotools-dev bash-completion bind9-host binutils busybox cpp ethtool ftp initramfs-tools less lsof m4 mime-support mtd-utils ntp openssh-client python telnet texinfo udev usbutils whois

Configure fstab:

cat > /etc/fstab << __EOF__
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
rootfs / jffs2 rw 0 0

__EOF__

Create missing /dev/shm folder:

sed -i '36i\\t[ ! -d /dev/shm ] && mkdir --mode=755 /dev/shm' /etc/init.d/mountdevsubfs.sh

Configure networking:

cat >> /etc/network/interfaces << __EOF__
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

__EOF__

Exit from chroot:

exit

==== Generate JFFS2 image ====

Run:

sudo mkfs.jffs2 -r armel-lenny/ -o lenny.jffs2 -e 128 -s 512 -p -n

Where:
* -e 128 - 128KiB of erase block
* -s 512 - 512B page size
* -p - pad the output to match erase block size
* -n - do not write cleanmarkers

==== Generate UBIFS image ====

Before creating image some NAND parameters must be known. The shown default values are for '''K9F4G08U0F''' chip.

* '''PEB''' -> Physical erase block, default: 128KiB (131072)
* '''LEB''' -> Logical erase block, default : 126KiB (131072)
* '''min. I/O size''' -> Page size, default : 2048
* '''sub-page size''' -> Subpage size, default : 512

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:Atmel]]

SAM9-L9260

2019-03-20T11:29:17Z

StefanM: /* Generate JFFS2 image */

SAM9-L9260

2019-03-19T06:40:53Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-19T06:39:54Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-19T06:39:36Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-18T13:17:45Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-18T13:17:21Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-18T12:39:46Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-18T12:31:02Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-18T09:55:43Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-18T09:06:50Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-15T13:53:44Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-15T13:50:13Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-15T13:39:23Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-15T12:57:20Z

StefanM: /* Preparing rootfs */

SAM9-L9260

2019-03-15T12:56:14Z

StefanM: /* Preparing rootfs */