From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Anderson Date: Sun, 2 Feb 2020 01:06:32 -0500 Subject: [PATCH v2 07/11] riscv: Add initial Sipeed Maix support In-Reply-To: <28100babec8b01176862646d9c422a65a7e89bc7.camel@auer.io> References: <3411d84b-5a56-ae4e-1deb-085ef1a4971d@gmail.com> <4c9aa605-013e-a32d-6d90-97286a0080dc@gmail.com> <3e8a4fc6-0ef0-74da-593d-7c0f9e81ca31@gmail.com> <28100babec8b01176862646d9c422a65a7e89bc7.camel@auer.io> Message-ID: <1cf0f5e6-a8b5-85e7-9c64-e27b19c4528f@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 1/30/20 5:21 PM, Lukas Auer wrote: > Interesting, I thought all SD cards support SPI mode. I think it's a different issue, but I wasn't sure. >> The board I am using has some serial issues which makes it difficult to >> flash any large images. I can get u-boot to flash after several >> attempts, but something like the linux kernel is far too unreliable to >> test regularly. I'm going to see if I can get my hands on another k210 >> board which hopefully doesn't have these issues. > > Ah ok, that's unfortunate. Thank you for your efforts! I have since found a computer where the serial works fine (which implies that the USB hardware on my current computer has some issues). I should be able to flash larger binaries fine now, but the current issue is getting the SPI to work. I think there may be some subtle differences between the driver and the manufacturer's sdk. I am also having some clock problems, despite (obstensibly) performing the same incantations as the sdk. I guess this is what happens when they refuse to release a technical reference... --Sean