Re: irda on the ipaq shell WORKING

Hi,

i tested right now... WORKS!!!
i had to use Michaels zImage_jan29a, my compiled image somehow does not
work, after the thermometer goes red, the screen just turns off, and i
have to reset... I will try a clean compile again with Michaels
h2200_config_jan29a

Regards, Patty

Pattrick Hüper wrote:

> Great!
>
> i did some testing with Andrews changes but did not get it to work,
> will try Dannys setting tomorrow, if i find the time, i am looking
> forward to it!!
>
> Regards, Patty
>
> Danny Norging wrote:
>
>> at 9600 bps :)
>>
>> Hi Pattrick and all others,
>>
>> after some testing last night, i am now able to get a shell via irda.
>> The basic idea is, *not* to use the "console=..." kernel boot paramter,
>> but instead hardcode the "console via irda" into /dev. So here are the
>> instructions:
>>
>> 1) build initrd with Andrews initrd-kit (was available at
>> http://zap.sh.nu:8000/files/initrd-kit.tar.bz2 but right now i am
>> getting a "connection refused") as root with:
>>
>> barney /home/ipaq/dev/tmp # tar xjf ../initrd-kit.tar.bz2
>> barney /home/ipaq/dev/tmp # echo '#!/bin/sh' > .initrd/linuxrc
>> barney /home/ipaq/dev/tmp # echo "/bin/sh" >> .initrd/linuxrc
>> barney /home/ipaq/dev/tmp # rm .initrd/dev/console
>> barney /home/ipaq/dev/tmp # mknod .initrd/dev/console c 4 66
>> barney /home/ipaq/dev/tmp # ./mkfs
>>
>> 2) remove the "console=..." part from startup.txt
>>
>> barney /home/ipaq/dev/tmp # cat startup.txt
>> set KERNEL zImage
>> set MTYPE 341
>> set INITRD initrd
>> set CMDLINE "root=/dev/ram0 rw init=/linuxrc cachepolicy=writethrough"
>> bootlinux
>>
>> 3) start minicom on pc with the following settings:
>>
>> barney /home/ipaq/dev/tmp # cat /etc/minicom/minirc.irda #
>> Machine-generated file - use "minicom -s" to change parameters.
>> pu baudrate 9600
>> pu bits 8
>> pu parity N
>> pu stopbits 1
>> pu rtscts No
>> 4) put ipaq in place and start haret, so i get in minicom
>>
>> BusyBox v0.60.5 (2004.01.12-19:49+0000) Built-in shell (ash)
>> Enter 'help' for a list of built-in commands.
>> sh: can't access tty; job control turned off
>> # dmesg
>> Linux version 2.6.1-rmk0-hh0 (ipaq_at_barney) (gcc version 3.3.2) #1 Wed
>> Feb 18 14:31:04 CET 2004
>> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE)
>> ...
>>
>> the kernel was compiled with Michael's h2200_config__jan29a
>>
>> Thats it for now, hope it works for you too :)
>>
>>
>> Keep up the *great* work and happy hacking
>>
>> Danny
>>
>>
>> On Mon, 2004-02-16 at 14:05, Pattrick Hueper wrote:
>>
>>
>>> Hi all,
>>>
>>> i just recently joined the h2200-port list, i have an h2210 and
>>> would like to help porting... i have some experience in programming
>>> for an ARM based CPU under pSOS... other than that mostly Windows
>>> application programming. I started looking at the handhelds. org
>>> website and wanted to try the support thus far.
>>>
>>> Since my laptop does not have a serial port, i would like to get
>>> started seeing the boot via my IR port, i followed the setup
>>> instructions i found in the wiki and also in the h2200-port list...
>>>
>>> So far i have gotten the following to work:
>>>
>>> I have downloaded the toolchain, kernel, starterkit, built the
>>> kernel using Michael's h2200_config_jan29a, and installed haret and
>>> booted the kernel on my h2210, it doesnt always boot (thermometer
>>> doesnt turn red) but after hard reset it does most of the times,
>>> however, i dont see anything on the IR console...
>>>
>>> I followed the instructions i found:
>>> - made sure CONFIG_SERIAL_PXA_SIR is set
>>> - changed startup.txt to "console=ttyS2,115200n8"
>>> - on my laptop unloaded all ir* drivers
>>>
>>> if i do cat /dev/ttyS1 on my laptop and try to send a contact from
>>> the PDA via infrared, i see characters coming out of ttyS1, same
>>> with minicom, i also tried Andrews suggestion with my digital video
>>> camera, i can see the diode blinking when sending the contact, but
>>> when booting the kernel it stays dark... so i suppose its not
>>> sending anything...
>>>
>>> I saw a warning when building the kernel:
>>>
>>> in file drivers/serial/pxa.c, line 64
>>>
>>> #warning "PLATFORM_SIR_ON/OFF not defined, SIR must be enabled in
>>> platform initialization code!"
>>>
>>> but investigating that, i only found PLATFORM_SIR_ON/OFF defined in
>>> asm/arch/aximx5-gpio.h, and there only in an #if 0...#endif, so its
>>> never defined...
>>>
>>> (btw, there seems to be an error in line 61, same file which says:
>>>
>>> #if !defined PLATFORM_SIR_OFF || !defined PLATFORM_SIR_OFF
>>>
>>> the second PLATFORM_... should be PLATFORM_SIR_ON, i guess...)
>>>
>>> Any suggestions what else i might try? I saw that in the config file
>>> CONFIG_IRDA is set, as well as CONFIG_IRTTY_SIR and
>>> CONFIG_IRPORT_SIR, is it possible, that these somehow disturb the
>>> raw access to the IR serial port? I might try unsetting them when i
>>> have time...
>>>
>>> Anyway, i really hope to be of some help to the project, even with
>>> my limited experience and time...
>>>
>>> Greetings,
>>>
>>> Patty
>>>
>>> Andrew Zabolotny wrote:
>>>
>>>
>>>
>>>> On Tue, 3 Feb 2004 13:54:06 +1100
>>>> Marcus Brown <marcusbrutus_at_internode.on.net> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> I'd like to be able to have something similar to irdadump as a
>>>>> sanity check. My old method of testing serial mice didn't work
>>>>> (ie. cat /dev/ttyS1) with a "cat: /dev/ttyS1: Input/output error".
>>>>>
>>>>>
>>>>
>>>> This means either a) somebody already uses ttyS1 (try as root:
>>>> fuser -v /dev/ttyS1), or your computer simply has no ttyS1 (AKA COM2).
>>>> What kind of IrDA dongle are you using? A real serial dongle? Or some
>>>> USB gadget? If it is in a laptop perhaps it uses some other kind of
>>>> serial connection... try all serial ports, look in dmesg file which
>>>> serial ports there are, or in /dev/tts/*.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Any easy way of passively watching the comm in tandem with minicom?
>>>>> Do I need to initiate anything in minicom?
>>>>>
>>>>>
>>>>
>>>> If you have a hand camera, you can try to look through the visor at
>>>> the
>>>> IR transmitter. With my Sony Handicam I have easily debugged such
>>>> problems in the past - only the data sequence has to be relatively
>>>> long,
>>>> e.g. send some file with minicom and you should see the IR diode
>>>> bright.
>>>> Same from PDA side - run linux to start booting and look through the
>>>> visor at it's IR diode - it should flash.
>>>>
>>>> --
>>>> Greetings,
>>>> Andrew
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> H2200-port mailing list
>>> H2200-port_at_handhelds.org
>>> https://handhelds.org/mailman/listinfo/h2200-port
>>>
>>>
>>
>>
>> _______________________________________________
>> H2200-port mailing list
>> H2200-port_at_handhelds.org
>> https://handhelds.org/mailman/listinfo/h2200-port
>>
>>
>>
>>
> _______________________________________________
> H2200-port mailing list
> H2200-port_at_handhelds.org
> https://handhelds.org/mailman/listinfo/h2200-port
>
>
Received on Thu Feb 19 2004 - 08:09:59 EST