I can not make SPI_CS1 work from register, also find the following small line from datasheet(page 87): So does this mean CS should be only controlled by software but not that SPI_ENABLE register? SPI_ENABLE is just a switch? But how CS0 be controlled? :'( Ahhhh, this kills me, maybe only ralink developer knows how to […]
🙂 So many mess things, delayed the SPI & MicroSD process. I have tried many many ways recently, finally get some results, still need more check/read/fix etc… First, I read all the code about SPI and MMC. Also the RT5350F datasheet, SPI part. Then, I tried to modify that spi-rt2880.c to support SPI1. Thanks for […]
SPI microSD is not done yet 🙂 Just finish an easy driver patch. This patch is used to get unique id from flash chip. That id is also VoCore Unique ID(unless you change the flash chip). It will be used to get back factory setting(include mac address, wifi parameter, etc.) If you change the flash […]
In linux kernel, there are several important files for SPI/MMC part. spi.c spi.h mmc_spi.c mmc_spi.h of_mmc_spi.c From openwrt side, one file related to it. spi-rt2880.c But spi-rt2880.c only supports one SPI device, the flash chip. There is a patch but not work, after I apply that, get the following error log. [ 15.050000] mmc_spi spi32766.1: […]
These days when I read the linux SPI driver code, I find there is no big issue to have two SPI slave device on one SPI master at driver part. SPI mmc(mircoSD) is mostly used to download, it will take most of SPI traffic. SPI flash is only used when the system is booting…then unless […]
Hardware part do not have big issue now, just pin 9, 10 are the microSD detector pin, but there is no place on PCB, have to ignore them… Now working on the software part, that really stunned me. 😀 I thought that should be already perfectly supported by openwrt driver…But after I check the  driver carefully, I think I […]
The three days I am working on SPI. It is a little hard to route, but I added SPI interface to the pins finally. The upper shows the SPI pins export map. The advantage of this version is all GPIOs(it is real, all 28 GPIOs have exported), and SPI interface is exported too. The […]
To make your customized official uboot or our standard uboot, it requires two steps. Download latest uboot source code from https://github.com/u-boot/u-boot/tags, normally I choose the stable version who is not end with rc. Use our config file from https://github.com/Vonger/vocore2/blob/master/uboot/vocore2_defconfig, replace u-boot-2023.04/configs/vocore2_defconfig, then you can use make menuconfig to choose the option you want. optional: for […]
Official uboot is very different from the mediatek uboot, not that easy to use but very flexible. For example, if my firmware stored in USB disk and I want to update firmware from uboot, I will need to load from usb disk to memory first, then erase flash and write to it all by command. […]
Currently latest version of uboot is working well on VoCore2. But because of the partition is not big enough for all uboot features, we have to do such cut off. We upload the config to https://github.com/Vonger/vocore2/blob/master/uboot/vocore2_defconfig Have a try 🙂 https://vonger.cn/misc/vocore2/u-boot-with-spl.bin 1. This is for 192KB partition of uboot, for mainline version you will need […]