sama5d36 other configuration

Moderator: nferre

Renn
Posts: 4
Joined: Wed Nov 04, 2015 7:23 pm

sama5d36 other configuration

Wed Nov 04, 2015 8:03 pm

Hello!
The device with use sama5d36
There are problems:
1.
sam-ba do not connect USB or UART
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 on : windows
-I- Connection : \USBserial\COM3 (target(comType) = 0)
-I- Board : at91sama5d3x-ek
-I- Traces Level : 4
-I- target(handle) : 29383160
Read device Chip ID at 0xfffff240 --- get 0x00000000
Read device Chip ID at 0xffffee40 --- get 0x8a5c07c2
-I- Found processor : at91sama5d3x (Chip ID : 0x8a5c07c2)
sourcing device file C:/Atmel/sam-ba_2.12/sam-ba.exe/../tcl_lib/devices/at91sama5d3x.tcl
sourcing board description file C:/Atmel/sam-ba_2.12/sam-ba.exe/../tcl_lib/at91sama5d3x-ek/at91sama5d3x-ek.tcl
-I- Loading applet applet-lowlevelinit-sama5d3x.bin at address 0x308000
The unique way connection through jtag after attempt will incorporate through USB or UART
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 patch7 on : windows
-I- Connection : \USBserial\COM3 (target(comType) = 0)
-I- Board : at91sama5d3x-ek
-I- Traces Level : 4
-I- target(handle) : 55843640
Read device Chip ID at 0xfffff240 --- get 0x00000000
Read device Chip ID at 0xffffee40 --- get 0x8a5c07c2
-I- Found processor : at91sama5d3x (Chip ID : 0x8a5c07c2)
sourcing device file C:/Atmel/sam-ba2.12/sam-ba.exe/../tcl_lib/devices/at91sama5d3x.tcl
sourcing board description file C:/Atmel/sam-ba2.12/sam-ba.exe/../tcl_lib/at91sama5d3x-ek/at91sama5d3x-ek.tcl
-I- Loading applet applet-lowlevelinit-sama5d3x.bin at address 0x308000

Close process sam-ba.exe

-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 patch7 on : windows
-I- Connection : \jlink\ARM0 (target(comType) = 2)
-I- Board : at91sama5d3x-ek
-I- Traces Level : 4
-I- target(handle) : 28619344
Read device Chip ID at 0xfffff240 --- get 0x00000000
Read device Chip ID at 0xffffee40 --- get 0x8a5c07c2
-I- Found processor : at91sama5d3x (Chip ID : 0x8a5c07c2)
sourcing device file C:/Atmel/sam-ba2.12/sam-ba.exe/../tcl_lib/devices/at91sama5d3x.tcl
sourcing board description file C:/Atmel/sam-ba2.12/sam-ba.exe/../tcl_lib/at91sama5d3x-ek/at91sama5d3x-ek.tcl
-I- Loading applet applet-lowlevelinit-sama5d3x.bin at address 0x308000
-I- Memory Size : 0x2 bytes
-I- Buffer address : 0x4
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- Low level initialized
-I- External RAM Settings : extRamVdd=0, extRamType=1, extRamDataBusWidth=16, extDDRamModel=1
-I- Loading applet applet-extram-sama5d3x.bin at address 0x308000
-I- Memory Size : 0x8000000 bytes
-I- Buffer address : 0x309074
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- External RAM initialized


-I- End of Initialisation

-I----------------------------------------------
-I- Don't close this window !!!
-I----------------------------------------------
I used sam-ba 2.12, 2.12 patch 6, 2.12 patch 7, 2.14, 2.15 (OS Linux, Windows XP, Windows 7 x32, Windows 7 x64).
The result has appeared identical. How it is possible to correct it?

2.
Configuration board:
ATSAMA5D36A-CN
MT47H128M16RT-3
MT29F2G08ABAEAH4-IT (In it a problem) "Can't detect known device - Can't detect known device"
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 on : windows
current connection is \jlink\ARM0, \\jlink\\ARM0 to be matched
-I- Retrieved arguments from command line :
-I- argv 0 : \jlink\ARM0
-I- argv 1 : at91sama5d3x-ek
-I- argv 2 : demo_linux_nandflash.tcl
1
\jlink\ARM0
-I- Connection : \jlink\ARM0 (target(comType) = 2)
-I- Board : at91sama5d3x-ek
-I- Traces Level : 4
-I- target(handle) : 54984112
Read device Chip ID at 0xfffff240 --- get 0x00000000
Read device Chip ID at 0xffffee40 --- get 0x8a5c07c2
-I- Found processor : at91sama5d3x (Chip ID : 0x8a5c07c2)
sourcing device file C:/Atmel/sam-ba_2.12/sam-ba.exe/../tcl_lib/devices/at91sama5d3x.tcl
sourcing board description file C:/Atmel/sam-ba_2.12/sam-ba.exe/../tcl_lib/at91sama5d3x-ek/at91sama5d3x-ek.tcl
-I- Loading applet applet-lowlevelinit-sama5d3x.bin at address 0x308000
-I- Memory Size : 0x2 bytes
-I- Buffer address : 0x4
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- Low level initialized
-I- External RAM Settings : extRamVdd=0, extRamType=1, extRamDataBusWidth=16, extDDRamModel=1
-I- Loading applet applet-extram-sama5d3x.bin at address 0x308000
-I- Memory Size : 0x8000000 bytes
-I- Buffer address : 0x308B0C
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- External RAM initialized
-I- Command line mode : Execute script file : demo_linux_nandflash.tcl
-I- === Board Family is sama5d3xek ===
-I- === Chip variant is sama5d36 ===
-I- === eccType is 0xc0902405 ===
-I- === Initialize the NAND access ===
-I- NANDFLASH::Init (trace level : 4)
-I- Loading applet applet-nandflash-sama5d3x.bin at address 0x20000000
-E- Script File demo_linux_nandflash.tcl returned error : Can't detect known device - Can't detect known device
while executing
"error "Can't detect known device""
(procedure "GENERIC::Init" line 45)
invoked from within
"GENERIC::Init $NANDFLASH::appletAddr $NANDFLASH::appletMailboxAddr $NANDFLASH::appletFileName [list $target(comType) $target(traceLevel)]"
(procedure "NANDFLASH::Init" line 11)
invoked from within
"NANDFLASH::Init"
(file "demo_script_linux_nandflash.tcl" line 306)
invoked from within
"source demo_script_linux_nandflash.tcl"
(file "demo_linux_nandflash.tcl" line 20)
invoked from within
"source $scriptFile"
Differences NAND Flash TSOP and BGA in two bytes
Image

