Freescale Total5200 QNX BSP for 6.3

QNX Newsgroups (Archives) qnx.bsp
1

I’m having problems flashing my Freescale Total5200.

The Total5200, is the MPC6XXX Total5200 V2 with Firmware v2d.2a.1a.
CPU is MPC5200 v1.2
Clocks: Core=396.00 MHz, SDRAM=132.00 MHz, IPBI=132.00 MHz,PCI=33.00 MHz
SDRAM: 00000000 - 07FFFFFF = 128 MBytes SDR
Flash: FC000000 - FFFFFFFF = 64 MBytes


Now this box came with a BSP from I believe Freescale that ran QNX
6.2.1. We purchased a the Freescale Total5200/Lite5200EVB BSP (ver.
1.0.x) (6.3.x) from QNX and are attempting to load this BSP on the
Total5200.

Now initially we tried just using the build file provided
(mgt5200.build) and using QNX Momentics build the ifs OS image and just
load that in. While it did work, obviously the first run doesn’t have
its problems. This build file seems to be setup as a minimal BSP load.
Not much on the system. But it is a plus that we have a system running.

Now this leads me to some questions for those of you with experience in
upgrading BSPs, whether this model the Total5200 or with another system
QNX supports.

We haven’t seemed to need to reflash the IPL, although one appears to be
provided with it. Should we go ahead and do that.

How does one go about making adding additional
drivers/executables/libraries to the image so that we have a more
functional system. Also since we have a limited system now, without df
and mount we seem to have no partitions just one image running. The old
system seemed to have mounted flash partitions with information on them.
It seems that there were flash partitions for everything from bin,
sbin, usr/lib and photon. How would one go about doing this with the
QNX BSP.


I realize this is alot of questions. But any help would greatly be
appreciated.

Ed


We would prefer to have the same functionality with the old system so we
would prefer to build a ifs and efs (I think they may be required).

2

Most of the time people have trouble with not being able toboot the minimal
image… Once you have it running, the rest is just a matter of reading docs
and doing your thing.

First step is you need to set up networking, so that you have access to
required files over network (NFS is the best way). You need to add network
driver, TCP stack and libsocket into the build template. Plus few useful
networking utils (ifconfig, route, netstat, ping, fs-nfs3, mount/umount).
Rebuild the image and start experimenting - just try to start up the
networking manually from shell prompt. Once you figure working combination,
put the commands into the boot script and let it run after the boot.

Now share QNX stuff from some Linux/Unix/Windows box (you need to run NFS
server). Mount it and you’re ready to set up the flash. Start the flash
driver and initialize it the way you want it. Then populate it with files.
You can do it in 2 ways - either prepare the entire flash image with mkefs
and then raw copy it into the flash partition, or just init the flash and
copy required files with cp/tar.

– igor

“Ed Berube” <eberube@gmail.com> wrote in message
news:ctu73r$ncu$1@inn.qnx.com…

I’m having problems flashing my Freescale Total5200.

The Total5200, is the MPC6XXX Total5200 V2 with Firmware v2d.2a.1a.
CPU is MPC5200 v1.2
Clocks: Core=396.00 MHz, SDRAM=132.00 MHz, IPBI=132.00 MHz,PCI=33.00 MHz
SDRAM: 00000000 - 07FFFFFF = 128 MBytes SDR
Flash: FC000000 - FFFFFFFF = 64 MBytes


Now this box came with a BSP from I believe Freescale that ran QNX 6.2.1.
We purchased a the Freescale Total5200/Lite5200EVB BSP (ver. 1.0.x)
(6.3.x) from QNX and are attempting to load this BSP on the Total5200.

Now initially we tried just using the build file provided (mgt5200.build)
and using QNX Momentics build the ifs OS image and just load that in.
While it did work, obviously the first run doesn’t have its problems.
This build file seems to be setup as a minimal BSP load. Not much on the
system. But it is a plus that we have a system running.

Now this leads me to some questions for those of you with experience in
upgrading BSPs, whether this model the Total5200 or with another system
QNX supports.

We haven’t seemed to need to reflash the IPL, although one appears to be
provided with it. Should we go ahead and do that.

How does one go about making adding additional
drivers/executables/libraries to the image so that we have a more
functional system. Also since we have a limited system now, without df
and mount we seem to have no partitions just one image running. The old
system seemed to have mounted flash partitions with information on them.
It seems that there were flash partitions for everything from bin, sbin,
usr/lib and photon. How would one go about doing this with the QNX BSP.


I realize this is alot of questions. But any help would greatly be
appreciated.

Ed


We would prefer to have the same functionality with the old system so we
would prefer to build a ifs and efs (I think they may be required).

3

Thank you, that provides alot of help. Now I have read some if not most
of the documents. And I laugh a bit, because my first attempt at
networking I somehow forgot to add the route binary. Easily fixed
problem.

However on a not as easily fixed problem, I did notice that inside the
BSP that QNX provides, it asks to put in flashctl and devf-mgt5200 -
which are two things that Momentics cannot seem to find when it tries to
build the image. And I did a search of the Momentics workspaces and I
couldn’t find them. Does anyone know where about those files might be
found?

