SDcard image generation alpha version released

[nathan]

The first alpha release of the Raspberry Pi image generation is now available in the git tree.

Note:
Downloading the GPU firmware will take a while. So be patient... ;-)

The sdcard image will contain:
- fat partition containing the GPU firmware and kernel image
- ext4 partition containing the root file system

Please give it a try and post any comments/bug reports to this mailing list.

Nathan.

[Pau]

I'm in vacations right now, I will test it after 21th of this month.

Thank you for your job! It looks very promising.

Cheers
--
./p4u

--
You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.
To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/TbbkVS_MtA8J.
To post to this group, send email to raspberrypi...@googlegroups.com.
To unsubscribe from this group, send email to raspberrypi-openw...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.

[Nathan Huizinga]

Have a nice vacation!

Grtz,
Nathan.

Pau <hak...@gmail.com> schreef:

[Pau]

Yesteday I did the first try.
1. update my git source (git pull)
2. copy again the config file
3. compile
4. dd raspberrypi-openwrt/bin/raspberrypi/openwrt-raspberrypi-sdcard.img to sd card

Then I put the sd into the rspi and... nothing happens. I saw this same issue when the partitions or bootloader are not fine.
There is a green led on the board namesd "OK" which is blinding when the SD card boots, but not in this case.

Let me know if I can test something more.

Cheers
--
./p4u

[Nathan Huizinga]

Hi p4u,

Thanks for testing! Although the results are not what I hoped for ;-)

There are many things that can be wrong:
1. Wrong partition generation
2. GPU firmware files missing/corrupt
3. Linux kernel file not correctly built
4. Second partition (containing rootfs) not working
5. ...

Could you mount the SDcard in your PC to check if you are able to see
the files on the FAT and/or EXT4 partitions? This would exclude points 1
and 4.

I did mount the generated image via a loop-back device to check, but did
not see anything wrong.

The current Linux kernel version has an issue when booting a compressed
image. And we're currently using a compressed Linux kernel ;-) So this
might be a problem here.

I will try to make some changes to the build process, so that we should
be able to tackle this problem.

As an alternative for the real dare devils / hackers:
try the "kernel_rework_patches" git branch. This contains the latest
kernel patches from https://github.com/raspberrypi/linux up until Sat
July 14, 2012.

Keep you posted!

Grtz,
Nathan.

On 23-07-12 12:46, Pau wrote:
> Yesteday I did the first try.
> 1. update my git source (git pull)
> 2. copy again the config file
> 3. compile
> 4. dd raspberrypi-openwrt/bin/raspberrypi/openwrt-raspberrypi-sdcard.img
> to sd card
>
> Then I put the sd into the rspi and... nothing happens. I saw this same
> issue when the partitions or bootloader are not fine.
> There is a green led on the board namesd "OK" which is blinding when the
> SD card boots, but not in this case.
>
> Let me know if I can test something more.
>
> Cheers
> --
> ./p4u
>
>
>
> On Thu, Jul 12, 2012 at 1:38 PM, Nathan Huizinga

> <nathan....@gmail.com <mailto:nathan....@gmail.com>> wrote:
>
> __ Have a nice vacation!
>
> Grtz,
> Nathan.
>
>
>
> Pau <hak...@gmail.com <mailto:hak...@gmail.com>> schreef:

>
> I'm in vacations right now, I will test it after 21th of this month.
>
> Thank you for your job! It looks very promising.
>
> Cheers
> --
> ./p4u
>
>
>
> On Fri, Jul 6, 2012 at 10:18 PM, nathan

> <nathan....@gmail.com <mailto:nathan....@gmail.com>>

