QUOTE(jessed @ Feb 10 2006, 06:25 AM)
I used the Archos supplied toolchain and kernel sources, which can be downloaded from their site:http://www.shoparchos.com/product.aspx?sku...0&culture=en-US
My config is based off the av500 config in their kernel source. The main change I made was turning off compressed boot loader in ROM/flash under general setup. I think the pma uses it, but those addresses are incorrect, but I'm not 100% sure. I'll attach my latest config, which isn't working yet.
I naively used my own built cross-compiler and a normal 2.6 kernel with some omap patches. These kernels made the archos shut down right after loading the aimage.img. This is worth nothing!
I tried (just like you) to use the official pma kernel source, toolchain and your config after reading your reply. I saw the same thing. The PMA didn't automaticly shutdown anymore. I saw this was actually working better than my own attempts. My second step was to build the very same kernel with my own toolchain which is based on Gcc 3.4.5. I had to modify many .c files in the kernel to get it building with gcc3. I even had to remove some C-flags that were unknow in GCC3. When I booted the new image, the same old behaviour returned: the PMA shuts down again. Not good!
The most frustrating part is yet to come. In my later attempts to boot the same kernel as in the first run, my PMA also shutted down. Although I'm pretty optimistic about seeing different behaviour, I'm less happy with the fact that it's not 100% predictable what happens (assuming I didn't make a mistake). I would have been very happy to see the same thing happening (not shutting down) with a kernel built with my own toolchain. This would give me confidence my toolchain and CFLAGS are correct AND opens the opportunity to compile more recent kernels easily. Ok, I'm going too fast now.
The kernel sources Archos provides are crap, but I really think they worked the time my archos didn't shut down automaticly!
We are missing very important stuff however. Very vital parts like the framebuffer driver are missing. I think it will give confidence to see a sign of life when booting a self built image. Maybe we could get this by attaching very common usb hardware, like an optical mouse which will give light once the USB host gets initialised on bootup. If this happens with a self-built kernel, an open-source PMA lives!!
Btw, you've applied sashz's bootloader crack, correct? Just making sure we're on the same page.
Yes, I'm able to boot modified images. But all working images use the pre-built kernel provided by Archos.
My plan of action is:
* Determine if the kernel works or see it's just a side effect that the PMA doesn't shut down
* Prove a self-built cross-compiler (fuck gcc2) also works
* Makeing up a list of needed changes to get an vanilla kernel working with the stock bootloader
* See if the open-source dm270fb works on the PMA