blob: 8a33fec32fdc325e7bb56ab717611ec90f527131 [file] [log] [blame]
Nobuhiro Iwamatsu16f47c92013-12-18 15:31:55 +09001-------------------------------------------------
2 Simple steps used to test the SH-QSPI at U-Boot
3-------------------------------------------------
4
5#0, Currently, SH-QSPI is used by lager board (Renesas ARM SoC R8A7790)
6 and koelsch board (Renesas ARM SoC R8A7791). These boot from SPI ROM
7 basically. Thus, U-Boot start, SH-QSPI will is operating normally.
8
9#1, build U-Boot and load u-boot.bin
10
11 => tftpboot 40000000 u-boot.bin
12 sh_eth Waiting for PHY auto negotiation to complete.. done
13 sh_eth: 100Base/Half
14 Using sh_eth device
15 TFTP from server 192.168.169.1; our IP address is 192.168.169.79
16 Filename 'u-boot.bin'.
17 Load address: 0x40000000
18 Loading: ############
19 2.5 MiB/s
20 done
21 Bytes transferred = 175364 (2ad04 hex)
22
23#2, Commands to erase/write u-boot to flash device
24
25 Note: This method is description of the lager board. If you want to use the
26 other boards, please change the value according to each environment.
27
28 => sf probe 0
29 SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 64 KiB, total 64 MiB
30 => sf erase 80000 40000
31 SF: 262144 bytes @ 0x80000 Erased: OK
32 => sf write 40000000 80000 175364
33 SF: 1528676 bytes @ 0x80000 Written: OK
34 =>
35
36#3, Push reset button.
37
38 If you're written correctly and driver works properly, U-Boot starts.