> wrote:
>
> The first alpha release of the Raspberry Pi image generation is now available in the git tree.
>
> Note:
> Downloading the GPU firmware will take a while. So be patient... ;-)
>
> The sdcard image will contain:
> - fat partition containing the GPU firmware and kernel image
> - ext4 partition containing the root file system
>
> Please give it a try and post any comments/bug reports to this mailing list.
>
> Nathan.
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "Raspberry Pi Openwrt Development" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/TbbkVS_MtA8J.
> To post to this group, send email to
> raspberrypi...@googlegroups.com

> <mailto:raspberrypi...@googlegroups.com>.

> To unsubscribe from this group, send email to
> raspberrypi-openw...@googlegroups.com

> <mailto:raspberrypi-openwrt-dev%2Bunsu...@googlegroups.com>.

> For more options, visit this group at
> http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "Raspberry Pi Openwrt Development" group.
> To post to this group, send email to
> raspberrypi...@googlegroups.com

> <mailto:raspberrypi...@googlegroups.com>.

> To unsubscribe from this group, send email to
> raspberrypi-openw...@googlegroups.com

> <mailto:raspberrypi-openwrt-dev%2Bunsu...@googlegroups.com>.

> For more options, visit this group at
> http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Raspberry Pi Openwrt Development" group.
> To post to this group, send email to
> raspberrypi...@googlegroups.com

> <mailto:raspberrypi...@googlegroups.com>.

> To unsubscribe from this group, send email to
> raspberrypi-openw...@googlegroups.com

> <mailto:raspberrypi-openwrt-dev%2Bunsu...@googlegroups.com>.

[Pau]

The image seems to be correct:

$ file openwrt-raspberrypi-sdcard.img
openwrt-raspberrypi-sdcard.img: x86 boot sector; partition 1: ID=0xc, active, starthead 1, startsector 63, 33201 sectors; partition 2: ID=0x83, starthead 1, startsector 33327, 98721 sectors, code offset 0x0

$ sudo mount -o loop,offset=$[63*512] openwrt-raspberrypi-sdcard.img ~/mnt

$ ls ~/mnt/
arm128_start.elf  arm192_start.elf  arm224_start.elf  bootcode.bin  cmdline.txt  COPYING.linux  kernel.img  LICENCE.broadcom  loader.bin  start.elf

$ sudo umount ~/mnt

$ sudo mount -o loop,offset=$[33327*512] openwrt-raspberrypi-sdcard.img ~/mnt

$ sudo mount ls ~/mnt/
bin  dev  etc  lib  lost+found  mnt  overlay  proc  rom  root  sbin  sys  tmp  usr  var  www

As an alternative for the real dare devils / hackers:
try the "kernel_rework_patches" git branch. This contains the latest kernel patches from https://github.com/raspberrypi/linux up until Sat July 14, 2012.

I'll try it.

If you want to provide me an image I will test it. Maybe you may upload it to the git repository.

--
./p4u

        <nathan....@gmail.com <mailto:nathan.huizinga@gmail.com>>

        wrote:

            The first alpha release of the Raspberry Pi image generation is now available in the git tree.

            Note:
            Downloading the GPU firmware will take a while. So be patient... ;-)

            The sdcard image will contain:
            - fat partition containing the GPU firmware and kernel image
            - ext4 partition containing the root file system

            Please give it a try and post any comments/bug reports to this mailing list.

            Nathan.


            --
            You received this message because you are subscribed to the
            Google Groups "Raspberry Pi Openwrt Development" group.
            To view this discussion on the web visit
            https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/TbbkVS_MtA8J.
            To post to this group, send email to

            raspberrypi-openwrt-dev@googlegroups.com

            <mailto:raspberrypi-openwrt-d...@googlegroups.com>.

            To unsubscribe from this group, send email to

            raspberrypi-openwrt-dev+unsub...@googlegroups.com

            <mailto:raspberrypi-openwrt-dev%2Bunsubscribe@googlegroups.com>.

            For more options, visit this group at
            http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.


        --
        You received this message because you are subscribed to the
        Google Groups "Raspberry Pi Openwrt Development" group.
        To post to this group, send email to

        raspberrypi-openwrt-dev@googlegroups.com

        <mailto:raspberrypi-openwrt-d...@googlegroups.com>.

        To unsubscribe from this group, send email to

        raspberrypi-openwrt-dev+unsub...@googlegroups.com

        <mailto:raspberrypi-openwrt-dev%2Bunsubscribe@googlegroups.com>.

        For more options, visit this group at
        http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.

    --
    You received this message because you are subscribed to the Google
    Groups "Raspberry Pi Openwrt Development" group.
    To post to this group, send email to

    raspberrypi-openwrt-dev@googlegroups.com

    <mailto:raspberrypi-openwrt-d...@googlegroups.com>.

    To unsubscribe from this group, send email to

    raspberrypi-openwrt-dev+unsub...@googlegroups.com

    <mailto:raspberrypi-openwrt-dev%2Bunsubscribe@googlegroups.com>.

    For more options, visit this group at
    http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.


