mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Anton Botvalde <anton.botvalde@gmail.com>
To: Roland Hieber <r.hieber@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Status of ptxdist and distrokit raspberry pi 2 images
Date: Wed, 20 Sep 2017 21:27:44 +0200	[thread overview]
Message-ID: <CANW-H2KZ7wqVecg8C+mxjBxVB-oQ1nUoY-teEcFSuOaJjMwu3w@mail.gmail.com> (raw)
In-Reply-To: <560f087f-a7b2-211f-6d9b-cd6a715e67e8@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 2772 bytes --]

Thanks for the reply!
I tried out what you said but I had no success with copying the zImage to
the boot partition.
I git cloned the official bearbox repo and tried different tagged releases
and I noticed that the last version that appear to work on my rpi2 is
v2017.03.0 and the versions afterwards appear to be broken (I haven't tried
them all yet but I am guessing none of them work on rpi2)..

2017-09-18 16:42 GMT+02:00 Roland Hieber <r.hieber@pengutronix.de>:

> Hi,
>
> On 11.09.2017 20:22, Anton Botvalde wrote:
>
>> Hello,
>>
>> I am new to the world of ptxdist and firmware image building. To get my
>> feet wet I have tried to build an image for my raspberry pi 2 with ptxdist
>> and distrokit following the blog post on the pengutronix homepage (
>> http://pengutronix.de/en/2017-08-28-distrokit-a-playground-
>> bsp-for-ptxdist.html <http://pengutronix.de/en/2017
>> -08-28-distrokit-a-playground-bsp-for-ptxdist.html>).
>>
>> The image for rpi2 is successfully built but I am unable to get the image
>> working on my rpi2. Nothing happens after the gpu firmware has booted and
>> using serial to usb connector gives nothing but radio silence so I am
>> guessing that the kernel is not booting at all. I have tried several sd
>> cards and another rpi2 so I have ruled out faulty hardware. I also tried
>> building an image for rpi1 but it didn't work as well.
>>
> I just tried it out, and you're right. We should see some barebox
> messages, and then some systemd startup messages, followed by a login
> prompt. However, the system does not even seem to start the barebox
> bootloader.
>
> I'm not sure how to debug this, but you could try to work-around this bug
> by copy /boot/zImage from the second partition on the SD card to the boot
> partition, and changing "kernel=barebox.bin" to "kernel=zImage" in
> config.txt.
>
> I found the following github repo (https://github.com/rohieb/Dis
>> troKit-rpi-ibrdtn <https://github.com/rohieb/DistroKit-rpi-ibrdtn>)
>> which seemed aimed at distrokit and rpi images so I tried to build an image
>> with it instead and managed to get an image that actually boots on my rpi2.
>>
>
> This is one of my old repos which I used as a playground for DistroKit
> when working on my master's thesis. It is a fork of an old version of the
> official DistroKit Git repo. Back then, I only had access to a RPi1, so I
> used platform-rpi. Also, this was before platform-rpi and platform-v7a was
> recently overhauled in DistroKit in July.
>
> What is the official status of the distrokit support for raspberry pi?
>>
>
> RPi 1 should work with platform-rpi, RPi 2 should work with platform-v7a.
> RPi 3 should in theory also work with platform-v7a, but I think no one has
> come around yet to testing that...
>
>  - Roland
>

[-- Attachment #1.2: Type: text/html, Size: 4082 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-09-20 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 18:22 Anton Botvalde
2017-09-18 14:42 ` Roland Hieber
2017-09-20 19:27   ` Anton Botvalde [this message]
2017-09-20 19:41     ` Uwe Kleine-König
2017-09-21 13:31       ` Lucas Stach
2017-09-21 16:28         ` Anton Botvalde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANW-H2KZ7wqVecg8C+mxjBxVB-oQ1nUoY-teEcFSuOaJjMwu3w@mail.gmail.com \
    --to=anton.botvalde@gmail.com \
    --cc=ptxdist@pengutronix.de \
    --cc=r.hieber@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox