From: Michael Wisse <mwisse@hs-harz.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] BSP for WAGO I/O-IPC
Date: Wed, 10 Jul 2013 09:46:57 +0200 [thread overview]
Message-ID: <e2938e5a3a7797d8.51dd2d91@hs-harz.de> (raw)
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
next reply other threads:[~2013-07-10 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 7:46 Michael Wisse [this message]
2013-07-10 20:00 ` Robert Schwebel
2013-07-10 13:50 Pascal K
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=e2938e5a3a7797d8.51dd2d91@hs-harz.de \
--to=mwisse@hs-harz.de \
--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