**** BEGIN LOGGING AT Fri Jan 23 02:59:57 2009 Jan 23 05:19:26 rwhitby: im working on a wrt400 now and i cant get any data from the serial port, should RX be 3,3v? I also measured NC to 3,3v Jan 23 05:19:46 krim: hi Jan 23 05:19:51 hi :) Jan 23 05:20:42 let's orientate ourselves first Jan 23 05:20:51 You're looking at JJ2, right? Jan 23 05:21:09 yep Jan 23 05:21:11 5 pin connector Jan 23 05:21:15 sure Jan 23 05:21:24 let's call pin 1 the pin closest to the ethernet ports Jan 23 05:21:30 yes Jan 23 05:21:33 and pin 5 is closest to the front panel leds Jan 23 05:21:51 you should see 3.3V between pin 1 (+ve) and pin 5 (gnd) - confirmed? Jan 23 05:22:23 pin 1,2,3 = 3,3v pin 4,5 = 0v Jan 23 05:22:43 are you sure about pin 2? I'd recorded that as NC Jan 23 05:22:51 im sure Jan 23 05:23:11 can check again hold on Jan 23 05:24:07 ok, given those voltages, I would first connect the recieve line from your usb serial converter (check that it is at 0V to make sure it's the RX line) to pin 3 and GND to pin 5. Jan 23 05:24:24 leaving the other transmit line from your usb serial converter unconnected for the moment Jan 23 05:24:36 (just in case we've got TX and RX on the board swapped) Jan 23 05:25:45 let me try connect again got something wrong here Jan 23 05:28:07 be careful - I expect I blew my serial port by swapping RX and TX, and the wiki page at http://www.nslu2-linux.org/wiki/WRP400/SerialPort could well be wrong Jan 23 05:28:26 think i blew it too Jan 23 05:30:24 so do you think that wiki page is incorrect? Jan 23 05:30:45 i think its upside down Jan 23 05:31:43 ive got another serialport lying around here somewhere Jan 23 05:31:59 oh, hang on - it does say bottom to top Jan 23 05:33:06 so pin 1 would be GND (OV), 2 would be TX (3.3V), 3 would be RX (input), 4 would be NC, 5 would be VCC (3.3v) in that configuration. Jan 23 05:33:30 the key is not to drive any voltages onto the board until you've verified RX vs TX Jan 23 05:34:32 closest to the ethernet ports pin 1 = 0v, 2 = 0v, 3=3,3v, 4=3,3v and 5=3,3v Jan 23 05:36:03 ok, take your serial port GND and connect to pin 1, and take your serial port RX (should be measured at 0V) and connect to pin 3. Jan 23 05:36:13 then power cycle and look for activity on the serial port. Jan 23 05:36:32 don't connect your serial port TX (the one that drives 3.3v) Jan 23 05:38:14 pin 3 also drives 3,3v should i connect rx to it anyway ? Jan 23 05:38:58 if pin3 is the TX pin from the board, then it should drive 3.3V when idle, and toggle on activity Jan 23 05:39:16 so you want to connect it to the RX signal of your serial converter Jan 23 05:39:40 pin3 (output) -> RX signal (input) Jan 23 05:39:57 just found it, im soldering it on now Jan 23 05:47:49 krim: any luck? Jan 23 05:53:30 no activity Jan 23 05:54:10 baud 115,2K right? Jan 23 05:55:12 yep Jan 23 05:55:14 8N1 Jan 23 05:55:29 yup Jan 23 05:55:57 is there a possibility that you've applied 3.3V to that pin3 ? Jan 23 05:56:38 pin 3 is 3,3v but rx is on that gnd on pin 1 Jan 23 05:56:42 and you're checking for activity immediately after a power-on, since the console is dead as soon as linux starts to boot Jan 23 05:56:58 yep Jan 23 05:57:41 are you able to test the operation of your serial converter on another known good device? Jan 23 05:58:11 ivet got some nslu2 lying around but no more pin headers Jan 23 05:58:21 nslu2s that is Jan 23 05:59:32 at this point, I would try the rx serial line (again, making sure that it's the input line, and is not driving a voltage) and connect it to pin 2 and pin 4 to see if there is any activity on them Jan 23 05:59:45 since the rx serial line is an input, it cannot damage anything on the wrp400 Jan 23 06:00:08 pin 2 first, and separately pin 4 Jan 23 06:01:09 you'll only see activity in the first few seconds after poweron - there's a short pause, then you see some u-boot stuff, then u-boot hands over to the kernel and you see nothing after that unless you've unlocked the console Jan 23 06:02:25 so ill try only gnd on pin1 and rx on pin2 first then pin4 ? Jan 23 06:03:13 yep Jan 23 06:10:49 got some crap on pin4 Jan 23 06:11:11 VEINn: and some cryptic stuff Jan 23 06:11:25 thats ubooy i guess Jan 23 06:11:36 uboot.. Jan 23 06:14:50 krim: you should get some ASCII art on boot Jan 23 06:15:47 as per http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRP400 Jan 23 06:16:08 its activity but not what i expected i expected that cybertan logo yes Jan 23 06:17:35 3 sec after bootup this comes up: y.......7.7./ú. ........... Jan 23 06:18:12 hold on i think ive got the latest fw on it Jan 23 06:18:52 latest firmware gave the same boot screen Jan 23 06:19:02 that looks like wrong baud rate or bad ground Jan 23 06:19:50 actually, try some other baud rates, cause 115200 isn't written on the wiki page Jan 23 06:20:01 so my memory could be wrong Jan 23 06:20:50 or could pin2 be gnd Jan 23 06:21:26 no, I'm pretty sure the end pins were GND and VCC Jan 23 06:21:41 try 57600, 38400, 19200, 9600 Jan 23 06:21:55 03bzhou * r9461 10optware/trunk/make/mpd.mk: mpd: added libshout to DEPENDS Jan 23 06:22:00 sure Jan 23 06:59:27 cant find the problem but its positive that rx is on pin 4. got some marvell stuff up, and that its checking boot image. Jan 23 06:59:43 its not the baud rate aand im pretty sure it has gnd right **** BEGIN LOGGING AT Fri Jan 23 08:55:23 2009 Jan 23 23:07:16 03bzhou * r9462 10optware/trunk/make/py-beaker.mk: py-beaker: 1.1.3 -> 1.2 Jan 23 23:15:36 03bzhou * r9463 10optware/trunk/make/libgcrypt.mk: libgcrypt: 1.4.3 -> 1.4.4 Jan 24 02:23:35 03bzhou * r9464 10optware/trunk/make/cherokee.mk: cherokee: 0.11.6 -> 0.98.0 **** ENDING LOGGING AT Sat Jan 24 02:59:57 2009