Marcellus Pereira

Members
  • Content Count

    9
  • Joined

  • Last visited

  1. Hello guys. After a long time unsuccesfully trying to use a NanoPi Neo to record I2S data, I wonder if is there some NanoPi board that is capable of such thing. Can you suggest one? Thank you very much!
  2. I don´t know if this thread is too much old... I have the same problem: using the H3 (NanoPI Neo) I2S0 as slave and capture audio data. Following this thread ( ) I was able to record some audio signals from an external I2S master generator. However, the signal seems to "slide" in blocks, as if the receiver buffer was corrupted or had missing samples. Maybe a DMA problem? The screenshot shows the audio actually recorded using an DScope Series III as I2S source (ds-NET VSIO Adapter). The codec driver is the adau-7002, and it´s showed after the module is loaded. Then, I record a few seconds of the incoming data stream. Do you have any news about this matter? Thank you very much!
  3. I thought I would have to write another driver, but this flash chip has the same identifications of the ATMEL AT25DF321A. And there is the line CONFIG_SPI_FLASH_ATMEL=y on the configuration file. This ID is specified in the file named "spi_flash_ids.c", line 47: const struct spi_flash_info spi_flash_ids[] = { #ifdef CONFIG_SPI_FLASH_ATMEL /* ATMEL */ {"at45db011d", INFO(0x1f2200, 0x0, 64 * 1024, 4, SECT_4K) }, {"at45db021d", INFO(0x1f2300, 0x0, 64 * 1024, 8, SECT_4K) }, {"at45db041d", INFO(0x1f2400, 0x0, 64 * 1024, 8, SECT_4K) }, {"at45db081d", INFO(0x1f2500, 0x0, 64 * 1024, 16, SECT_4K) }, {"at45db161d", INFO(0x1f2600, 0x0, 64 * 1024, 32, SECT_4K) }, {"at45db321d", INFO(0x1f2700, 0x0, 64 * 1024, 64, SECT_4K) }, {"at45db641d", INFO(0x1f2800, 0x0, 64 * 1024, 128, SECT_4K) }, {"at25df321a", INFO(0x1f4701, 0x0, 64 * 1024, 64, SECT_4K) }, {"at25df321", INFO(0x1f4700, 0x0, 64 * 1024, 64, SECT_4K) }, {"at26df081a", INFO(0x1f4501, 0x0, 64 * 1024, 16, SECT_4K) }, #endif And the H3 uses the file "sunxi_spi_spl.c", with the CONFIG_SUNXI_GEN_SUN6I. At least, I think... It should work, right? :-( []s Marcellus
  4. Now, the board boots from SPI flash, but I can´t see the flash using teh sf command: => sf probe Invalid bus 0 (err=-19) Failed to initialize SPI flash at 0:0 => sf probe 0:0 Invalid bus 0 (err=-19) Failed to initialize SPI flash at 0:0 => The configuration of U-boot is: The SPI0 registers seems to not be initialized: => md.w 0x01c68000 36 01c68000: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 01c68010: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 01c68020: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 01c68030: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 01c68040: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 01c68050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 01c68060: 0000 0000 0000 0000 0000 0000 ............ => Using an oscilloscope, I can see the /CS pin changing, during the boot process. Howerver, the same pin stays in "1" when I type the "sf probe" command. Any ideas? Thanks again, Marcellus
  5. zador, you are absoutely right! :-) => version U-Boot 2017.11-MPS (Apr 20 2018 - 11:51:50 -0300) Allwinner Technology arm-linux-gnueabihf-gcc (Linaro GCC 7.2-2017.11) 7.2.1 20171011 GNU ld (Linaro_Binutils-2017.11) 2.28.2.20170706 => Thank you very much!
  6. Well, the problem was the enabled "Global Protection bit". Now, I can save and erase the U-Boot from the SPI Flash: osboxes@osboxes:~/nanoPi/sunxi-tools$ hexdump spi-flash-read-data.bin -n 512 0000000 457f 464c 0101 0001 0000 0000 0000 0000 0000010 0002 0028 0001 0000 0000 4a00 0034 0000 0000020 2f08 0030 0200 0500 0034 0020 0003 0028 0000030 0022 0021 0001 0000 0000 0001 0000 4a00 0000040 0000 4a00 f6c4 0004 f6c4 0004 0007 0000 0000050 0000 0001 0002 0000 f63c 0005 f63c 4a04 0000060 f63c 4a04 0088 0000 0088 0000 0006 0000 0000070 0004 0000 e551 6474 0000 0000 0000 0000 0000080 0000 0000 0000 0000 0000 0000 0007 0000 0000090 0010 0000 0000 0000 0000 0000 0000 0000 00000a0 0000 0000 0000 0000 0000 0000 0000 0000 * 0000200 osboxes@osboxes:~/nanoPi/sunxi-tools$ hexdump -n 512 ../build/cache/sources/u-boot/v2017.11/u-boot 0000000 457f 464c 0101 0001 0000 0000 0000 0000 0000010 0002 0028 0001 0000 0000 4a00 0034 0000 0000020 2f08 0030 0200 0500 0034 0020 0003 0028 0000030 0022 0021 0001 0000 0000 0001 0000 4a00 0000040 0000 4a00 f6c4 0004 f6c4 0004 0007 0000 0000050 0000 0001 0002 0000 f63c 0005 f63c 4a04 0000060 f63c 4a04 0088 0000 0088 0000 0006 0000 0000070 0004 0000 e551 6474 0000 0000 0000 0000 0000080 0000 0000 0000 0000 0000 0000 0007 0000 0000090 0010 0000 0000 0000 0000 0000 0000 0000 00000a0 0000 0000 0000 0000 0000 0000 0000 0000 * 0000200 osboxes@osboxes:~/nanoPi/sunxi-tools$ cmp -b spi-flash-read-data.bin ../build/cache/sources/u-boot/v2017.11/u-boot osboxes@osboxes:~/nanoPi/sunxi-tools$ Unfortunately, the board still misses the U-Boot and shows up as "Onda V972 tablet in flash mode". :-(
  7. Definitely there´s something wrong... :-) osboxes@osboxes:~/nanoPi/sunxi-tools$ hexdump spi-flash-read-data.bin -n 100 0000000 6571 6160 2c61 7024 0070 0000 405b 5041 0000010 5100 5241 1045 0208 7060 2120 0820 4040 0000020 3030 3038 000a 0000 3167 0a3d 7472 3d31 0000030 0a30 7064 3173 303d 710a 734d 3267 0a3d 0000040 7472 3d32 0a30 7064 3273 303d 710a 734d 0000050 3367 0a3d 7472 3d33 0a30 7064 3373 303d 0000060 710a 734d 0000064 osboxes@osboxes:~/nanoPi/sunxi-tools$ hexdump -n 100 ../build/cache/sources/u-boot/v2017.11/u-boot 0000000 457f 464c 0101 0001 0000 0000 0000 0000 0000010 0002 0028 0001 0000 0000 4a00 0034 0000 0000020 2f08 0030 0200 0500 0034 0020 0003 0028 0000030 0022 0021 0001 0000 0000 0001 0000 4a00 0000040 0000 4a00 f6c4 0004 f6c4 0004 0007 0000 0000050 0000 0001 0002 0000 f63c 0005 f63c 4a04 0000060 f63c 4a04 0000064 osboxes@osboxes:~/nanoPi/sunxi-tools$
  8. Thank you very much, Igor! It works perfectly. Now I will find why the sf command is unable to find the SPI Flash chip (probably, because I need to write a driver). I´ll post updates here, in case someone is interested. []s Marcellus
  9. Dear All, I´m trying to boot my nanoPi NEO from an external SPI Flash. Actually, I attached a small AT25DF321A and I´m able to see it´s is working: when in FEL mode, using a slightly modified sunxi-tools, there´s the message: osboxes@osboxes:/tmp/marcellus-sunxi-tools/sunxi-tools$ sudo ./sunxi-fel spiflash-info Manufacturer: Adesto AT25DF321A (1Fh), model: 47h, size: 4096k bytes. I can write to and read from it, too. Now, I need to compile U-BOOT with the command "sf" (I know I will need to write another spi driver, but baby steps...). The problem is: when I change the U-BOOT´s .config file and call the "compile.sh" script using the option CREATE_PATCHES=yes, my .config file is overwritten. Is there a way to make the modifications made with the "make menuconfig" command be persistent? Thank you very much! Marcellus