Trying to add ethernet to the PXA270 BSP build

QNX Momentics IDE 6.3 with SP1. Host: PC running QNX. Target:
Intel PXA270 Development system

As imported there are a number of projects in this BSP, but only
one of them: devc-serpxa250 is included in the original image.

I’d like to add more stuff from the BSP to the image and to start
out I want to add ethernet. Here is what I do:

Using devc-serpxa250 as an example,

I see that the absolute path is:

WORKSPACE/bsp-intel-dbpxa270dp_dev-serpxa250/serpxa250/arm/le/devc-serpxa250

So for the ethernet it would make sense to have a path of:

WORKSPACE/bsp-intel-dbpxa270dp_devn-smc9000/smc9000/arm/dll.le/devn-smc9000.so

But adding this file to the image is not straightforward and not
consistent with devc-serpxa250:

  1. devn-smc9000.so does not show up in the search paths (nor do
    any of the other files from the BSP).

  2. Navigating to the file directly I get a path without the
    ‘WORKSPACE’ prefix:

/home/workspace/bsp-intel-dbpxa270dp_devn-smc9000/smc9000/arm/dll.le/devn-smc9000.so

I must be doing something wrong. What is the cannonical way to
add ethernet and other stuff from the bsp into the image?

Thanks,

Robert

Robert Whaley wrote:

QNX Momentics IDE 6.3 with SP1. Host: PC running QNX. Target: Intel
PXA270 Development system

As imported there are a number of projects in this BSP, but only one of
them: devc-serpxa250 is included in the original image.

I’d like to add more stuff from the BSP to the image and to start out I
want to add ethernet. Here is what I do:

Using devc-serpxa250 as an example,

I see that the absolute path is:

WORKSPACE/bsp-intel-dbpxa270dp_dev-serpxa250/serpxa250/arm/le/devc-serpxa250


So for the ethernet it would make sense to have a path of:

WORKSPACE/bsp-intel-dbpxa270dp_devn-smc9000/smc9000/arm/dll.le/devn-smc9000.so


But adding this file to the image is not straightforward and not
consistent with devc-serpxa250:

  1. devn-smc9000.so does not show up in the search paths (nor do any of
    the other files from the BSP).

  2. Navigating to the file directly I get a path without the ‘WORKSPACE’
    prefix:

/home/workspace/bsp-intel-dbpxa270dp_devn-smc9000/smc9000/arm/dll.le/devn-smc9000.so


I must be doing something wrong. What is the cannonical way to add
ethernet and other stuff from the bsp into the image?

Thanks,

Robert

Well, I haven’t had much success with using non-absolute paths.
I think the only other alternative to absolute paths is probably
to add each project individually to the list of paths. (But that
doesn’t explain how the serial driver was setup with it’s
non-absolute path).

I was successful getting the ethenet driver into the image and
making it work. However, I had to add it and libraries to the
build manually (Optimize System did not work for the dlls or
libraries). Also, the added stuff would not actually appear in
the image after a build unless I would exit the IDE and restart
the IDE – only then would the new stuff show up in the image!

My impression so far is that BSPs are best maintained via the
command line stuff rather than the IDE.

“Robert Whaley” <rwhaley@applieddata.net> wrote in message
news:dkaphn$bjc$1@inn.qnx.com

Robert Whaley wrote:
[…]

I was successful getting the ethenet driver into the image and
making it work. However, I had to add it and libraries to the
build manually (Optimize System did not work for the dlls or
libraries). Also, the added stuff would not actually appear in
the image after a build unless I would exit the IDE and restart
the IDE – only then would the new stuff show up in the image!

I had the same problem with binaries not appearing in the pxa270 image. In
my case it was user error. I would add the binary using the system builder,
then build the project, then try it out and the new binaries were missing.
My mistake? Stupid me, I didn’t SAVE the project before building. Haven’t
had the problem since.

My impression so far is that BSPs are best maintained via the
command line stuff rather than the IDE.

I’m having some bumps in the road trying to adapt to the IDE. Been using QNX
on the command line for >20 years, so it’s been hard for me to adapt.