Here is my steps to program the board. I try to boot from qspi flash but fail...
1. I change the backup register as below,
>sam-ba -p j-link -d sama5d2 -a bootconfig -c writecfg:bscr:valid,bureg0 -c writecfg:bureg0:QSPI0_DISABLED,QSPI1_IOSET2,SPI0_DISABLED,SPI1_DISABLED,NFC_DISABLED,SDMMC0,SDMMC1,EXT_MEM_BOOT
Opening J-Link with S/N '483029471'
Found Atmel SAMA5D2x device
Disabling watchdog
Connection opened.
Executing command 'writecfg:bscr:valid,bureg0'
Setting BSCR to 0x00000004 (BUREG0,VALID)
Executing command 'writecfg:bureg0:QSPI0_DISABLED,QSPI1_IOSET2,SPI0_DISABLED,SPI1_DISABLED,NFC_DISABLED,SDMMC0,SDMMC1,EXT_MEM_BOOT'
Setting BUREG0 to 0x000403f7 (QSPI0_DISABLED,QSPI1_IOSET2,SPI0_DISABLED,SPI1_DISABLED,NFC_DISABLED,SDMMC0,SDMMC1,UART1_IOSET1,JTAG_IOSET1,EXT_MEM_BOOT)
Connection closed.
2. I update the bootstrap and uboot and zImage by sam-ba as well, after reboot, it shows as below and stop,
AT91Bootstrap 3.8.9-00026-gd7a52fb (四 2月 1 14:12:51 CST 2018)
SF: Got Manufacturer and Device ID: bf2643
SF: Copy 0xa0000 bytes from 0x10000 to 0x23f00000
SF: Done to load image
3. Then I can't program any more, it always shows,
Opening J-Link with S/N '483029471'
Error: Unsupported device
fail to program SAMA5D27-SOM1-ek1 qspi flash by sam-ba
Moderator: nferre
- blue_z
- Location: USA
Post
Seems like there are a plethora of salient details that you have neglected to mention.
Did you even verify what was written before trying to execute it?
What did you do to get this message?
Regards
Re: fail to program SAMA5D27-SOM1-ek1 qspi flash by sam-ba
That does not look like a prebuilt binary from Linux4SAM.ryback wrote:2. I update the bootstrap and uboot and zImage by sam-ba as well, after reboot, it shows as below and stop,
AT91Bootstrap 3.8.9-00026-gd7a52fb (四 2月 1 14:12:51 CST 2018)
Seems like there are a plethora of salient details that you have neglected to mention.
Did you even verify what was written before trying to execute it?
That's insufficient context.ryback wrote:3. Then I can't program any more, it always shows,
Opening J-Link with S/N '483029471'
Error: Unsupported device
What did you do to get this message?
Regards
Post
I have done test for SD card and it works. However I would like to try boot from QSPI but never success.
After install the toolchain, I get bootstrap by doing this, $ git clone git://github.com/linux4sam/at91bootstrap.git
then try to build the image,
$ cd at91bootstrap/
$ make mrproper
$ make sama5d27_som1_ekqspi_uboot_defconfig
$ make CROSS_COMPILE=arm-linux-gnueabi-
and I got the image in binaries/at91bootstrap.bin.
The same way I did for u-boot and linux kernel.
After I change the backup register by step. 1 which I did last time, I use sam-ba to program it,
$ sam-ba -p j-link -b sama5d27-som1-ek -a qspiflash -c writeboot:at91bootstrap.bin -c write:u-boot.bin:0x10000 -c write:zImage:0x200000
while all done, I press reset button, and that message shows up.
AT91Bootstrap 3.8.9-00026-gd7a52fb (四 2月 1 14:12:51 CST 2018)
SF: Got Manufacturer and Device ID: bf2643
SF: Copy 0xa0000 bytes from 0x10000 to 0x23f00000
SF: Done to load image
I attached the sceenshot for this.
$sam-ba -p j-link -d sama5d2 -a bootconfig -c readcfg:bscr -c readcfg:bureg0 -c readcfg:bureg1 -c readcfg:bureg2 -c readcfg:bureg3 -c readcfg:fuse
Opening J-Link with S/N '483029471'
Error: Unsupported device
Re: fail to program SAMA5D27-SOM1-ek1 qspi flash by sam-ba
I follow the process from this website, www.at91.com/linux4sam/bin/view/Linux4S ... EKMainPageryback wrote:
2. I update the bootstrap and uboot and zImage by sam-ba as well, after reboot, it shows as below and stop,
AT91Bootstrap 3.8.9-00026-gd7a52fb (四 2月 1 14:12:51 CST 2018)
That does not look like a prebuilt binary from Linux4SAM.
Seems like there are a plethora of salient details that you have neglected to mention.
Did you even verify what was written before trying to execute it?
I have done test for SD card and it works. However I would like to try boot from QSPI but never success.
After install the toolchain, I get bootstrap by doing this, $ git clone git://github.com/linux4sam/at91bootstrap.git
then try to build the image,
$ cd at91bootstrap/
$ make mrproper
$ make sama5d27_som1_ekqspi_uboot_defconfig
$ make CROSS_COMPILE=arm-linux-gnueabi-
and I got the image in binaries/at91bootstrap.bin.
The same way I did for u-boot and linux kernel.
After I change the backup register by step. 1 which I did last time, I use sam-ba to program it,
$ sam-ba -p j-link -b sama5d27-som1-ek -a qspiflash -c writeboot:at91bootstrap.bin -c write:u-boot.bin:0x10000 -c write:zImage:0x200000
while all done, I press reset button, and that message shows up.
AT91Bootstrap 3.8.9-00026-gd7a52fb (四 2月 1 14:12:51 CST 2018)
SF: Got Manufacturer and Device ID: bf2643
SF: Copy 0xa0000 bytes from 0x10000 to 0x23f00000
SF: Done to load image
I attached the sceenshot for this.
I got the message because I cannot boot normaly from step.2, so I tried to program again by sam-ba. However every command will return the message back.ryback wrote:
3. Then I can't program any more, it always shows,
Opening J-Link with S/N '483029471'
Error: Unsupported device
That's insufficient context.
What did you do to get this message?
$sam-ba -p j-link -d sama5d2 -a bootconfig -c readcfg:bscr -c readcfg:bureg0 -c readcfg:bureg1 -c readcfg:bureg2 -c readcfg:bureg3 -c readcfg:fuse
Opening J-Link with S/N '483029471'
Error: Unsupported device
Post
Re: fail to program SAMA5D27-SOM1-ek1 qspi flash by sam-ba
I think this is either a license restriction or a bug, it appears that any non 0 BUREGx register causes the OB J-link to have issues.
- blue_z
- Location: USA
Post
The SAMA5D27-SOM1-Kit1 is wired to use JTAG I/O set 3.
Your write of BUREG0 (inadvertently) reconfigured the JTAG interface to use I/O set 1 (which is the default value), and effectively disconnected the J-Link from the SoM after you rebooted.
Regards
Re: fail to program SAMA5D27-SOM1-ek1 qspi flash by sam-ba
The problem appears to be an unintended reconfiguration of the JTAG interface (that takes effect after the next reboot).ryback wrote: ↑1. I change the backup register as below,
>sam-ba -p j-link -d sama5d2 -a bootconfig -c writecfg:bscr:valid,bureg0 -c writecfg:bureg0:QSPI0_DISABLED,QSPI1_IOSET2,SPI0_DISABLED,SPI1_DISABLED,NFC_DISABLED,SDMMC0,SDMMC1,EXT_MEM_BOOT
Opening J-Link with S/N '483029471'
...
Setting BUREG0 to 0x000403f7 (QSPI0_DISABLED,QSPI1_IOSET2,SPI0_DISABLED,SPI1_DISABLED,NFC_DISABLED,SDMMC0,SDMMC1,UART1_IOSET1,JTAG_IOSET1,EXT_MEM_BOOT)
Connection closed.
The SAMA5D27-SOM1-Kit1 is wired to use JTAG I/O set 3.
Your write of BUREG0 (inadvertently) reconfigured the JTAG interface to use I/O set 1 (which is the default value), and effectively disconnected the J-Link from the SoM after you rebooted.
Regards
Who is online
Users browsing this forum: No registered users and 1 guest