Re: [tracker2] T2-301 serial port problems
That was it! As it turns out, cu(1) has a 6+ year old bug that forces
hardware flow control regardless of whether the user has disabled this
cu(1) is a great little program for getting a quick console to many
devices but the version shipped with most Linuxes is not suitable for
the Tracker2. C-Kermit (with SET FLOW NONE) is working great, though.
On Tue, Sep 20, 2011 at 8:47 AM, Scott Miller <scott@...> wrote:
> Chris, sounds like your terminal program has CTS/RTS flow control
> enabled. You'll need to find that and disable it. I don't know cu(1),
> but you could try minicom.
> On 9/19/2011 10:45 PM, Christopher Snell wrote:
>> Hi All,
>> I have a new T2-301 that I finally got around to playing with tonight.
>> I powered it up using the T2-301 serial+power cable with the one
>> yellow DB-9. I attached my USB<->Serial console cable to the black
>> DB-9 and was able to get to the T2's console. Good. Next, I powered
>> the device off and attached the red/blue splitter cable to the black
>> DB-9 end of the T2's power/serial cable. I tried attaching my console
>> cable to both the blue and red ports but could not get a console to
>> come up.
>> I removed the splitter and re-attached the console cable to the
>> power/serial cable and started poking around in the T2's settings. I
>> noticed that AMODE was set to AUTO and BMODE was set to FLOW. I
>> changed BMODE to AUTO, hoping this would make the splitter work but
>> instead, it broke all console access completely! Now I can't get into
>> the console regardless of whether I'm using the splitter.
>> Any ideas?
>> FWIW, I'm using Ubuntu and cu(1) to talk to the serial port at 4800 baud.
>> Chris NW5W
> Yahoo! Groups Links