mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Pascal K <pascalkrauth@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] BSP for WAGO I/O-IPC
Date: Wed, 10 Jul 2013 15:50:12 +0200	[thread overview]
Message-ID: <CADj18OW6Lburtmi0RHKNx+WC9UfHja_YkwsJAeW9NOSgL8Yu3Q@mail.gmail.com> (raw)


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

The structure in my PTXdist BSP with PD12.1.1 is following:
/opt/Projectroot/configs
this holds the ptxconfig
inside
/opt/Projectroot/configs/hardwareBSP/
there is the platformconfig, kernelconfig, bareboxconfig and the patches if
any exist.

Simply backup the configs folder and if you changed some make, in files
backup the rules folder.
That is all I manually backup for my project.


Best regards,
Pascal


2013/7/10 Michael Wisse <mwisse@hs-harz.de>

> Hello,
>
> I try to use a preconfigured BSP  for a WAGO I/O-IPC with Geode-CPU, which
> is based on PTXdist 2011-03.1 .  The BSP was originally developed for an
> I/O-IPC with 128MB Flash and RAM. I have some older IPCs with 32MB Flash /
> RAM and try to adapt the BSP to this hardware.
>
>  I want to copy the actual ptxdist-project and reduce the size of
> partitions in the new project, e.g. remove the codesys runtime environment.
> I'm a ptxdist beginner and I'm confused with the project directory
> structure. I found some projects
>
>  ./ptxdist projects
> ptxdist: searching for projects:
> ptxdist: scanning /home/local/IPC-BSP-r0.3/ipc/ipc-dist/configs...
> ---------------------- Available PTXdist Projects:
> ----------------------------
> Wago-IO-IPC-P-Codesys
> Wago-IO-IPC-P-Codesys-Tele
> devkit-ti-am3517-wac3
> Wago-IO-IPC-Codesys
> devkit-ti-am3517-pac200
> Wago-IO-IPC-Codesys-Tele
>
> and clone one project:  ./ptxdist clone Wago-IO-IPC-Codesys
> Wago-IO-IPC-32MB
>
> Now I have a copy, not in
> .../ipc-dist/configs/Wago-IO-IPC-32MB/      as expected , but in
> .../ipc-dist/Wago-IO-IPC-32MB/.
>
> But if understood the manual, this is only the userland configuration and
> I still need a copy of the platform configuration
> .../ipc-dist/platform-IO-IPC-Codesys ?
> Because in this directory I will later find the images, I should have a
> copy of it, named e.g.
> .../ipc-dist/platform-IO-IPC-32MB.
>
> Why does a project only contain the userland configuration and not the
> platform configuration?
> Do I have to copy the platform configuration manually?
>
> thanks and regards
> Michael
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>

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

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

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2013-07-10 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 13:50 Pascal K [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-10  7:46 Michael Wisse
2013-07-10 20:00 ` Robert Schwebel

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=CADj18OW6Lburtmi0RHKNx+WC9UfHja_YkwsJAeW9NOSgL8Yu3Q@mail.gmail.com \
    --to=pascalkrauth@gmail.com \
    --cc=ptxdist@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