Core Board - continuous Rolling Reboot issue

Technical Support for Routers
1

I am stuck with the Core Board rolling through Reboot over-and-over at around #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
`

2

Now I finished a 2nd Board.
Testing them, now I have 2 CORE DI Boards running with this continuous rolling Reboot.

Am I missing something … Is there something needed besides short across R6 , and 10K across RTS and GND ???

Ok, I think I have a solution.
Apparently, (1) Usb to Serial Power (100mA) is enough to Boot.
But, when the Boot reaches the #32-47, the LAN and Wireless, it Reboots.

I linked a second UsbToSerial Converter Power (totaling 200mA for both),

  • it did not Reboot again.

So, 100mA can Boot and Run -without LAN and Wireless.
But, with Wireless and/or LAN then 200mA is needed.

3

You can test the continuous current after the module runs. 200mA should be more than enough.

4

will do.
(2) 100mA Usb2Ser seemes to be enough.