configuration changes. (I've seen it being used with two serial ports)
L.
Date: Thu, 18 Nov 2010 12:13:42 -0000
Subject: Re: [Wild-ducks] other peripherals for beagleboard - VGA
Hi Tom,
When are you expecting to have " muxcons " available?
Could you share some of the information around fshell to be used with Wild
Ducks and Beagleboard on the Wild Ducks wiki, please?
Any tricks, useful commands, etc
Best regards,
Arnaud
-----Original Message-----
Sent: 18 November 2010 11:49
Subject: Re: [Wild-ducks] other peripherals for beagleboard - VGA
I don't plan to get any new monitor just for the sake of playing with
the beagleboard ;)
Fshell will happily let you use a beagleboard headlessly, so long as
everything you want to do can be done over command line (connects via
the serial port)
In fact muxcons (not yet released, contact me directly if you're
interested) can mirror the display output over the serial port if you
really need.
http://developer.symbian.org/wiki/Fshell
http://developer.symbian.org/wiki/Fshell/Getting_Started#Getting_starte
d_on_Beagleboard_with_S.5E3_Textshell
Cheers,
Tom
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
_______________________________________________
Wild-ducks mailing list
http://developer.symbian.org/mailman/listinfo/wild-ducks
Symbian Foundation Limited is a Company Limited by Guarantee and not having
Share Capital
We're registered in England and Wales - Companies House knows us by the
number 6683783
Our address is 1 Boundary Row, Southwark, London SE1 8HP.
---------- Wiadomo¶æ przekazana dalej ----------
Date: Thu, 18 Nov 2010 13:15:56 +0100
Subject: Re: [Wild-ducks] other peripherals for beagleboard - VGA
Hi Arnaud,
When are you expecting to have " muxcons " available?
It's getting there, I might have something releasable by next week.
Could you share some of the information around fshell to be used with
Wild
Ducks and Beagleboard on the Wild Ducks wiki, please?
Good idea but I've rather got my hands full already. If one of the other
ducks wanted to step in I'd be happy to help, and there's already quite a
lot of info on the fshell wiki including beagle instructions.
Cheers,
Tom
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
---------- Wiadomo¶æ przekazana dalej ----------
Date: Thu, 18 Nov 2010 13:33:40 +0000
Subject: Re: [Wild-ducks] GCC_SURGE catchup
Yes I saw it. The "ii" => "ll" fix is a beauty.
- if (!PyArg_ParseTupleAndKeywords(args, kwds, "ll", kwlist, &base, &size ))
+ if (!PyArg_ParseTupleAndKeywords(args, kwds, "ii", kwlist, &base, &size ))
The characters in the string are the data types (l==long and i==int), I changed the types from long (which is 32bits wide on a 32 bit CPU and 64 bits wide on a 64 bit CPU) to int (which is always 32 bits wide).
I had to explicitly cast self.nvmemory_sharedmemory_host_address to ctypes.c_void_p when it is passed into a C function. Without this explicit cast Python treats the value as a 32 bit integer.
Regards,
George
*Sent:* 18 November 2010 11:32
*To:* Norton, George
*Subject:* Re: [Wild-ducks] GCC_SURGE catchup
Ah, I hadn't noticed your fix while my head's been in BB. That's great!
I'll go see what you did.
Syborg ROMs with persistent storage are broken for 64 bit builds.
I though I had fixed this in the latest QEMU GCC_SURGE.. Does it still not
work for you?
-George
*Sent:* 18 November 2010 10:53
*Subject:* Re: [Wild-ducks] GCC_SURGE catchup
A Linux/GCCE build on a 64 bit host with 64 bit build tools is also fine.
Nice, as Syborg ROMs with persistent storage are broken for 64 bit builds.
The Linux/GCCE build of Beagleboard boots fine and stands up for the usual
sort of noodling. So does the Windows/GCCE build. These are textshell ROMs.
Some assert failures logged on boot in both cases:-
+\0xa8SerialKeyboard::Create bound to interrupt
At address 80007600 :-
Assertion failed: Don't call from thread with kernel unlocked
At address 80007600 :-
Assertion failed: Don't call from thread with kernel unlocked
At address 80007600 :-
Assertion failed: Don't call from thread with kernel unlocked
At address 80007600 :-
Assertion failed: Don't call from thread with kernel unlocked
...
- but they don't seem to hurt.
FCL/sf/os/buildtools/ #f7dee603db09 (GCC_SURGE)
FCL/sf/os/kernelhwsrv/ #9b85206a602c (GCC_SURGE)
FCL/sf/adapt/beagleboard/ #c1bfa2b1009b (GCC_SURGE)
The Raptor rombuild doesn't work out-of-box. It will need another commit
to to either buildtoools or kernelhwsrv to fix that.
*(Q. Is anyone getting Raptor to build BB roms?)*
One minor difference between RVCT and GCCE roms: According to the BB
Quickstart Wiki (
http://developer.symbian.org/wiki/Kernel:BeagleBoard_Quick_Start#Loading_the_ROM_Image),
the rom fatload address is 0x81000000. For GCCE roms, it is 0x82000000. I
have updated the Wiki on this point though I haven't yet investigated the
cause..
The fact that you can now do BB dev with a fully open platform and tools
is worth publicising. I will make a BB wiki page along the lines of
http://developer.symbian.org/wiki/How_to_build_and_run_a_Symbian_QEMU_ROM_with_GNU/Linux_toolsand link it from the Wild Ducks landing page.
The GCC_SURGE branch of beagleboard was 3.5 months stale. I have merged it
up to the default tip, with necessary fixes for Linux portability and for
GCCE's lack of vfp math support. The ROM builds but I haven't tried to boot
it yet - next.
--
Mike Kinghan,
Test Lead, Symbian
+44(0)776 5222 793
--
Mike Kinghan,
Test Lead, Symbian
+44(0)776 5222 793
--
Mike Kinghan,
Test Lead, Symbian
+44(0)776 5222 793
Symbian Foundation Limited is a Company Limited by Guarantee and not having Share Capital
We're registered in England and Wales - Companies House knows us by the number 6683783
Our address is 1 Boundary Row, Southwark, London SE1 8HP.
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
--
Mike Kinghan,
Test Lead, Symbian
+44(0)776 5222 793
Symbian Foundation Limited is a Company Limited by Guarantee and not having Share Capital
We're registered in England and Wales - Companies House knows us by the number 6683783
Our address is 1 Boundary Row, Southwark, London SE1 8HP.
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
--
Mike Kinghan,
Test Lead, Symbian
+44(0)776 5222 793
Symbian Foundation Limited is a Company Limited by Guarantee and not having Share Capital
We're registered in England and Wales - Companies House knows us by the number 6683783
Our address is 1 Boundary Row, Southwark, London SE1 8HP.
---------- Wiadomo¶æ przekazana dalej ----------
Date: Thu, 18 Nov 2010 13:30:23 +0000 (GMT)
Subject: [Wild-ducks] AT Modem Project
All,
I've been trying to get the AT Modem Project going. All I'm currently
looking to do is have the Windows emuilator talk to the Telit modem I have -
its a Telit GE864-QUAD.
So far I've: -
Got the modem connected to the PC via USB. Its using COM21 (which is
VCP1). I've managed to use Hyperterminal to successfully send AT
commands.
Downloaded PDK 3.0.1 (I've tried using 3.0.0 with the same results)
Cloned and built the AT_Test_LTSY branch of the FCL
Run the configatmodem.bat script. I set the COM port to port 20 (1
less than Windows right?) and the Baud to 115200
Removed SIM Check from startup
Patched and built the Phone App (for 3.0.1)
I then ran epoc.exe from M:\epoc32\release\winscw\udeb
At this point the emulator starts up, but doesn't seem to pick up the
network (there is a T-Mobile sim in the modem, but the emulator just has
"Operator" displayed). Plus I can't make/recieve calls etc. Running portmon
shows that there are some communications between the emulator and the
modem. It seems there is a IOCTL_SERIAL_WAIT_ON_MASK and IRP_MJ_READ which
just hang, as when I close the emulator these just show as cancelled and a
IRP_MJ_CLEANUP and IRP_MJ_CLOSE are added.
Have you got any ideas what I might be doing wrong, and what I might need
to do to make it work?
Cheers.
_______________________________________________
Wild-ducks mailing list
http://developer.symbian.org/mailman/listinfo/wild-ducks