Serial connection.

[warri]

What parameters to use for serial console.

I tried 115200 data 8 parity none and stop bits 1

and the output is not readable.. atleast not human readable.

Code: Select all

 00y bd fb fb fb fb fb fb fb fb fb fb 0b bf bf bf
 bf bf bf bf bf bf bf bfAAAA bfA bf e5 eb bf bf bf bf
 bf bf bf bf bf bf 07 bf 07 bf bf bf bfAA bfA bf a1
 bfAAA afA ad bfAAA e5 eb bf bf bf bf bf bf bf bf bf bf
 07 bf 07 bf bf bf a1 bfA? bf 07 bf 07 bf bf bf 07
 bf 07 a1 bfA bfG e5 eb bf bf bf bf bf bf bf bf bf


lots of stuff like that.

[fvdw]

Which program do you use to connect to the serial console and which wires did you connect? Should be only rx, tx and gnd. Furthermore you must us a ttl 3.3v rs 232 cable

[warri]

tried in linux with picocom and in windows using putty and some other which name cant remember.
putty output looks a bit different.

Code: Select all

y▒▒▒▒▒▒▒▒▒▒▒
            ▒▒▒▒▒▒▒▒▒▒▒AAAA▒A▒▒뿿▒▒▒▒▒▒▒▒▒▒▒▒▒AA▒A▒▒▒AAA▒A▒▒AAA▒뿿▒▒▒▒▒▒▒▒▒▒▒▒▒▒A?▒▒▒▒▒▒▒▒A▒G▒뿿▒▒▒▒▒▒▒▒▒AAA▒▒A▒▒AAA▒▒▒AA▒▒뿿▒▒▒▒▒▒▒▒AAAAAGAA▒AGAAAAAGAAA▒▒A▒▒▒A▒▒▒▒▒AAAA▒▒▒▒▒▒▒▒▒▒▒▒▒▒A▒▒▒▒▒▒▒▒▒AA▒▒▒▒AAA▒▒▒AAA▒▒A▒▒▒▒▒▒AAA▒▒A▒G▒▒▒A▒G▒▒▒A▒G▒AA▒▒▒▒A▒AAA▒A▒▒▒▒A▒▒▒▒A▒▒▒A▒▒▒GAAA▒▒▒▒▒AAAA▒▒GAAA▒▒GAAA▒▒GAA▒37▒▒▒▒▒[[▒;▒▒▒▒m▒▒▒▒뿫▒▒e}[Sugg▒{a}[w▒▒}YWacAcY▒gu▒y▒+:▒▒=;!#▒▒▒'!#1▒▒▒▒s}mg▒▒▒▒▒▒U▒{!!▒▒▒▒▒▒▒▒k=#▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒e=''▒5▒▒▒▒▒▒▒▒▒g=y-5▒▒▒▒▒▒▒▒▒▒e{▒37▒1▒;;!!▒▒▒▒▒▒▒U▒{!!▒9!75▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒w▒▒▒{YY▒▒▒▒▒▒▒▒{w}u▒▒▒▒▒Y!9▒▒▒▒s▒▒▒▒▒}▒▒▒ww[▒▒▒▒y_U▒▒▒▒▒e/


And yes connected only gnd, tx and rx. and crosslinked rx to tx and tx to rx.

serial cable is based on ch340 and says 3.3-5v

[fvdw]

The only things I can think of is
- you connected gnd to the wrong pin
- your ch340 cable is not able to communicate with ttl 3.3v serial port due to a jumper setting level to 5 v iso 3.3 v

[warri]

The only things I can think of is
- you connected gnd to the wrong pin
- your ch340 cable is not able to communicate with ttl 3.3v serial port due to a jumper setting level to 5 v iso 3.3 v

well i found a picture of the connector. and according to that they are the correct pins..

8 pins and (depending on the side you look them).

TX RX xx xx xx xx GND V3.3

actually tried other also, based on PL2303HXA chip.. which says 3,3-5v

[Jocko]

Hi

I assume you get it from this page : https://web.archive.org/web/20150730041425/http://lacie.nas-central.org/wiki/Serial_port_(Network_space_2)which details also the right cable you have to use

[warri]

Yes. Well got another cable of the sort and that does work. kwboot doesnt work though. Did you mess around with the uboot file included so that possibility of using kwboot is ruled out ?

[Jocko]

Hi

Nope !

We only release an uboot version for nwsp v2 classic with GPT support and nothing else...
According to your feedback, that means it is not supported natively by the lacie uboot

[fvdw]

Kwboot is supported on nwsp2 but you need to do in the correct way.
I can look in my archives how it should be done but it is of little or no use when you have access via serial interface. Note that if you change environment variables of uboot they are not persistent and will be overwritten by uboot at next boot. Using kwboot make only sense if you have a corrupt uboot or if you want to test a new uboot image before writing it to flash.

Kwboot is handled by the first stage bootloader and has in fact nothing to do with uboot. The bootloader either loads an image via kwboot (uart) and if thats not present/available it loads second stage uboot from flash memory.

A good how to can be find here. https://forum.doozan.com/read.php?3,7852,7852It also describe a way to check if the bootrom in your nas supports kwboot.