--
You received this message because you are subscribed to the Google
Groups "Raspberry Pi Openwrt Development" group.
To post to this group, send email to

raspberrypi-openwrt-dev@googlegroups.com.

To unsubscribe from this group, send email to

raspberrypi-openwrt-dev+unsub...@googlegroups.com.

For more options, visit this group at
http://groups.google.com/group/raspberrypi-openwrt-dev?hl=en.

--
You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.

To post to this group, send email to raspberrypi-openwrt-dev@googlegroups.com.
To unsubscribe from this group, send email to raspberrypi-openwrt-dev+unsub...@googlegroups.com.

[Mr R.B.]

I have given the "kernel_rework_patches" image a try and still find the Pi  does not boot up.

[N.M.]

I have the same problem, I could build the image successfully, but not boot (screen stays blank)

[N.M.]

Btw, arteq did post an alpha version of openwrt on the rasb pi forum:

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=1098&p=133382&hilit=openwrt#p133382 

ftp://artekw.cerbero.pl/openwrt/trunk/brcm2708 

But the version is already one month old and have not heard anything new from him.

I would prefer to have the ability to build the image myself, as the goal of this project is.

I tried to copy its "boot" / vfat files over to the sdcard (the kernel was about 3,4 mb, while ours was 1,7 or so..)

but it did not change the results: Screen stayed blank.

( which is quite strange... given the point that the files worked and only the vfat partition is needed to get the screen up (as I think) - this should work if nothing is completly wrong with the partitioning of the card?

(or am I wrong?)

[nathan]

@Mr R.B.

Thanks for testing this branch. It seems that both branches suffer the same problem.

@N.M.

You are probably right. At this point I suspect the FAT filesystem generation and/or the partition generation steps. The FAT filesystem generation differs from the way it is done in the patch you linked. But the partition generation is done the same way.

Can you verify that this image is working?!? That will help me pinpointing the problem faster.

Grtz,

Nathan.

[N.M.]

Yes, that Image does work.

However, there are still these nasty SDCard Write not finished Errors on the screen, but none then less, it does work.

Thanks

[Nathan Huizinga]

Ok, thanks for the quick reply.
Now I have some clues to follow ;-)

The sdcard errors should be fixed with the latest patches...

Grtz,
Nathan.

"N.M." <xenomo...@gmail.com> schreef:

--
You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.

To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/hiW_JvbZwWwJ.
To post to this group, send email to raspberrypi...@googlegroups.com.
To unsubscribe from this group, send email to raspberrypi-openw...@googlegroups.com.

[N.M.]

well I could not integrate the patch 5 into the "clean" openwrt trunk checkout.

I do not know how to correctly integreate that patch file into the checkout, as I have never done that.

As soon as you got an new version, I am looking forward to test it! :)

[N.M.]

Ok another quick note:

I did an fresh install of the OpenWRT trunk today and did recompile the whole stuff

