Page 1 of 1

SAMA5D2 Xplained Ultra rev.B: how to login?

Posted: Thu Nov 23, 2017 2:46 am
by Pilot8
Hello everyone,

We work on SAMA5D2 Xplained Ultra rev.B board. I followed the instructions in linux4sam/bin/view/Linux4SAM/Sama5d2Xpl ... he_console. Now we are able to boot the board and connect to the board by using minicom. But after booting, we cannot input any character thru the minicom console. Does anyone know what could be wrong? How to login? What it the username/password?

Thanks everyone!

Here is the booting log:
Flattened Device Tree blob at 21000000
Boting using the lob at 0x210 Loageviee to 3fb58000, end 3fb632c7 .. OK

Starting kernel ...

Linux on physlCPU 0x0
Linux version 4.9.52-linuxm_5.7 (nferre@tefe)cc vn .0 C) ) #1 Tue Oct 3 114:45 CES2017
CPU: ARMv7 rocessor [410fc01] revision1 (Av7), cr10c53c7d
CPU / naliasing data cache, VIPT aliasing instruction cache
OF: :Machine model: el SAMA5D2 Xplained
cma: Reserve 16 MiB at 0x3e800000
Memory polic: Data cache writebackPU: All(started in SVCmod
abl8 (order: 1, 8192 bytes) Built 1 zonelists in Zneordemobility grouping on. tal pages: 129920Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootf1
Dentre hash table entries: 65536 (oder: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 493028K/524288K availale (6rnede,197K rwdata, 976K rodata, 1024K ini, 195K bss, 14876K reserved, 16384K cma-rrved)
Virtual kernel mery layo
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xe0800000 - 0xff800000 ( 496 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc000000 0xc0a3f8 ( 196 kB)
NR_IRQS:16 nr_irqs:16 1
L2C-310 ID efetch enabd, offset 2 lines
L2C-310namic clock gating enabled, standbode enabled
L2C-0ache controller eled, 8 ways, 128 kB
L2C CACHE_ID 0x410000c9, AUX_CTRL 0x36020000
clocksx_cycles: 0x7fffff,le_ns: 11517062 nsched_clock: bitn 10000000ns, raps 21474836475000000ns
Console: colour dummce 80x30
Calibratindelay loop... 329.31lpj=16592)
pid_lt: 3276minimu301
Mount-cache hasha en 024 (order: 4096ytes)
Mouhah table enies: 1024 (der: 0, 4096 bytes)
CPU: Testing wrte buffer coherency: ok
Sttingup staticitap for 0x20100000 - 20100058
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 2 part 30 variant 5 rev 1
clocksource:fies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 12604467000
nctrl core initialized pinctrl subsystem072 bytes)
N Registered protocol fl
DMA: preallocated 256 KiB pool foatomicohelocons
cpuidle: using governor menu
AT91: PM: standby standby suspend: ulp1
xdm f001nels, mapped at 0xe0841000max_le_ 217874325ns
at_xdmac f0004000.dma-controller: 16 channels, mapped at 00
A: Detected SoCsama5d2
AT91: Detected SoC: sama5d27evision 1
SCSI subsystem initized
uc: registered newtere drivesbfs
usbctereew ierfce drier hub
cegistered new device driver usb
at91_i2c f8028000.i2c: could not find pctldev for node /ahb/apb/pincfc030/i2c0_defaultdeferring probe
at91_i2c 28000.i2c: could t find pctldev for nde /ahb/apb/pinc@380002c1_dfaul deferring probe
media: Linux media interface: v0.10
Linux video capture interface: v2.00
Advanced Linux Sourchitecture Driver Initial.
cksource:o clocksource tcb_clksrc
NET: Regitocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries:96 (order: 284 bytes)
TCP: Hash tables configured (established 4nd 4096)
UDP hash table entries: 256 (ordr: 0, 4096 bytes)
Ush table eries56 (er: 0, 4096 bytes)
NET: Registeredo family PC: Registereamed UNIX socket transpor module.
: Registered udp transport mansport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
gis (default)imestas=14 max_order=17 bucket_order=3
pinctrl-at91-pio4 fc038000.pinctrl: atmel pinctrl initial
f80200 at MM8020000 (irq = 35,e_baud = 5187500L_SERIAL
console [ttyS0] enab[drm] Initializ
brd: module loaded
8600.i2c: UsiO (16 00.
f8000000.spi: DMA TX cel not available, SPm25p80 spi32766.0: at25df321a (4096 Kbytes)atmel_spi f8000000.smel SPI Controlleersion 0x311 at 000q 29)
hy: Fixed MDBusrobed
iver irfacem_can f8054000.can: an device regist (irq=38, version=31)
fc05 m_ce gistered (irq=4rsioACB_mii_bus: probed
macb8008000.ethernet ethq 19, io mem 0x00500000 or KSZ8]us:y_addr=f8008000herne01,4)
atmel-eh500000.oundor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, Serialber=1
usb usb1: Product: EHCost Contler
usb u: nutr: Lux 4.52-lux4sam.7 ehc
usb usb1: SerialNu: 500000.ehci
ohhcd: USB 1.1 'Open' HoController (OHCI) Driohci-at
at91_ohci 400000.ohci: USB Host Controller
at91_ohci 400000.ohci: nebus regired, assigned bunumber
at9ci 400000, io mem 0usb usb2: New USB device found, idVendor=1d6b, idProd=0001
usb usb2: New Udevisngs: Mfr=3, Product=2, SerialNumb1
usb usb2: Product: USB Hostontrolleusb usb2: Manufacturer: Linux 452-linux4sam_5.7 ohci_hcd
usb usb2: SerialNumber: at1
hub 2-0:1: USB hub found
hub 2-0:1.0: 3 ports detected
usbcorregistered interface driver usb-storage
rtcc0: alarm rollover not handled
rtc rtc0:nvalid alarm value: 1900-1-1 0:0:at91_rtc 0480b0.rtc: rtc core: registered f80480b0.rtc as rtc0
at91_rtc f80480b0.rtc: AT91 Real Time Ck driver.
i2c /dev entridriver
AT91: Starting after wap
sama5d4_wdt f8048040.watg: initialized (timeout = 16 sec, nowayout = 0)
dhci:right(c) Pierremanost Controllnterface driver
sdhci-pltfm: SDHCI pltform and OF driver helper
sdhci-at91 a0000000.sdio-host: update clk mul to39 as gck rate is 4z
mmc0: SDHCI controller on a0000000.sdio-hot [] using ADMA
sdhci-at91 b0000000.sdio-host: update clk tas gck rate is 480000000 Hz
ledpu:regised tondice acton Cs-ost [] sing
atmel_aes02c000.aes: version: 0x500
atmel_sh8000: version510
atme_s0028000a: usg dma0chan2 fMA ansfers
atmel_sha AtHAHA256/SHA2384/SHA
atmdes fc044000.tdeersionatmel_es fc044000.tdes: using dma0chan3, dma0chan4 for DMA transfers
mmc0: new DDR MMC card iB
boot0000G partiM
0bomc0:l_tdes f44000.tlS/TDES
mmcblk0rpmb: mmc0:0001 MMC04G partition 3 128 KiB
atmassd048000.classd: Pes Drenialnonovlas eab
atmel-classd fc048000.clad: atmel-classd-hifi <-> fc040.classd mapping NET: Regised protocol family 10
sit: IPv6, IPv4 and MPLS over IPvriver
n:ntrearea nrev 20528 abi 9)
NET: Retered procol family 29
can: r894ger: have been suspendeat91_i2c f8028000.i2c: AT91 i2c bus driver (hw versin: 0x704).
at91_i2c fc028000.i2c: cat get DMA chann, continue without DMA support
at91_i2c fc028000.i2c: at24 2-0054: 56 byte 24c02 EEPROM, ble, 16 bytes/write
at91_i2c fc028000.i2c: AT91 i2n: 0x704).
rsion: 800d2_adc fc030000.adc: setting up trigger as externalsing
input: gpio_keys as /dform/gpiokeys/input/input0
at91_rtc f800b0 seng system clock to 2017-10-03 10:07:00 UTC (1507025220)
ALSA device list:
atmel_usart f8020000.serial: using dma0chan6 for rx DMA transfers
atmel_usart f8020000.serial: using dma0chan7 for tx DMA transfers
EXT4-fs (mmcblk0p1): recovery complete
EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:1.
devtmpfs: mounted
Freeing unused kernel memory: 1024K
INIT: version 2.88 booting

