yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] vve:
To anybody here:

Is it possible to write a brief step-by-step guide to explain how to compile applications for Universal?

I just need some guidelines: what options should I use for configuration scripts, what environment variables should be set etc.

Let's imagine I'm going to use GNU assembler (as) on my device.

I've downloaded binutils package from GNU site, unpacked it...what's next?

Here's current state of my experience:

1. I have an arm-linux 3.4.1 installed on my PC.

2. I'm able to cross-compile the current CVS kernel and it works :).

P.S. My intention for now is to port a development suite to device itself. Help me please.
[JASJAR, XDA Exec, MDA Pro General] cr2:
The generic, but a very far-fetched answer is : use the openembedded build system.

I wish somebody has corrected the qpegps.ipk and

zroadmap.ipk ...

Tell that to madkat :lol: :lol: :lol:
[JASJAR, XDA Exec, MDA Pro General] vve:
Openembedded seems to be too heavy for my task. See http://oe.handhelds.org/cgi-bin/moin.cgi/RequiredSoftware: Python, Bison...I hope I'm not living in the zoo :). I think there are some more simple solutions for my problem.

Yes, I'm a low level programmer. Regardless of anything madkat could say :) I'll keep trying to find a way to port a development suite to Universal side.
[JASJAR, XDA Exec, MDA Pro General] vve:
What ...arm-linux-gcc in your example should be point to? To a top level ARM stuff, to bin directory in it or to real arm-linux-gcc executable?

Really, it would :). For me, to run gas is not a real aim - it's just a step to create a development system "onboard".
[JASJAR, XDA Exec, MDA Pro General] cr2:
To the real executable. Then it will be included in the all

downstream makefiles.
[JASJAR, XDA Exec, MDA Pro General] vve:
Well, after 'make' command binutils are really compiled and this is really an ARM code! What options (if any) do I need before 'make install'? I'm afraid if this installation will replace my current x86 executables.
[JASJAR, XDA Exec, MDA Pro General] cr2:
Don't compile as root ;)
[JASJAR, XDA Exec, MDA Pro General] madkat:
I hope you're going to test it out, refine it and add it to the Wiki :P

:roll:
[JASJAR, XDA Exec, MDA Pro General] pedroalves:
set --prefix to a different path. see ./configure --help

Having a toolchain on the device is quite possible.

For wince there are at least too projects that have it:

Mamaich's:

http://mamaich.cjb.net/

and Vitaliy's:

http://pocketgcc.sourceforge.net/

With my version of the wince cross toolchain it should also be possible to build a native arm toolchain, as it is based on mamaich's version.

I never tried it, though.

See here:

http://cegcc.berlios.de

For linux, I guess debian arm should have it, no?

