SAMA5D27-SOM1-EK1 problem with boot at91bootstap from qspiflash

Moderator: nferre

supersonic31337
Posts: 5
Joined: Tue Feb 19, 2019 11:55 am

SAMA5D27-SOM1-EK1 problem with boot at91bootstap from qspiflash

Wed Feb 20, 2019 4:54 pm

Hello all! I have developing board ATSAMA5d27-SOM1_EK1, doing all as decribed here
https://www.at91.com/linux4sam/bin/view ... edMainPage
But "at91bootstap" and "u-boot" image I place to qspiflash, after connecting to board with terminal I got just string "RomBOOT", after press reset button had same results, no any at91bootstrap or u-boot ouput strings dosnt appear.
blue_z
Location: USA
Posts: 1943
Joined: Thu Apr 19, 2007 10:15 pm

Re: SAMA5D27-SOM1-EK1 problem with boot at91bootstap from qspiflash

Thu Feb 21, 2019 11:51 pm

supersonic31337 wrote: I have developing board ATSAMA5d27-SOM1_EK1, doing all as decribed here
https://www.at91.com/linux4sam/bin/view ... edMainPage
If you have a SAMA5D27-SOM1-EK1 board, then why are you using the SAMA5D2 Xplained web page?
That's two different boards that use similar yet distinct SoCs.


supersonic31337 wrote: But "at91bootstap" and "u-boot" image I place to qspiflash, after connecting to board with terminal I got just string "RomBOOT", after press reset button had same results, no any at91bootstrap or u-boot ouput strings dosnt appear.
Exactly what image of AT91Bootstrap did you use?
How did you verify that the write was successful?

Regards
supersonic31337
Posts: 5
Joined: Tue Feb 19, 2019 11:55 am

Re: SAMA5D27-SOM1-EK1 problem with boot at91bootstap from qspiflash

Fri Feb 22, 2019 10:58 am

If you have a SAMA5D27-SOM1-EK1 board, then why are you using the SAMA5D2 Xplained web page?
That's two different boards that use similar yet distinct SoCs.
Sure, I know this is two different boards, but when building bootstrap, I used config for my board
$ git clone git://github.com/linux4sam/at91bootstrap.git
$ cd at91bootstrap/
$ make mrproper
$ make sama5d27_som1_ekqspi_uboot_defconfig
$make
In "binaries" folder I got new "sama5d27_som1_ek-dataflashboot--3.8.12.bin"
After it actions I use sam-ba tool
Exactly what image of AT91Bootstrap did you use?
How did you verify that the write was successful?

Code: Select all

D:\sam-ba_3.3-beta1>sam-ba -p serial -b sama5d27-som1-ek -a qspiflash -c writeboot:sama5d27_som1_ek-dataflashboot--3.8.12.bin -c verify:sama5d27_som1_ek-dataflashboot--3.8.12.bin
Opening serial port 'COM4'
Connection opened.
Detected memory size is 8388608 bytes.
Page size is 256 bytes.
Buffer is 90368 bytes (353 pages) at address 0x00229e60.
Supported erase block sizes: 4KB
Executing command 'writeboot:sama5d27_som1_ek-dataflashboot--3.8.12.bin'
Appending 52 bytes of padding to fill the last written page
Wrote 9216 bytes at address 0x00000000 (100.00%)
Executing command 'verify:sama5d27_som1_ek-dataflashboot--3.8.12.bin'
Appending 52 bytes of padding to fill the last written page
Verified 9216 bytes at address 0x00000000 (100.00%)
Connection closed.
Also, Im not sure, whats boot config parametrs should will be set, In configuration file for building bootstrap I see

Code: Select all

CONFIG_SAMA5D27_SOM1_EK=y
CONFIG_RAM_128MB=y
CONFIG_SPI_CLK=66000000
CONFIG_QSPI=y
CONFIG_QSPI_BUS1=y
CONFIG_QSPI1_IOSET_2=y
CONFIG_IMG_ADDRESS="0x00008000"
CONFIG_JUMP_ADDR="0x23f00000"
CONFIG_DEBUG=y
# CONFIG_ENTER_NWD is not set
Im use:

Code: Select all

D:\sam-ba_3.3-beta1>sam-ba -p serial -b sama5d27-som1-ek -a bootconfig -c writecfg:bureg0:ext_mem_boot,sdmmc1,sdmmc0,qspi0_ioset1,qspi1_ioset2,jtag_ioset3
Opening serial port 'COM4'
Connection opened.
Executing command 'writecfg:bureg0:ext_mem_boot,sdmmc1,sdmmc0,qspi0_ioset1,qspi1_ioset2,jtag_ioset3'
Setting BUREG0 to 0x00060004 (QSPI0_IOSET1,QSPI1_IOSET2,SPI0_IOSET1,SPI1_IOSET1,NFC_IOSET1,SDMMC0,SDMMC1,UART1_IOSET1,JTAG_IOSET3,EXT_MEM_BOOT)
Connection closed.
blue_z
Location: USA
Posts: 1943
Joined: Thu Apr 19, 2007 10:15 pm

Re: SAMA5D27-SOM1-EK1 problem with boot at91bootstap from qspiflash

Fri Feb 22, 2019 11:20 pm

You neglect to describe your development host machine and the toolchain.
A possible cause of execution failure by AT91Bootstrap is known to be bad code generation by some toolchains, which is mentioned in the README.txt and KNOWN_ISSUES files in the source code.
Also see Build AT91Bootstrap from sources.

Regards

Return to “SAMA5-based”

Who is online

Users browsing this forum: Bing [Bot] and 0 guests