/S03systemd-udevd: line: No su directory
starting version 23ba_udc 300000.gadget: MMIO registers at 0xfc02ror -g_serial gadgeer v2.4dget:reaEXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
Sending discover..No lease, forking to background
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd
Starting rpcbind daemon...done.
starting statd: done
Starting atd: OK
Starting bluetooth
exportfs: can't open /etc/exports for reading
NFS daemon support not enabled in kernel
Starting syslogd/klogd: done
Starting crond: OK

Poky (Yocto Project Reference Distro) 2.2.2 sama5d2-xplained /dev/ttyS0

sama5d2-xplained login:

Re: SAMA5D2 Xplained Ultra rev.B: how to login?

Posted: Thu Nov 23, 2017 4:24 am
by blue_z
Pilot8 wrote:I followed the instructions in linux4sam/bin/view/Linux4SAM/Sama5d2Xpl ... he_console.
That's insufficient information to determine why the boot log is incomplete and has missing characters.
E.G. two connection methods for the console are mentioned, so which one did you use?
All I can deduce from what little you've provided is that your PC is running Linux (because the terminal emulator program is minicom).

Study (and apply) How To Ask Questions The Smart Way.

Pilot8 wrote:What it the username/password?
The username is "root" with no password.


Re: SAMA5D2 Xplained Ultra rev.B: how to login?