[ installing build as usual  http://wiki.openwrt.org/doc/howto/buildroot.exigence ]

but I did also do 

echo CONFIG_TARGET_brcm2708=y > .config
make defconfig
make download

to make an fitting default config for the rasp pi.

after that I did build the whole image as usual with make.

After the make process ended, I found the images in the bin/brcm2708 folder, directly made for 128, 192 or 224 mb CPU RAM usage.

I could flash them and boot and everything works, it looks like even audio could work.

BUT: in target/linux/brcm2708 the folder names state that the trunk is on the patch level 3.3 - and the mmc0 final write errors are on this image persistent,

so it seems like the patch 5 is not yet checked in the openwrt trunk.

Any idea how to integrate this latest patch? that would be awesome.

Thank you very much for your work!

Am Freitag, 6. Juli 2012 22:18:37 UTC+2 schrieb nathan:

[nathan]

Thanks for the thinking along with me!

I managed to fix the branch  "kernel_rework_patches" by using small parts of the patch 5 ;-), so eventually I think

that more parts of this patch should be used.

The generated image boots correctly now and you should be able to have console access with an USB keyboard.

Note:

The compiler flags have changed, so a complete rebuild is needed:

• cp configs/config-rpi ./config
  
• make menuconfig (and save the updated config)
• make world V=99

And take a long coffee break... (~ 2.5 hours).

If this is working for everyone, I'll start cleaning the "kernel_rework_patches" branch and merge it into the master/head.

The second step will be integrating the patch 5, but based on the 3.1.9 Linux kernel. Because this is the "official" supported kernel for now.

Other suggestions/feature requests are welcom!

Grtz,

Nathan.

[Nico Maas]

You are most welcome!
I deleted my working folder and made an clean checkout,
did copy the file, needed to select the Raspberry-Pi as "build target" because the broadcom was selected as default,
saved the file and now it is compiling.

I have a VMWare Ubuntu running, so it will take some time, as my box is a bit old.
But as soon as I come home this evening ( I hope in 10 hours or so ), I will try the image and see what came out! :)

Greetings,

Nico

2012/8/3 nathan <nathan....@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.

To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/eVA3HbIe4zwJ.

[Mr R.B.]

I also have this now compiling on my laptop. Will update once it has been tested.

2012/8/3 nathan <nathan....@gmail.com>

To post to this group, send email to raspberrypi-openwrt-dev@googlegroups.com.
To unsubscribe from this group, send email to raspberrypi-openwrt-dev+unsub...@googlegroups.com.

[N.M.]

Sadly the screen still stays blank :(.

Sorry!

Could not get it to work :/!

[Mr R.B.]

Seconds this did not work. I was able to build a img from the openwrt repo. It was built based on the brcm2708 config.

If it helps the file can be found here http://eevahome.ath.cx/openwrt-brcm2708-sdcard-vfat-ext4_224.img

This image is running fine on my second pi.

[N.M.]

Another - maybe interessting info:

There is a new start file in the raspberry pi github to launch the rasp pi cpu not only with 128, 192 or 224, but 240 mb!

And yes, with the original openwrt, it does work!

just download, copy to the boot partition and name it start.elf, as you would do when changing these files.

Here is the link: https://github.com/raspberrypi/firmware/tree/master/boot 

[N.M.]

Ok, these errors are still persistent:

mmc0: final write to SD card still running

mmc0: Timeout waiting for hardware interrupt - cmd12.

mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900

It does not matter which sdcard or image, they still come up all the time, until the OpenWRT System really bricks and I have to reformat the SDCard with a fresh copy.

Any idea how to fix this?

I think it could be that an new kernel could resolv these errors, but "just copying" the new kernel.img from the github (look above) did not work as rasbpi did not boot correctly.

[nathan]

I have uploaded a clean build image:

http://raspberrypi-openwrt.googlecode.com/files/openwrt-raspberrypi-sdcard.img.bz2

Please give it a try and report any problems.

I'll write some build instructions in the coming days, as I'm now on holidays ;-)

Grtz,
Nathan.

[N.M.]

awesome!

that did work!

no filesystem errors, no problems.

but it seems like not all patches are integrated, i.e. the soundcard is not integrated

have some nice holidays, looking forward to your results.

[Mr R.B.]

That build works for you? I get a kernel panic. Mounting the file system all I can see is /lib and /root these are the only folders present. Hmm strange.

[Nico Maas]

Maybe your dl is corrupt? Try downloading the tar again? I did download the tar, untar with 7zip, formated the sdcard with sdcard formater/official tool and copyed the img with some windows tool - all on win7

--

You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.

To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/vn5J8UwypWIJ.

[Mr R.B.]

Hmmm strange, seems the sd card was not being unmounted when I ran umount and this messed up the write. All sorted and working here.

On Monday, August 6, 2012 10:02:26 AM UTC+1, N.M. wrote:

Maybe your dl is corrupt? Try downloading the tar again? I did download the tar, untar with 7zip, formated the sdcard with sdcard formater/official tool and copyed the img with some windows tool - all on win7

Am 06.08.2012 10:33 schrieb "Mr R.B." <mr.r.b...@gmail.com>:

That build works for you? I get a kernel panic. Mounting the file system all I can see is /lib and /root these are the only folders present. Hmm strange.

On Sunday, August 5, 2012 10:55:38 AM UTC+1, N.M. wrote:

awesome!

that did work!

no filesystem errors, no problems.

but it seems like not all patches are integrated, i.e. the soundcard is not integrated

have some nice holidays, looking forward to your results.

--
You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.
To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/vn5J8UwypWIJ.

To post to this group, send email to raspberrypi-openwrt-dev@googlegroups.com.
To unsubscribe from this group, send email to raspberrypi-openwrt-dev+unsub...@googlegroups.com.

[Nathan Huizinga]

You are correct. This build is not yet up-to-date and does not contain
all features from the "patch 5".

I'll start lining up this version with the official OpenWrt version
containing the "patch 5".

First I want to play a bit with my Rpi, because I finally have received
mine! Yeah!

Grtz,
Nathan.

> --
> You received this message because you are subscribed to the Google
> Groups "Raspberry Pi Openwrt Development" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/syQKjw34XqYJ.

[Nico Maas]

Awesome!

Yeah I am really looking forward to this,

especially getting it to work with all patches, latest openwrt revision and 240 mb ram image for another 16 mb on the cpu!

awesome!

2012/8/6 Nathan Huizinga <nathan....@gmail.com>

[Mr R.B.]

Just as a side not, since the image now boots, I have removed the image that I had uploaded. (As I can see a few tries to download the file)

[N.M.]

Hi there,

just wanted to ask when its planed to update the firmware to the latest version (raspi firmware / openwrt trunk)?

Thank you very much!

[Pau]

Hi.

@Nathan, I have some questions for you.

1. In rspi github there is a new kernel version 3.2.27, would be nice to upgrade. As far I know the only thing we need to do is to upgrade the files on target/linux/raspberrypi of OpenWRT to the new kernel version.

2. Where did you get all these linux patches? In raspberrypi github I can see the kernel source code but not the patches. Did you make all of them using git diff between a clean copy of linux and the one on github? If so, it is quite crazy :-S

3. Any special point of using eglibc instead of uclibc?

4. I believe upgrade to last openwrt trunk would be easy, it is just a matter of doing a pull. But it would be nice to start integrating it to the current OpenWRT source tree, so maybe you/we can write a patch or a targz which can be simply extracted in the root of OpenWRT buildroot. Can you provide a list of the files added or modified by you? Later on we can send this patches/targz to OpenWRT developers.

I would like to help you but you should provide a little more of information.

Thank you!
--
./p4u

--

You received this message because you are subscribed to the Google Groups "Raspberry Pi Openwrt Development" group.

To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/5tejyA4himgJ.

[Pau]

By the way, did you know that? http://www.zoobab.com/raspberry-pi-openwrt

--
./p4u

[Gregory Dymarek]

Isn't it based on the patches from here?

To unsubscribe from this group, send email to raspberrypi-openwrt-dev+unsub...@googlegroups.com.

[Mr R.B.]

That link is what I used to get my last build working, which has since been deleted as I used the pi for other things now.

[nathan]

@N.M:
As from now I have updated the OpenWrt to revision 33369 (Attitude Adjustment).
When the final version is released of Attitude Adjustment, I'll update again.
The RPi firmware will be next, but will take some time for me to sync with all patches since start of August.

@p4u:
The current kernel version is 3.3.8, because OpenWrt does not longer support 3.1 and 3.2 kernels.
So I had to make some changes to the existing patch set to get applied on top of the 3.3.8 sources.
The patches are indeed from the github site and extracted from git manually ;-) That's why it takes so much time
to get the individual patches and get them applied correctly in the OpenWrt build environment.

Because the Rpi is not a device with real resource limitations (256MB RAM and >2GByte storage), I choose for eglibc because of the following:

From: http://www.eglibc.org/home

Embedded GLIBC (EGLIBC) is a variant of the GNU C Library (GLIBC) that is designed to work well on embedded systems. EGLIBC strives to be source and binary compatible with GLIBC. EGLIBC's goals include reduced footprint, configurable components, better support for cross-compilation and cross-testing

 
So a library designed for embedded, but with the intention to be source and binary compatible with the glibc library. That's why I choose this one.

Al my changes can be extracted from git and when everything is settling down, such a list of changes can be made. Currently I have modified the "brcm2708" target, which
was initially created by Ian Ridge and applied to OpenWrt mainstream. The "raspberrypi" target has been completely replaced by the "brcm2708" target.

Interesting link you sent, I didn't know this one. Thanks!

Every kind of help is welcome, and I'm happy to provide all kinds of details to get you going.

Grtz,
Nathan.

[Pau]

The current kernel version is 3.3.8, because OpenWrt does not longer support 3.1 and 3.2 kernels.
So I had to make some changes to the existing patch set to get applied on top of the 3.3.8 sources.
The patches are indeed from the github site and extracted from git manually ;-) That's why it takes so much time
to get the individual patches and get them applied correctly in the OpenWrt build environment.

Dammit, there exist any way to do it less manual?

Because the Rpi is not a device with real resource limitations (256MB RAM and >2GByte storage), I choose for eglibc because of the following:

Ok, and I can adda another point to use Eglibc: Debian has choosed it. However in my experience eglibc support in openWRT is not so good than uclibc.
Many packages don't compile with eglibc (not the important ones) because it seems to be not so maintained.
Another bad point is that you cannot use standar OpenWRT repository because these binaries are compiled with uClibc and they are not compatible.
However, it is just a matter of changing it in the menuconfig. The user can choose :-)

Al my changes can be extracted from git and when everything is settling down, such a list of changes can be made. Currently I have modified the "brcm2708" target, which

was initially created by Ian Ridge and applied to OpenWrt mainstream. The "raspberrypi" target has been completely replaced by the "brcm2708" target.

And what is the difference between the RsPi target of OpenWRT mainstream [1] and your target? Instead of working in paralel, would be great to join effors.

Thanks for your job!

[1] https://dev.openwrt.org/browser/trunk/target/linux/brcm2708/profiles/100-RaspberryPi.mk

--
./p4u

To view this discussion on the web visit https://groups.google.com/d/msg/raspberrypi-openwrt-dev/-/qKHLq1BN3nkJ.

To post to this group, send email to raspberrypi...@googlegroups.com.

To unsubscribe from this group, send email to raspberrypi-openw...@googlegroups.com.