Good idea,
I've taken the tshell from the 3.0.0 PDK and attempted to run that.
I did the usual: -
mmc init
fatload mmc 0 0x81000000 beagle_tshell_ARMV5_udeb.img
go 0x81000000
The output I get is: -
## Starting application at 0x81000000 ...
ArmCpuVersionId CORTEX_A8 Rev:2
CPU at 600 MHz
[LCD] H_SYNC too big
+TSerialKeyboardl::Create:PRM client ID=0
+TSerialKeyboard::Create bound to interrupt
Nothing appears on the screen, however, when I type characters on the keyboard I do get output on the telnet, ie: -
Key received: 113 164
AddKey 0 0 0 164
Any ideas?
Thanks.
--- On Tue, 30/11/10, Arunabh Ankur <arunabha-***@public.gmane.org> wrote:
From: Arunabh Ankur <arunabha-***@public.gmane.org>
Subject: Re: [Wild-ducks] Beagleboard-xM
To: "Scamp Scamp" <scamps-ur4TIblo6goN+***@public.gmane.org>
Cc: "George Norton" <uk.george.norton-gM/Ye1E23mwN+***@public.gmane.org>, wild-ducks-***@public.gmane.orgbian.org
Date: Tuesday, 30 November, 2010, 14:57
May I advice you to first try one of the textshell images and verify if that works - the only reason I say that is the number of issues you can run into with a textshell is relatively low (as compared to full UI) and it's easier to debug.
Also , if it works , we can be sure that the Beagle baseport and the kerenel/mem configuration are all working fine on the XM.
The crash what you see is because you probably don't have Telephony Feature enabled. The latest ROM builds (from PDK 3.0.3 onwards ) has fixed that . But anyways it's not fatal and shouldn't stop the boot.
cheers !!Arunabh
Arunabh AnkurTechnology ManagementMobile : +44 7771376840Skype : arunabha.symbian
On 30 November 2010 13:14, Scamp Scamp <scamps-ur4TIblo6goN+***@public.gmane.org> wrote:
Thanks for your help.
I've partitioned my SD card with a boot partition (150MB) and a rootfs partition with the remaining space (aprx 4GB). I have then put an MLO and u-boot.bin in the boot partition, along with the beagle.rom.img and drive_c.img pre-built images (all in the boot partition).
I then run the commands: -
mmc init
fatload mmc 0 0x81000000 drive_c.img
fatload mmc 0 0x82000000 beagle.rom.img
go 0x82000000
I then gets lots of output to the telnet terminal, however it hangs with this as its final output.
RFile::Open, file= z:\resource\apps\bubblemanager.mif, errorcode=0
RFile::Open, file= z:\resource\numbergrouping.rsc, errorcode=0
RFile::Open, file= z:\resource\apps\phoneui.rsc, errorcode=0
Exc 1 Cpsr=60000030 FAR=00000000 FSR=00000005
R0=00000000 R1=00000000 R2=00000002 R3=0062dbb0
R4=0060a2e8 R5=00000000 R6=0060c50c R7=00000000
R8=00000112 R9=00000040 R10=c80e09e8 R11=00000000
R12=00000008 R13=00406ae8 R14=827c9b67 R15=827c99c6
R13Svc=c91a2000 R14Svc=8004d9cc SpsrSvc=20000010
Thread Telephone::Telephone, KernCSLocked=0
Thread full name=Telephone::Telephone
Thread ID=213, KernCSLocked=0
Has anyone got any ideas what I'm doing wrong?
Thanks.
--- On Tue, 30/11/10, George Norton <uk.george.norton-gM/Ye1E23mwN+***@public.gmane.org> wrote:
From: George Norton <uk.george.norton-gM/Ye1E23mwN+***@public.gmane.org>
Subject: Re: [Wild-ducks] Beagleboard-xM
To: "Scamp Scamp" <scamps-ur4TIblo6goN+***@public.gmane.org>
Cc: wild-ducks-Jz5k0oT2vTnIfpBs1kz409i2O/***@public.gmane.org
Date: Tuesday, 30 November, 2010, 8:32
I haven't tried a BeagleBoard XM, but I have booted a Zoom3 from SD.
The XM doesn't have any NAND so u-boot won't be pre-installed on the device. Instead you need to prepare an SD card with an MLO and u-boot.bin binary on it, so that you can boot uboot from the SD card.
If you take a look at the various Linux distributions for the beagleboard they all have .sh scripts for preparing SD cards (MLO is a bit fiddly as it needs to be in the first sector of the disk, copying the file from Windows doesn't seem to work.)
-George
On Mon, Nov 29, 2010 at 4:50 PM, Scamp Scamp <scamps-ur4TIblo6goN+***@public.gmane.org> wrote:
Hi Guys,
I've been using an old beagleboard for sometime using the instructions here: -
http://developer.symbian.org/wiki/BeagleBoard_Quick_Start
However, I now want to try and run the same Symbian images I had before, on the new xM model. Having plugged the board into my PC, I can no longer use minicom/telnet to connect in the same way, and hence cannot run the usual mmc init, etc, commands.
Can anyone tell me how I'm meant to use these newer xM boards?
Thanks
_______________________________________________
Wild-ducks mailing list
Wild-ducks-Jz5k0oT2vTnIfpBs1kz409i2O/***@public.gmane.org
http://developer.symbian.org/mailman/listinfo/wild-ducks
_______________________________________________
Wild-ducks mailing list
Wild-ducks-Jz5k0oT2vTnIfpBs1kz409i2O/***@public.gmane.org
http://developer.symbian.org/mailman/listinfo/wild-ducks
Some facts about Symbian that we are legally obliged to tell you:
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.