Posted: Fri Nov 24, 2017 10:02 pm
by Pilot8
Hi blue_z,

Thanks for your reply.

I used J14(EDBG_USB) connection. I checked and found I needed to "Close JP2 to disable de DEBUG port J1". After doing that, I got Linux booting by running "boot" command from U-Boot.

The new question is: how to get Linux boot working by directly running "bootcmd" from U-Boot?

I "setenv bootdelay 3" and "saveenv". However, each time, the booting process still run into U-Boot. And I also noticed, there are some weird "ATE1 E0" string and some other string in U-Boot. It's like this(not sure what sending these commands):
=> 1 E0 '`�f�1' -y 'help'
=> ATE1 E0
Unkncommand 'ATE1' - try 'help'
=> ATE1 E0
Unknown command 'ATE1' - try 'help'
=> ~x�~~x�~

Here is printenv:
=> printenv
bootargs=console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootfstype=ext4 rootwait atmel.pm_modes=standby,ulp1
bootcmd=ext4load mmc 0 0x21000000 boot/at91-sama5d2_xplained.dtb; ext4load mmc 0 0x22000000 boot/zImage; bootz 0x22000000 - 0x21000000


Re: SAMA5D2 Xplained Ultra rev.B: how to login?

Posted: Fri Nov 24, 2017 11:09 pm
by blue_z
Pilot8 wrote:I used J14(EDBG_USB) connection. I checked and found I needed to "Close JP2 to disable de DEBUG port J1". After doing that, I got Linux booting by running "boot" command from U-Boot.
That doesn't explain the dropped characters.

Pilot8 wrote:The new question is: how to get Linux boot working by directly running "bootcmd" from U-Boot?
(You seem to be asking the wrong question.)
Study the U-Boot manual which is online.
The `bootd` command is equivalent to typing `run bootcmd`, which is performed for autoboot.

Pilot8 wrote:And I also noticed, there are some weird "ATE1 E0" string and some other string in U-Boot. It's like this(not sure what sending these commands):
Those look like Hayes modem (aka AT) commands.
Check your minicom configuration; the modem Init and Reset strings should be empty (the default setting) for this connection.

If you're sending characters to the board's console (intentionally or not) during boot, that will cause U-Boot to abort the autoboot and switch to the command-line mode.
Is that what you mean by "the booting process still run into U-Boot"?
You should describe what actually happens (e.g. you see the U-Boot prompt), rather than compose your interpretation (which makes no sense).