Keep up the great work, guys!
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
Hey :`)

Nice to see you back. Hope you had a great time in Vienna. A conference is not like hollidays, but i hope you have enjoyed your time there.

Is there some progress on the kernel from your side?

I have added a link to the technical documentation for the touchscreen in wiki. Maybe this could help?
[JASJAR, XDA Exec, MDA Pro General] ghl10000:
So you guys...

...have your phones just for experimenting with them and obviously don't have to rely on them ?

Forgive me for this sarcastic assumption, but from the early Windows Mobile phones until the Tornado and Universal designs there was a long way until they were really (almost) perfect.

I can remember early devices I had, which really needed all my preparedness and dedication to accept them as phones as the GPRS performance was good, but the performance as a phone was catastrophic.

In these times I wished to get a MS Smartphone once, which really performs in an acceptable way in both segments.

The Tornado and Universal now for the first time are designs which fulfill, if not supersede these requirements.

On the other hand I can understand your approach (to a certain extent).

I myself would have some sort of "Knoppix for MS Mobiles", a Linux environment that runs on top of the MS OS, a design like PocketDOS (which is really very smart).

This would allow me to do some Linux hacks when not at home or having no access to a real mobile PC (e.g. my notebook).

Of course this would be hard to achieve (if not totally impossible) as long as the RAM of these designs still is only 64 MB (note: my older iPAQ had 128 MB !) and/or cannot be (easily) extended.

I admire your courage to obviously be prepared to flash Linux into your phone, thus throwing Windows completely out.

Even Windows haters have to bear in mind that the OS of the mobile phone is just a system providing the functionalities of the phone, rather than a philosophy or a hype.

What Linux definitely does on a PC might not be achievable (in the near future) on a phone device.

While I strongly support the idea of documenting software APIs you cannot expect from manufacturers to open their hardware specs, which they never intended to make public and which wouldn't make sense to the majority of users (and developers).

I wish you all the best for your project and efforts and would be happy if someone encodes a Phone Linux which at least gives me the same functionality as the current Windows Mobile 5 and lets me upgrade to it safely.

If this can be achieved I'd be among those to switch to Linux for Phones.

Honestly speaking I do not think that I will see this for the lifetime of my HTC Universal.
[JASJAR, XDA Exec, MDA Pro General] cr2:
I need to commit some minor changes to CVS, so you

can compile the working kernel too.

I have used the Blueangel haret earlier, but it was too

unreliable, contained the code from evildoers like Larry McVoy, and needed a microsoft compiler to

compile. So i have rewritten some parts of

haret, now it is compiled with gcc, becoming a really

free software.

This part of haret is quite useless for debugging, so i

have removed it.

Download the latest copy and tell me about your experiences.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: So you guys...

I think you are too rational. It's all about to have some fun, isn't it? :-)
[JASJAR, XDA Exec, MDA Pro General] cr2:
Hmm. Why would one want to run Linux on top of

the unstable and insecure 25bit operating system,

whose purpose is milking "the consumers",

when you can remove it from memory, and have the full control over the hardware yourself ?

Universal is not a great video performer, compared to

the himalaya and blueangel, which have a dedicated

video accelerated chipset.

The "video" memory is split into two parts: the first one is in the main RAM, the second one is in PXA270 SRAM.

I am using the first part, the second contains the leftover bitmap

from wince. It can be just cleaned on startup, so it

will not confuse you.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Ok, I see. That's why I haven't see the pinguin at all when using haret 0.3.6 (the latest one). I thought it's a sign this version is incompatible with Universal...
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: So you guys...

I am wondering if you are just trolling, or are really serious 8) :shock:

For making calls I am using a real Linux phone -

Motorola A780. It has a builtin GPS receiver and complete maps of Europe. That's all what i need from

such device: call, answer the calls, sms and GPS route

planning. Soon we will do it all with free software on

our phones :lol:
[JASJAR, XDA Exec, MDA Pro General] cr2:
Sorry, i forgot to attach the binary.
[JASJAR, XDA Exec, MDA Pro General] cr2:
you should use "console=tty0" now.

and "bootlinux" should be replaced by "boot2"

I can upload my compiled kernel (900K)

for testing.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Kernel upload: yes, it would be great (until I have a better one - no I'm joking :-) )
[JASJAR, XDA Exec, MDA Pro General] cr2:
Try "dump wince" and "dump pxa27x"

with haret, it is interesting to see the output.

I will upload the kernel now.
[JASJAR, XDA Exec, MDA Pro General] cr2:
It is too big.

Take it at

http://jornada820.sf.net/files/zi
[JASJAR, XDA Exec, MDA Pro General] cr2:
FB screenshot.

framebuffer screenshot:
[JASJAR, XDA Exec, MDA Pro General] pasztorl:
With the new haret I can boot my compiled kernel too.

The frame buffer is not working properly on my device.

I see about ten pixel black line at the top.

Can you upload your initrd? I should try the X server.
[JASJAR, XDA Exec, MDA Pro General] pasztorl:
Re: FB screenshot.

Good work! :)

If you write your home address I will send you a gift! ;)

( http://www.unicum.hu )
[JASJAR, XDA Exec, MDA Pro General] cr2:
Are you using the standard pxafb driver ?

The driver is pxa25x-oriented, so maybe the pixclock

should be halved.

Put your modules on the Blueangel initrd. The X server

is in /usr/X11R6/bin, but it needs a touchscreen device. Login over usb, and create a fake with

something like

mkdir /dev/touchscreen
touch /tmp/0
ln -sf /tmp/0 /dev/touchscreen/0

You can also try opie/gpe as described on the Blueangel page at handhelds.org.
[JASJAR, XDA Exec, MDA Pro General] pasztorl:
I tried your kernel and has the same result. :(
[JASJAR, XDA Exec, MDA Pro General] cr2:
I don't understand what do you mean.

The black block you see on the screenshot

has 16384 black

pixels, which represent the available memory

(64MB=16384*(4K pages)). The red line is the

kernel+ramdisk, how it is located in the memory

(the black pixels are replaced by red).

These pixels were blue when the kernel was first loaded, so if you can see the red pixels

then haret has reached the last "assembler" stage.
[JASJAR, XDA Exec, MDA Pro General] pasztorl:
OK. So it is not the kernel frame buffer problem, this is a haret feature.

So... When I see this screen I know, the kernel and the initial ramdisk are loaded to memory.

How can I know, the kernel really boots?

How can I see the kernel frame buffer output?
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Sorry to bother you again but i'm having problems to get the Universal kernel up and running. First of all whatever kernel I try (including your "zi" image) all I see is the memory map you describe. I have several question:

1. Is the current CVS tree actual one? It doesn't seem to be...

2. What framebuffer device shall be used? pxafb or htcuniversalfb? In order to compile the htcuniversalfb I had to modify Kconfig file in drivers/video.

3. Should be fb device compiled as a module or as a part of the kernel?

4. I replaced /lib/modules in blueangel initrd (I hope we speak about the same image) with the compiled ones (/lib/modules/2.6.12-hh2-xda0-un0). Is this ok?

Is there anything I'm missing?
[JASJAR, XDA Exec, MDA Pro General] cr2:
Do you have "mem=63M" on the kernel commandline ?

I forgot that it is necessary for the "simple framebuffer"

to work :(
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
bootstrap-image

Is there any bootstrap-image for the Blueangel? I have found one for the Hx4700 and tried it out (with some modifications, copied in modules an deleting some modules and so on) but i think it might not be a healty thing for the Universal.

I have googled and googled for it but havent found any yet. Can somone help me out here?

U see, i am trying to get XFCE to run on it, but i cant get it to work without GPE running in background.

*UPDATE*

I am trying to build one for my self with bitbake. But this one i will try for the HTC Universal. Has implemented some htc universal files (config files).

It's compiling now ( has odne in one and a half hour allready) will come back if i manage to bulid it.

If it goes well, i will try bulid and OPIE and a GPE image too.
[JASJAR, XDA Exec, MDA Pro General] cr2:
LCD suspend/resume.

Hmm. There is something wrong in the code, or

htcuniversal_lcd and pxafb don't want to play together.

Wince does the following (GPIOA2 is the audio chip power):

--- close cover ---
GPIOB11 S 0 NIGHT_SENSOR 475663
GPIOA11 S 0 COVER_ROTATE 476086
GPIOD12 S 0 FL_PWR 476393
GPIOD14 S 0 BL_KEYP_PWR 476650
CKEN1 PWM1 off
CKEN16 LCD off
GPLR86 0 476848
GPLR87 0 476849
GPIOA15 S 0 PWR somethingA15 476851
GPIOB6 S 0 LCD_PWR3 476875
GPIOC9 S 0 LCD_PWR1 476897
GPIOC10 S 0 LCD_PWR2 476919
GPIOD13 S 0 LCD_PWR4 476941

--- open cover---
GPIOA11 S 1 COVER_ROTATE 485994
GPIOD12 S 1 FL_PWR 486301
GPIOD14 S 1 BL_KEYP_PWR 486404
CKEN1 PWM1 on
CKEN16 LCD on
GPLR86 1 486476
GPLR87 1 486477
GPIOA2 S 1 PWR somethingA2? 486480
GPIOA15 S 1 PWR somethingA15 486502
GPIOB6 S 1 LCD_PWR3 486524
GPIOC9 S 1 LCD_PWR1 486549
GPIOC10 S 1 LCD_PWR2 486571
GPIOD13 S 1 LCD_PWR4 486593
GPIOB11 S 1 NIGHT_SENSOR 486722
[JASJAR, XDA Exec, MDA Pro General] milanvot:
wlan driver

Today I made a major step forward with the wlan driver. I can see a new network interface wlan0, I can set ESSID and WEP key.

#iwconfig
lo no wireless extensions.

usb0 no wireless extensions.

wlan0 IEEE 802.11b+ ESSID:"EZ0437" Nickname:"acx100 v0.2.0pre8"
Mode:Auto Channel:1 Access Point: 00:00:00:00:00:00
Bit Rate=22 Mb/s Tx-Power=18 dBm Sensitivity=0/255
Retry min limit:7 RTS thr:off
Encryption key:XXXX-XXXX-XX Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

next step is to associate with an AP and transfer some data ... :-)
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: wlan driver

That's the most tough part :)

Can you dump the EEPROM contents ?

The links having most information are:

http://195.66.192.167/linux/acx_patches

svn://fuzzyneural.net/h6300/omap-linux/trunk
[JASJAR, XDA Exec, MDA Pro General] AnimaLupi:
Hi everyone, just exiting from lurking mode to say "good job!"...

This latest news about the wifi starting to work just made me happy... this functionality and a working touchscreen are all I need to migrate my stuff from the Zaurus to the Universal.

Sorry I don't have the knowledge and time to be more useful than being just a tester...

Anyway keep going, your work it's really appreciated!

Andrea
[JASJAR, XDA Exec, MDA Pro General] madkat:
Re: LCD suspend/resume.

Why does it try to power on the audio chip, if the audio chip was not powered off? Other than bad M$ code? (To power it off would be a bad thing for people who want to listen to audio with the device closed in their pocket :-) )

What's the difference between this and what htcuniversal_lcd / pxafb do?
[JASJAR, XDA Exec, MDA Pro General] EyeOfTheStorm:
Re: LCD suspend/resume.

It makes sense. There are 2 speakers located on cover. If the cover is closed, you will use the outer one for telefon calls. Otherwise, the inner one. So one of the 2 speakers is turned off, depending on cover state.
[JASJAR, XDA Exec, MDA Pro General] madkat:
Re: LCD suspend/resume.

I will try this - I was certain that the outer speaker was for the ringer - it is much louder than when you test the ringer within WinCE.
[JASJAR, XDA Exec, MDA Pro General] cr2:
Aren't these very outdated projects ?

For the bootloader I'm using the toolchain from videolan

http://download.videolan.org/pub/testing/wince

BTW, do you know why it is impossible to compile

the wince2.11 binaries with gcc ?
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: LCD suspend/resume.

Sounds reasonable. I'm not quite sure what device is

powered with which gpio.
[JASJAR, XDA Exec, MDA Pro General] pedroalves:
Yes, they are a bit outdated.

I have seen that toolchain from videolan. In fact, I have integrated in my

version of the toolchain some of their patches.

Before starting my work on the toolchain, I have tried to reach them on the mailing list, but got no reply.

My version has some important improvements.

I have pragma pack support, which is essential for many win32 structures defined in mingw or in ms's sdks.

Their version uses mingw headers, and msfts runtime only, while mamaich/voxware/cegcc use newlib to have a more complete c runtime. I plan on using mingw's headers too, just haven't got into it yet.

You can download gcc4.1 patches, and binutils patches at

http://cegcc.berlios.de [project page->files]

Never tried it. Only have Pocket PC 2003 SE device.

What are the symptoms?
[JASJAR, XDA Exec, MDA Pro General] cr2:
The linker sets the "minimal wince version" 3.0 in the exe header. There was some talk on the binutils mailing

list some years ago about some 4/8 byte instruction offset.

I'm quite happy with the videolan gcc for compiling the

bootloader 8) ,but i'd like to compile the gps program http://roadmap.digitalomaha.net

for wince2.11.

BTW, do you know how to replace the aygshell* stuff

with the normal menu ? I'm not that much into wince

programming ;)
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: wlan driver

I think there is no EEPROM in acx. It appears to be operating in EEPROMless mode.

Also the data between CPU and acx are transferred using CPU itself probably :-)
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: wlan driver

But there is a _physical_ I2C EEPROM on the motherboard, and it is the same on Blueangel !

Not great for the performance if you'd like to do VoIP ;)

And we need to understand how it is done. The author

of the omap driver told me he can't transfer the data, too.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: wlan driver

I would bet that the acx parameters are stored in the registry ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WZCSVC\Parameters\Interfaces\TIACXWLN1] maybe) and the EEPROM is not used at all.

edit:

I'm wrong probably. The registry entry is a wep key storage.
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Volume adjusting work's :-)

I installed alsamixer and adjusting volume works now. The adjusting only works with alsamixer, not the default one in Opie yet.

Does anyone have a clue how to link the Opie volume control to the alsamixer?

And another thing:

I am able to pair my Universal with my other bluetooth stuff now using the Opie bluetooth manager. The only thing that is missing there is that the bleutooth icon in the tray doesnt change status when bluetooth is on ( like the IRDA tray icon does, it turns red when it's on, and gray when it's off). Would like to see that with the BT icon to, so it turns blue when the BT is on, and grey when it's off.

The bluetooth discover also works in Opie now, when i turned my BT headset on a box popped up and said that someone is trying to connect to me.

Oh man this is going forward. :-)
[JASJAR, XDA Exec, MDA Pro General] madkat:
Does this mean the screen calibration works?

Where can I get binaries? :D
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
No screen calibration is not working yet. I am also waiting for this, i am now using the keyboard to navigate around the menus.

What i did was that i downloaded the HX4700 opie-image and adapted the htcuniversal modules and som other files and scripts form earlier versions of the BA-Opie image.

The first boot of the image it's kind of messy because it stills try to load som HX4700 modules, but after loaded the right modules and a 'update-modules' the next boot behave as normal.

Adjusting background light

For a couple of days ago i was running an GPE image (dont remember wich one) and with that image i was able to adjust the background light, but i am not able to do that in Opie, why is that, wich files do i need to get so i am also able to adjust the backgroundlight in Opie?

Milanvot

If u have some spear time :-) and stalled with the wlan driver. Could you maybe looked in to the hardware volume button so we can control the alsamixer. I have been at the Opie irc channel and they said, to control the alsamixer from Opie we have to write an alsamixer app. for Opie, but we dont need that so long we can adjust volume with the hardware volume button, can you fix that, is it doable??
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Stuck in splash screen

After playing with the wlan driver I'm stuck in the splash screen after reboot. Any help cr2? :-)
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
Re: Stuck in splash screen

Arent you able to hardreset either?
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

I'm able to hardreset the machine but then again, I'm stuck in the splash screen. Now I'm trying to reflash the device...

edit:

...and it helped :-)

edit II:

I was too fast. I can go through Qtek splash screen but I'm stuck in 'Windows Mobile' screen now :-)
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: Stuck in splash screen

You can read this thread first

http://xdaforums.com/viewtopic.php?t=43592

I can tell you how to boot the zImage from the HTC bootloader, but it is unlikely to initialize everything properly. Eventually we should do it, since it is

very similar to the "resume" sequence.
[JASJAR, XDA Exec, MDA Pro General] cr2:
You need a device-specific support patch (ODevice) for opie.

Otherwise, the control interface is in /sys/class/backlight/*
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

I went through this thread but I didn't find anything usefull. I'm afraid I managed to damage the internal DiscOnChip somehow. Now I'm downloading MS Platform Builder to see Wince log :-) Shall I try mtty tool?
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: Stuck in splash screen

They claim that 'task 28' will format DoC, but it is a very

dangerous operation.

It is a good idea.

/dev/ttyUSB0 works in Linux, there is nothing really special

about this 'mtty'.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

It's interesting. Few minutes ago I somehow managed to boot into wince (I don't know how :-)) and I can't start wifi. Maybe it's a proof that there IS an eeprom in acx I have overwritten by accident (an improper pointer cast) ...
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Safe mode

Is there something like the safe mode in wince?
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: Stuck in splash screen

I think that we need to make a EEPROM dump before

messing with the wifi chip.
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: Safe mode

afaik, no.
[JASJAR, XDA Exec, MDA Pro General] cr2:
DoC driver.

cp15 was working on the DoC driver, but i don't know

his current status. The G3 DoC is used on many other

PDAs too.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

Do you think you can make a dump of your eeprom which I can upload to my eeprom?
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

Sorry to bother you again my can you explain how to boot to Linux from the bootloader?
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

I have tried 'task 28' from mtty and the DoC is ok.
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: Stuck in splash screen

Probably yes, but before i will try it i'd like to see

the code :)
[JASJAR, XDA Exec, MDA Pro General] cr2:
Re: Stuck in splash screen

If your universal is not locked, then you can create

a SD bootable image with the 'sdtool.pl' available here

in wiki. The zimage should be loaded above 16MB,

so you don't trash the bootloader internal data, framebuffer and such stuff.
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

May I ask for a little howto? It will take 2 days for me to understand which images & offsets to use...
[JASJAR, XDA Exec, MDA Pro General] milanvot:
Re: Stuck in splash screen

99976 PID:f3cbe6c2 TID:f3c762d2 W:DetectWlanOnEvent
101970 PID:f3cbe6c2 TID:f35d892a Data Abort: Thread=93278574 Proc=908afcb0 'device.exe'
101974 PID:f3cbe6c2 TID:f35d892a AKY=00000009 PC=011f7c00(tiacxwln.dll+0x00017c00) RA=011f7bf8(tiacxwln.dll+0x00017bf8) BVA=088be69a FSR=00000003
101984 PID:f3cbe6c2 TID:f35d892a RaiseException: Thread=93278574 Proc=908afcb0 'device.exe'
101987 PID:f3cbe6c2 TID:f35d892a AKY=00000009 PC=03f7dbd4(coredll.dll+0x0001dbd4) RA=9054d6e0(NK.EXE+0x0000d6e0) BVA=00000001 FSR=00000001
[JASJAR, XDA Exec, MDA Pro General] goxboxlive:
GPE or OPIE

Here is the (xdm) startup screen i would like to se on our universal. It's about wich GUI to start.

The H2200 has managed it.

http://opdenacker.org/pda/h2210/photos/graphics/gpe_or_opie_Big.jpg