CIsco RV345 Console Connection

[pfrazao99]

Just purchased a RV345 and would like to establish a console connection and login via putty, iterm, etc.

When connected to console, it seems to freeze the console on the following line at the bottom:

barebox 2011.06.0-dirty (May 26 2017 - 15:09:22)

1.0.00.06
booting kernel of type uimage from /dev/nand0.kernel2.bb
Image verified and authenticated
Verifying Checksum ... OK
Image Name: Linux-3.2.54
Created: 2017-05-26 9:44:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2929496 Bytes = 2.8 MB
Load Address: 03008000
Entry Point: 03008000
OK

Starting kernel ...

commandline: loglevel=4, init=/etc/preinit, panic=10 mac_addr=EC:BD:1D:44:78:B0,EC:BD:1D:44:78:AF,EC:BD:1D:44:78:B1 ip=none root=ubi0:rootfs ubi.mtd=7 rootfstype=ubifs rw noinitrd mtdparts=comcertonand:512k(barebox),512k(bareboxfact)ro,128k(env),8M(kernel1),92M(rootfs1),128k(reserved_dtb1),8M(kernel2),92M(rootfs2),128k(reserved_dtb2),2M(configcert),12M(avcsign),32M(webrootdb),2M(license);spi1.0:128k(uloader)ro,512k(barebox),128k(env),128k(boardinfo)ro,64k(md5sum1),64k(md5sum2),64k(boot_check) usb3_internal_clk=yes pcie0_gen1_only=yes pcie1_gen1_only=no pcie_external_clk=yes bareboxver=barebox 2011.06.0-dirty (May 26 2017 - 15:09:22) bareboxver_rv340=1.0.00.06 boot_fail_flag=0
arch_number: 1094
Uncompressing Linux... done, booting the kernel.

==============

Router boots fine as I can login to web interface and do all my config, changes, etc. But console connection never fully comes up. I have tried both putty on Windows and the Serial app on MacOS and I get the same result from either desktop.

Assistance appreciated.

[sgizdov]

Granted this is a 9 month old post and things may have changed... but my experience with the RV345 leads me to conclude that:

1. Serial Port connection spec for access to the console seems to change depending on the boot stage at which the router is. I.e. During initial boot sequence, the only way I could see the boot logging was with 115200{Speed}/8{Data}/1{Stop bits}/None{Parity}/None{Flow control}. That is for the Out-of-the box firmware 1.0.00.06, which came with the router. Once you see the "Uncompressing Linux... done, booting the kernel." message, change the current connection speed from 115200 to 9600 and you will continue to see messages for various diagnostic messages (such as "[   19.690367] pe_load_ddr_section: load address(3fb0000) and elf file address(e8a7b000) rcvd", etc.) and a login prompt. I tried logging in with the default userid and password as documented, but those did not work for the console login. I thought that maybe the default login info, being forced to change the password using the GUI was somehow preventing the console login, but even after changing the password through the Web GUI, I was still not able to login on the console.

2. Upgrading the firmware to the latest ("RV34X-v1.0.01.17-2017-05-26-15-14-45-PM" is the one I used) seems to either disable access to the console altogether (during boot-up and afterwards) with any of the serial line settings I tried. So far no luck. So even to get to the console is firmware level dependent? The release notes on the 1.0.01.17 firmware do not mention anything about the console port. Maybe someone from Cisco can clarify/weigh in on this behavior for the RV345.

I tried, in addition to using Putty, TeraTerm as well. Granted, TeraTerm does automatic speed negotiations on the serial line (not sure if Putty can do that or not) but the results produced were the same with the baseline factory firmware.

My questions are as follows:

1. Is the console port going to be usable with the latest firmware (and in the future) and if so,

2. What serial line connection spec should be used?

3. What login info can be used to login via the terminal console?

Thx!