Igor Kovalenko wrote:

Most of the time people have trouble with not being able toboot the minimal
image… Once you have it running, the rest is just a matter of reading docs
and doing your thing.

First step is you need to set up networking, so that you have access to
required files over network (NFS is the best way). You need to add network
driver, TCP stack and libsocket into the build template. Plus few useful
networking utils (ifconfig, route, netstat, ping, fs-nfs3, mount/umount).
Rebuild the image and start experimenting - just try to start up the
networking manually from shell prompt. Once you figure working combination,
put the commands into the boot script and let it run after the boot.

Now share QNX stuff from some Linux/Unix/Windows box (you need to run NFS
server). Mount it and you’re ready to set up the flash. Start the flash
driver and initialize it the way you want it. Then populate it with files.
You can do it in 2 ways - either prepare the entire flash image with mkefs
and then raw copy it into the flash partition, or just init the flash and
copy required files with cp/tar.

– igor

“Ed Berube” <> eberube@gmail.com> > wrote in message
news:ctu73r$ncu$> 1@inn.qnx.com> …

I’m having problems flashing my Freescale Total5200.

The Total5200, is the MPC6XXX Total5200 V2 with Firmware v2d.2a.1a.
CPU is MPC5200 v1.2
Clocks: Core=396.00 MHz, SDRAM=132.00 MHz, IPBI=132.00 MHz,PCI=33.00 MHz
SDRAM: 00000000 - 07FFFFFF = 128 MBytes SDR
Flash: FC000000 - FFFFFFFF = 64 MBytes


Now this box came with a BSP from I believe Freescale that ran QNX 6.2.1.
We purchased a the Freescale Total5200/Lite5200EVB BSP (ver. 1.0.x)
(6.3.x) from QNX and are attempting to load this BSP on the Total5200.

Now initially we tried just using the build file provided (mgt5200.build)
and using QNX Momentics build the ifs OS image and just load that in.
While it did work, obviously the first run doesn’t have its problems.
This build file seems to be setup as a minimal BSP load. Not much on the
system. But it is a plus that we have a system running.

Now this leads me to some questions for those of you with experience in
upgrading BSPs, whether this model the Total5200 or with another system
QNX supports.

We haven’t seemed to need to reflash the IPL, although one appears to be
provided with it. Should we go ahead and do that.

How does one go about making adding additional
drivers/executables/libraries to the image so that we have a more
functional system. Also since we have a limited system now, without df
and mount we seem to have no partitions just one image running. The old
system seemed to have mounted flash partitions with information on them.
It seems that there were flash partitions for everything from bin, sbin,
usr/lib and photon. How would one go about doing this with the QNX BSP.


I realize this is alot of questions. But any help would greatly be
appreciated.

Ed


We would prefer to have the same functionality with the old system so we
would prefer to build a ifs and efs (I think they may be required).

4

Ed,

You need to get the Flash Filesystem and Embedding TDK in order to get those binaries on your host system.

-Jay.

Ed Berube wrote:

Thank you, that provides alot of help. Now I have read some if not most
of the documents. And I laugh a bit, because my first attempt at
networking I somehow forgot to add the route binary. Easily fixed problem.

However on a not as easily fixed problem, I did notice that inside the
BSP that QNX provides, it asks to put in flashctl and devf-mgt5200 -
which are two things that Momentics cannot seem to find when it tries to
build the image. And I did a search of the Momentics workspaces and I
couldn’t find them. Does anyone know where about those files might be
found?

Igor Kovalenko wrote:

Most of the time people have trouble with not being able toboot the
minimal image… Once you have it running, the rest is just a matter
of reading docs and doing your thing.

First step is you need to set up networking, so that you have access
to required files over network (NFS is the best way). You need to add
network driver, TCP stack and libsocket into the build template. Plus
few useful networking utils (ifconfig, route, netstat, ping, fs-nfs3,
mount/umount). Rebuild the image and start experimenting - just try to
start up the networking manually from shell prompt. Once you figure
working combination, put the commands into the boot script and let it
run after the boot.

Now share QNX stuff from some Linux/Unix/Windows box (you need to run
NFS server). Mount it and you’re ready to set up the flash. Start the
flash driver and initialize it the way you want it. Then populate it
with files. You can do it in 2 ways - either prepare the entire flash
image with mkefs and then raw copy it into the flash partition, or
just init the flash and copy required files with cp/tar.

– igor

“Ed Berube” <> eberube@gmail.com> > wrote in message
news:ctu73r$ncu$> 1@inn.qnx.com> …

I’m having problems flashing my Freescale Total5200.

The Total5200, is the MPC6XXX Total5200 V2 with Firmware v2d.2a.1a.
CPU is MPC5200 v1.2
Clocks: Core=396.00 MHz, SDRAM=132.00 MHz, IPBI=132.00 MHz,PCI=33.00 MHz
SDRAM: 00000000 - 07FFFFFF = 128 MBytes SDR
Flash: FC000000 - FFFFFFFF = 64 MBytes


