RT5350F-OLinuXino official images build instructions
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
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 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: 188.8.131.52
ASIC 5350_MP (Port5<->None)
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
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:
Bytes transferred = 106976 (1a1e0 hex)
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
Upload prebuilt images using programmer tool
We will use 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:
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.
Get the sources from:
git clone https://github.com/OLIMEX/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.
You'll see that the default location is /opt/buildroot-gcc342/bin. Change that with your path.
To actually build u-boot run:
At the end of the process you'll see something like this
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.
Make a directory:
# mkdir some_dir
# cd some_dir
# git clone https://github.com/OLIMEX/openwrt -b rt5350f
Go into openwrt directory:
# cd openwrt
You can use our config:
or if you want to change something:
# make menuconfig
After some time build will finish. The image is found under:
Place that file on some tftp server and then upload it to the board.
Release-2 (06 JUL 2015)
The following changes were made: