Updating u-boot

Kernel hacking implies a lot of iterative small changes followed by a deployment on the board, that  become really annoying if we have to switch the SD card from the board to the computer in order to copy the kernel and put it back to the board again, without speaking about the degradation of the SD card adapter by these multiple mechanical operations.

A solution is to have u-boot to download the kernel directly from the compilation host. I used to have tftpboot loading the kernel and the dtb. For this, we need an u-boot supporting the rock960 and hopefully the upstream support is almost ready (patches are submitted and very likely they will be merged soon 09-26-2018). In addition an USB dongle with ASIX chipset must be used (it is the one I'm used to have), you can find this with the following keywords over internet : USB 2.0 RJ45 Lan Ethernet Asix AX8872B

Until we have those patches merged, this is the quick summary of what is needed to compile u-boot for the rock960.

Before going forward, make sure:

  • no USB-A connected but only USB-C. The board works in OTG or host mode, so if something is plugged on the USB-A, the OTG won't work
  • no MMC is inserted. . If a MMC card is inserted, the flashing mode won't switch. 
  • flashing the board with the rk tools as root
  • USB2 only (USB3 not supported on u-boot)

Generating the u-boot:

  • Clone the upstream u-boot git tree
    • git clone git://git.denx.de/u-boot.git
  • After setting the .pwclientrc file with the u-boot project, apply the patches with the command  (please refer to pwclient documentation on the patchwork website):
      • pwclient git-am -s -p uboot 975858 975861 975860 975859
    • Note these patches may be already merged when you read this howto
  • Follow the instructions you can find in the README file in the u-boot source tree
    • board/vamrs/rock960_rk3399/README
  • In case you are lost, get some additionnal information from the 96boards rock960 howto
There are two recipes at one moment for u-boot, SPL and miniloader. Use the latter if you have a 4GB memory board.

At this point, you have compiled and flashed u-boot. However PHY USB support and USB ethernet dongle will be missing, so you have to tweak the configuration via menuconfig.
  • make ARCH=arm64 menuconfig
  • Set USB phy for Rockchip option (CONFIG_ROCKCHIP_USB2_PHY=y)
    • Device drivers => USB Support => Rockchip USB2 PHY
  • Set USB ethernet dongle option (CONFIG_USB_ETHER_ASIX=y)
    • Device drivers => USB Support => USB to Ethernet Controller Drivers => ASIX AX8817X (USB 2.0) support
And redo the operations compilation and flashing (I could have added those information before but for the sake of clarity I decided to not nest them with the others).

At this point, u-boot is compiled and flashed on the board. We now begin the configuration steps, for this, let's remove the USB-C and plug the USB ethernet dongle, reset the board.

On the u-boot prompt, type usb start and see if it finds an ethernet dongle


USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00  
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) found

If yes, then we can go further.


Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Custom kernel compilation

Compilation of the upstream kernel Yes, I'm serious, the rock960 is supported mainline (without the graphics obviously). Well to be exact, all the bits are in the soc maintainer tree and will be merged for 4.21. But until then, you should use the arm-soc tree, or mmind tree with the for-next branch (Dec, 22 2018). Build the kernel:    make ARCH=arm64 menuconfig    make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 12 Image dtbs Generate the image: Create the configuration file  rock960-rk3399-kernel.its with the following content: /dts-v1/; / { description = "Mainline kernel image with one or more FDT blobs"; #address-cells = <1>; images { kernel@1 { description = "Mainline kernel"; data = /incbin/("./arch/arm64/boot/Image"); type = "kernel"; arch = "arm64"; os = "linux"; /* load = <0x2080000>; entry = <0x2080000>; */ load =
Lire la suite
Image
The 96boards - rock960 My goals with this board The rock960  showed interesting technical characteristics, I wanted to acquire this board and have fun. The decision to spend some money on this board was greatly influenced by the upstream support. It may not be complete but I know Heiko Stubner, maintainer of the rockchip platform, is doing a great job so it would be a question of time before having all the bits supported mainstream. My goal is to have this board working with an upstream kernel, if it is close to full support, I'm perfectly fine to contribute and bring my stone to the edifice. Ordering the board There are two versions of this board, a light one with 2GB of memory and 16GB of eMMC and a stronger one with 4GB of memory and 32GB of eMMC. I choose the later because, by experience, advanced benchmarking programs often blow memory and are impossible to run on a 2GB system without triggering the Out-Of-Memory killer (swap is not an option for obvious reason
Lire la suite
Booting a BSP kernel on the rock960 board Before hacking the board, I want to evaluate it and for this, a kernel supporting the board is needed. Hopefully there is a full debian image with a 4.4 kernel  available at varms.com. The image partitions layout is described on the 96boards web site . I prefer to use the SD card to install the system. As my console is setup, I can simply power up the board with the micro SD card inserted in and see what happens. After a few seconds, I have a prompt :) The kernel version is  4.4.103 , debian is 9.2 Supported features Network Wifi was not tested but it appears to work for the "iwlist scanning" with some warnings "wl_escan_handler : escan is not ready ndev" The ethernet - USB adapter with an asix AX88772B is detected and the network works fine Power management The idle states are managed through PSCI, there are three states (WFI, cpu sleep and cluster sleep), the characteristics for each cluster are
Lire la suite