Is there an UART tha is usable instead of USB Serial for Serial Command Shell?

Are any of the UART pins available to use at Bootup, instead of the USB Serial -for Linux Serial Command Shell ??

To expand upon my question :
Is there any way of programming the Core Board - just via UART ?

Are p20 UartRx and p21 UartTx the UART that drives through the USB

  • displaying the Linux Bootup and the Shell Connection ?

Okay,
I booted up successfully through the UART p2 & p3 to UART-to-USB Converter to the PC !


[   38.350000] br-lan: port 2(wlan0) entered disabled state
BusyBox v1.22.1 (2015-06-12 16:41:57 HKT) built-in shell (ash)
Enter 'help' for a list of built-in commands.
              _____                        _
             |  __ \                      (_)
             | |  | |   ___    _ __ ___    _   _ __     ___
             | |  | |  / _ \  | '_  '_ \  | | | '_ \   / _ \
             | |__| | | (_) | | | | | | | | | | | | | | (_) |
             |_____/   \___/  |_| |_| |_| |_| |_| |_|  \___/
                          OpenWrt Wireless Freedom                              
root@domino:/# [   41.740000] warning: alljoyn-daemon' uses 32-bit capabilities

Minimum Board Procedure:

  • Simply solder the Domino CORE Chip to the DI-Board.
  • Solder across R6.
  • Connect 10k Resistor across p5 to p6.
  • Connect USB +3.3V and Gnd- to p7=3.3V and p6=Gnd.
    Use a Term to the USB ComPort at 115K baud.

Caution - this may put an overdrain on the PC USB Port.

Now I have it stuck rolling through Reboot over-and-over at about #45.xx - 47.xx
While PI just stops at #45.17
How do I get out of this ?


[   41.900000] warning: 

alljoyn-daemon’ uses 32-bit capabilities (legacy support in use)
[ 42.680000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[ 42.690000] jffs2_build_filesystem(): unlocking the mtd device… done.
[ 42.690000] jffs2_build_filesystem(): erasing all blocks after the end marker… [ 46.900000] br-lan: port 2(wlan0) entered forwarding state
[ 46.910000] br-lan: port 2(wlan0) entered forwarding state
[ 46.910000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 46.950000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready


  •    U-Boot 1.1.4  (Jun  6 2015)        *
    

AP121 (AR9331) U-Boot for DOMINO v1

DRAM: 64 MB DDR2 16-bit
FLASH: Winbond W25Q128 (16 MB)
CLOCKS: 400/400/200/33 MHz (CPU/RAM/AHB/SPI)

** Warning: bad env CRC, using default,
use ‘saveenv’ to save it in FLASH

LED on during eth initialization…


| __ \ / __ \ | / | |_ | | \ | | / __
| | | | | | | | | \ / | | | | | | | | | |
| | | | | | | | | |/| | | | | . ` | | | | |
| || | | || | | | | | | | | |\ | | || |
|
/ _/ |
| || |_____| || _| ____/

Hit any key to stop autobooting: 0

Device calibrated. Booting …
Booting image at: 0x9F050000

Image name: MIPS OpenWrt Linux-3.10.49
Created: 2015-06-17 7:07:46 UTC
Image type: MIPS Linux Kernel Image (lzma compressed)
Data size: 1114216 Bytes = 1.1 MB
Load address: 0x80060000
Entry point: 0x80060000

Uncompressing kernel image… OK!
Starting kernel…

[ 0.000000] Linux version 3.10.49 (alzhao@alzhao-ubuntu) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r45620) ) #41 Wed Jun 17 15:07:32 HKT 2015
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 00019374 (MIPS 24Kc)


[ 38.770000] device wlan0 entered promiscuous mode
[ 41.740000] warning: `alljoyn-daemon’ uses 32-bit capabilities (legacy support in use)
[ 42.820000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[ 42.820000] jffs2_build_filesystem(): unlocking the mtd device… done.
[ 42.830000] jffs2_build_filesystem(): erasing all blocks after the end marker… [ 47.190000] br-lan: port 2(wlan0) entered forwarding state
[ 47.190000] br-lan: port 2(wlan0) entered forwarding state
[ 47.200000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 47.230000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready


  •    U-Boot 1.1.4  (Jun  6 2015)        *
    

AP121 (AR9331) U-Boot for DOMINO v1


[ 42.100000] warning: `alljoyn-daemon’ uses 32-bit capabilities (legacy support in use)
[ 43.130000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[ 43.130000] jffs2_build_filesystem(): unlocking the mtd device… done.
[ 43.140000] jffs2_build_filesystem(): erasing all blocks after the end marker… [ 47.090000] br-lan: port 2(wlan0) entered forwarding state
[ 47.090000] br-lan: port 2(wlan0) entered forwarding state
[ 47.100000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 47.120000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready


  •    U-Boot 1.1.4  (Jun  6 2015)        *
    

AP121 (AR9331) U-Boot for DOMINO v1


[ 47.080000] br-lan: port 2(wlan0) entered forwarding state
[ 47.090000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 47.100000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready


  •    U-Boot 1.1.4  (Jun  6 2015)        *
    

AP121 (AR9331) U-Boot for DOMINO v1
`

I think that you are probably drawing too much current from your 3.3V supply (Are you using the 3.3V from your serial/USB converter?). This is causing a reboot once it hits a particular point where additional current is needed, and resets itself. If you solder on the 3.3V regulator included with the bare PCB you can use the 5V directly from the USB/serial converter instead of overloading its on-board converter. There are two places that accept 5V on the Di board: on the end of the board labeled UART, and at the opposite end marked USB (They are connected together so it doesn’t matter which you use). I haven’t had any stability issues powering the Di that way, and I’ve connected a USB flash drive to the USB GND, 5V, and D-/D+ pins successfully.
V

Yes, solved by using (2) Usb2Serial for 3.3V power.

Its also possible to disable thw Wifi:


In order to disable it, you need to
- edit file /etc/config/wireless and change line 

Code: [Select]

 option disabled 0

to 
Code: [Select]

 option disabled 1

- edit file /etc/rc.local and change line 

Code: [Select]

 wifi-live-or-reset

to 
Code: [Select]

 #wifi-live-or-reset