Now this box came with a BSP from I believe Freescale that ran QNX
6.2.1. We purchased a the Freescale Total5200/Lite5200EVB BSP (ver.
1.0.x) (6.3.x) from QNX and are attempting to load this BSP on the
Total5200.

Now initially we tried just using the build file provided
(mgt5200.build) and using QNX Momentics build the ifs OS image and
just load that in. While it did work, obviously the first run doesn’t
have its problems. This build file seems to be setup as a minimal BSP
load. Not much on the system. But it is a plus that we have a system
running.

Now this leads me to some questions for those of you with experience
in upgrading BSPs, whether this model the Total5200 or with another
system QNX supports.

We haven’t seemed to need to reflash the IPL, although one appears to
be provided with it. Should we go ahead and do that.

How does one go about making adding additional
drivers/executables/libraries to the image so that we have a more
functional system. Also since we have a limited system now, without
df and mount we seem to have no partitions just one image running.
The old system seemed to have mounted flash partitions with
information on them. It seems that there were flash partitions for
everything from bin, sbin, usr/lib and photon. How would one go
about doing this with the QNX BSP.


I realize this is alot of questions. But any help would greatly be
appreciated.

Ed


We would prefer to have the same functionality with the old system so
we would prefer to build a ifs and efs (I think they may be required).
\

5

In 6.2.1 flashctl was standard component and BSP-specific drivers were part
of BSP. But alas, no more buffet.

“Jay Greig” <greig@qnx.com> wrote in message
news:cu0p2p$m80$1@inn.qnx.com…

Ed,

You need to get the Flash Filesystem and Embedding TDK in order to get
those binaries on your host system.

-Jay.

Ed Berube wrote:
Thank you, that provides alot of help. Now I have read some if not most
of the documents. And I laugh a bit, because my first attempt at
networking I somehow forgot to add the route binary. Easily fixed
problem.

However on a not as easily fixed problem, I did notice that inside the
BSP that QNX provides, it asks to put in flashctl and devf-mgt5200 -
which are two things that Momentics cannot seem to find when it tries to
build the image. And I did a search of the Momentics workspaces and I
couldn’t find them. Does anyone know where about those files might be
found?

Igor Kovalenko wrote:

Most of the time people have trouble with not being able toboot the
minimal image… Once you have it running, the rest is just a matter of
reading docs and doing your thing.

First step is you need to set up networking, so that you have access to
required files over network (NFS is the best way). You need to add
network driver, TCP stack and libsocket into the build template. Plus
few useful networking utils (ifconfig, route, netstat, ping, fs-nfs3,
mount/umount). Rebuild the image and start experimenting - just try to
start up the networking manually from shell prompt. Once you figure
working combination, put the commands into the boot script and let it
run after the boot.

Now share QNX stuff from some Linux/Unix/Windows box (you need to run
NFS server). Mount it and you’re ready to set up the flash. Start the
flash driver and initialize it the way you want it. Then populate it
with files. You can do it in 2 ways - either prepare the entire flash
image with mkefs and then raw copy it into the flash partition, or just
init the flash and copy required files with cp/tar.

– igor

“Ed Berube” <> eberube@gmail.com> > wrote in message
news:ctu73r$ncu$> 1@inn.qnx.com> …

I’m having problems flashing my Freescale Total5200.

The Total5200, is the MPC6XXX Total5200 V2 with Firmware v2d.2a.1a.
CPU is MPC5200 v1.2
Clocks: Core=396.00 MHz, SDRAM=132.00 MHz, IPBI=132.00 MHz,PCI=33.00
MHz
SDRAM: 00000000 - 07FFFFFF = 128 MBytes SDR
Flash: FC000000 - FFFFFFFF = 64 MBytes


Now this box came with a BSP from I believe Freescale that ran QNX
6.2.1. We purchased a the Freescale Total5200/Lite5200EVB BSP (ver.
1.0.x) (6.3.x) from QNX and are attempting to load this BSP on the
Total5200.

Now initially we tried just using the build file provided
(mgt5200.build) and using QNX Momentics build the ifs OS image and just
load that in. While it did work, obviously the first run doesn’t have
its problems. This build file seems to be setup as a minimal BSP load.
Not much on the system. But it is a plus that we have a system
running.

Now this leads me to some questions for those of you with experience in
upgrading BSPs, whether this model the Total5200 or with another system
QNX supports.

We haven’t seemed to need to reflash the IPL, although one appears to
be provided with it. Should we go ahead and do that.

How does one go about making adding additional
drivers/executables/libraries to the image so that we have a more
functional system. Also since we have a limited system now, without df
and mount we seem to have no partitions just one image running. The
old system seemed to have mounted flash partitions with information on
them. It seems that there were flash partitions for everything from
bin, sbin, usr/lib and photon. How would one go about doing this with
the QNX BSP.


I realize this is alot of questions. But any help would greatly be
appreciated.

Ed


We would prefer to have the same functionality with the old system so
we would prefer to build a ifs and efs (I think they may be required).
\