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