I in SignalTap II see that he reads these parametres.
Image
Correction of an source code applet files is necessary. I cannot find that it is necessary to correct.
How it is possible to correct it?
Renn
Posts: 4
Joined: Wed Nov 04, 2015 7:23 pm

Re: sama5d36 other configuration

Fri Nov 13, 2015 1:25 pm

There are live people? :)
Help to solve the remained problem please.
The connection problem sam-ba through USB or UART is not solved.
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.15 on : windows
-I- Connection : \USBserial\COM3 (target(comType) = 0)
-I- Board : at91sama5d3x-ek
-I- Traces Level : 4
-I- target(handle) : 27648144
-I- sourcing board description file C:/Atmel/sam-ba_2.15/sam-ba.exe/../tcl_lib/at91sama5d3x-ek/at91sama5d3x-ek.tcl
Read device Chip ID at 0xFFFFEE40 --- get 0x8a5c07c2
-I- Found chip : at91sama5d3x (Chip ID : 0x8a5c07c2)
-I- Loading applet applet-lowlevelinit-sama5d3x.bin at address 0x308000
P.S. The problem with NAND is solved. The problem was with DDR.
blue_z
Location: USA
Posts: 1979
Joined: Thu Apr 19, 2007 10:15 pm

Re: sama5d36 other configuration

Fri Nov 13, 2015 11:50 pm

Renn wrote:The connection problem sam-ba through USB or UART is not solved.
SAM-BA cannot use the DBGU (much less a UART) port to connect to a SAMA5D36.
Apparently this is due to the XMODEM bug in the ROM program as mentioned in the datasheet Errata (according to correspondence with Atmel Tech Support).

Are you using a custom board?
Which USB port are you trying to use?

Regards
Renn
Posts: 4
Joined: Wed Nov 04, 2015 7:23 pm

Re: sama5d36 other configuration

Sat Nov 14, 2015 12:12 pm

blue_z wrote:
Are you using a custom board?
Which USB port are you trying to use?

Regards
Yes custom board.
I use USB port А
It is defined as "AT91 USB to Serial Converter"
joshw
Posts: 14
Joined: Sat Jan 17, 2015 4:29 am

Re: sama5d36 other configuration

Sat Nov 14, 2015 3:46 pm

I can confirm that SAM-BA does work on ATSAMA5D36 despite the erratum that blue_z speaks of. You just can't use the xmodem feature.

I'm not quite sure I understand the most recent problem Renn describes. It halts when it reaches the "loading applet at <address>" phase? Consistently?
Josh @ CIHOLAS Inc
Renn
Posts: 4
Joined: Wed Nov 04, 2015 7:23 pm

Re: sama5d36 other configuration

Mon Nov 16, 2015 7:19 am

joshw wrote:It halts when it reaches the "loading applet at <address>" phase? Consistently?
Yes. When to connect via USB A, loading applet is infinite
blue_z
Location: USA
Posts: 1979
Joined: Thu Apr 19, 2007 10:15 pm

Re: sama5d36 other configuration

Mon Nov 16, 2015 9:54 pm

Renn wrote:I use USB port А
The SAM-BA Monitor (which resides in the SAM's ROM) does not use a Host port; it only uses a USB Device port.
Study the SAM-BA Monitor section in the datasheet.
Renn wrote:It is defined as "AT91 USB to Serial Converter"
If you mean you're using a USB-to-RS232 adapter on the SAMA5's Host USB port, then that cannot work unless U-Boot or Linux is running with the proper device driver.
The ROM code does not have any USB adapter drivers.

Regards
blue_z
Location: USA
Posts: 1979
Joined: Thu Apr 19, 2007 10:15 pm

Re: sama5d36 other configuration

Mon Nov 16, 2015 10:25 pm

joshw wrote:I can confirm that SAM-BA does work on ATSAMA5D36 despite the erratum that blue_z speaks of.
Your statement is ambiguous, and therefore is not as informative as you probably think it is.
Presumably you are making the SAM-BA connection using the USB Device port, a salient detail that you omit.
I was specifically referring to the DBGU port.
joshw wrote:You just can't use the xmodem feature.
That's rather difficult in SAM-BA.
In hindsight I should not have mentioned this detail.
The relationship between the SAMA5D3x's DBGU bug with the XMODEM bug is unclear, and the XMODEM bug does not seem to an issue when using the USB Device port.
All I was trying to do was cite a source (i.e. Atmel TS), and should have omitted their confusing response.

Regards
joshw
Posts: 14
Joined: Sat Jan 17, 2015 4:29 am

Re: sama5d36 other configuration

Tue Nov 17, 2015 2:40 am

Yes, I do refer to connecting SAM-BA to USB.
Josh @ CIHOLAS Inc

Return to “SAMA5-based”

Who is online

Users browsing this forum: No registered users and 3 guests