SandPoint with 8245

[Alex Ivchenko]

John,

thank you very much for your help!

It was much easier to put MontaVista Linux on Sandpoint, at list documentation was OK.
I didn't expect that QNX docs ain't so good.

need to remove the "ÿimage_download_8250" from main.c, and modify
the scanning routines (image_scan) to scan for the OS in flash.
Thanks, I found it and correct code.

Question: when I recompile
C:\qnxsdk\QNXsdk\target\qnx6\usr\src\bsp-6.1.0\ppc\sandpoint\src\hardware\ipl\boards\sandpoint\makefile

compiler couldn't find ipl.h. OK, there is no such a file in Windows CDK.
I copied it from QNX

However:
there is no definition of:
init_icache();
in ipl.h and ipl.h is the only header included into main.c
is it "void init_icache(void)"?

Also makefile has library ipl.lib included (-lipl)
I couldn't find that library anywhere.

As far as burning the flash is concerned, we've simply pop off
the 512K part and used a flash burner to put a Neutrino image on the flash.
I have to put QNX into PMC Flash, and it's in SMT package.

Thus, fu -l -o ...


--
Regards,
Alex

--
Alex Ivchenko, Ph.D.
United Electronic Industries, Inc.
"The High-Performance Alternative (tm)"
--
611 Neponset Street
Canton, MA 02021
Tel:(781)821-2890 x222 Fax:(781)821-2891
http://www.ueidaq.com

[John Wall]

Alex Ivchenko <aivchenko@ueidaq.com> wrote:
: John,

: thank you very much for your help!

: It was much easier to put MontaVista Linux on Sandpoint, at list documentation was OK.
: I didn't expect that QNX docs ain't so good.


Hi Alex,

I was wondering whether you could expand on this. We're looking for
any feedback concerning the BSP docs. Did you expect a more "step
by step" approach to putting the image in flash? Our approach has
been to make the instructions "step by step" to boot the OS via
the monitor but to let the customer decide how things are configured
otherwise. We try to generically describe the IPL in the "Building
Embedded Systems" and hope that with the code the user can move
forward. I welcome your suggestions.


:>> need to remove the "ÿimage_download_8250" from main.c, and modify
:> the scanning routines (image_scan) to scan for the OS in flash.
: Thanks, I found it and correct code.

: Question: when I recompile
: C:\qnxsdk\QNXsdk\target\qnx6\usr\src\bsp-6.1.0\ppc\sandpoint\src\hardware\ipl\boards\sandpoint\makefile

: compiler couldn't find ipl.h. OK, there is no such a file in Windows CDK.
: I copied it from QNX

I'm not familiar with the Windows version of the tools, but I believe
you need to do a "make" from the ..\bsp-6.1.0\ppc\sandpoint directory
first.ÿ This will make sure everything is correctly setup. Once
this is done you can go the individual components (as above) and
type "make install" to rebuild the component and install it to the correct
location. I believe there was a seperate release note to this
affect.

Hope this helps.

--
John

[Alex Ivchenko]

John,

: It was much easier to put MontaVista Linux on Sandpoint, at list documentation was OK.
: I didn't expect that QNX docs ain't so good.

Majority of information is already in BSP docs. However It's hard to start working with
it from the scratch.

I would suggest to structure documents like:
1. Getting Started manual:
where to look for what,
description of files in BSP tree,
how to recompile parts of the project
how to customize image (and links to existing manuals)
2. Sandpoint-specific manual
how to download program and write to the flash
what are installation options (download, flash, hdd, ...)

by step" approach to putting the image in flash? Our approach has
been to make the instructions "step by step" to boot the OS via
the monitor but to let the customer decide how things are configured
otherwise. We try to generically describe the IPL in the "Building
Embedded Systems" and hope that with the code the user can move

Step-by-step approach is not so bad and quite useful.
I think you need to add overview into documents, some kind of short tutorial
explaining different options.

Again, majority of information is there, just make it easier to use.
For example, instead of giving link to the whole System Architecture document
give a link to the particular chapter where related things are discussed.

--
Regards,
Alex

--
Alex Ivchenko, Ph.D.
United Electronic Industries, Inc.
"The High-Performance Alternative (tm)"
--
611 Neponset Street
Canton, MA 02021
Tel:(781)821-2890 x222 Fax:(781)821-2891
http://www.ueidaq.com

[John Wall]

Alex Ivchenko <aivchenko@ueidaq.com> wrote:
: John,


:> : It was much easier to put MontaVista Linux on Sandpoint, at list documentation was OK.
:> : I didn't expect that QNX docs ain't so good.

: Majority of information is already in BSP docs. However It's hard to start working with
: it from the scratch.

: I would suggest to structure documents like:
: 1. Getting Started manual:
: where to look for what,
: description of files in BSP tree,
: how to recompile parts of the project
: how to customize image (and links to existing manuals)
: 2. Sandpoint-specific manual
: how to download program and write to the flash
: what are installation options (download, flash, hdd, ...)

:> by step" approach to putting the image in flash? Our approach has
:> been to make the instructions "step by step" to boot the OS via
:> the monitor but to let the customer decide how things are configured
:> otherwise. We try to generically describe the IPL in the "Building
:> Embedded Systems" and hope that with the code the user can move

: Step-by-step approach is not so bad and quite useful.
: I think you need to add overview into documents, some kind of short tutorial
: explaining different options.

: Again, majority of information is there, just make it easier to use.
: For example, instead of giving link to the whole System Architecture document
: give a link to the particular chapter where related things are discussed.


Thank you Alex ... I will pass this information to our docs
people.

--
John

[Alex Ivchenko]

John,

As far as I understood to rebuild startup-sandpoint (to support 8245 and switch completely to
57600) I need pre-built libstartup.a

Am I right?

--
Regards,
Alex

--
Alex Ivchenko, Ph.D.
United Electronic Industries, Inc.
"The High-Performance Alternative (tm)"
--
611 Neponset Street
Canton, MA 02021
Tel:(781)821-2890 x222 Fax:(781)821-2891
http://www.ueidaq.com

[John Wall]

Alex Ivchenko <aivchenko@ueidaq.com> wrote:
: John,

: As far as I understood to rebuild startup-sandpoint (to support 8245 and switch completely to
: 57600) I need pre-built libstartup.a

: Am I right?

I'm not sure I completely understand the question ... Yes, the startup
lib you have (from the BSP) does not support the 8245. No, the startup
lib is not required to change the baud to 57600. You can simply pass
a command line option to startup-sandpoint, as follows:


startup-sandpoint -D8250.0xfe0003f8.57600.1846200.16 -vvvv


Let me know if this is what you meant.

--
John

[Alex Ivchenko]

John,

startup-sandpoint -D8250.0xfe0003f8.57600.1846200.16 -vvvv
Thanks, this works.

--
Regards,
Alex

--
Alex Ivchenko, Ph.D.
United Electronic Industries, Inc.
"The High-Performance Alternative (tm)"
--
611 Neponset Street
Canton, MA 02021
Tel:(781)821-2890 x222 Fax:(781)821-2891
http://www.ueidaq.com