Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
QNX Operating System/Discussion/OSTech/ifs issue with M6 drop/List of Posts
Forum Topic - ifs issue with M6 drop: (6 Items)
   
Update
dave carlson(deleted)
04/10/2008 5:48 PM
post6651
ifs issue with M6 drop   
I built my first T2 system today.  I used exactly the "old" working ifs.bld.

I get:

Scanning flash at 0xC8040000 (1st 128KB sector)
Found image        @ 0xC8040000
Jumping to startup @ 0xC0031B80
Unable to access "/dev/ser1" (2)
Unable to access "/dev/fs0p0" (2)
Welcome to QNX 6.4.0
Unable to start "devc-pty" (2)

[+script] .script = {
    umask 0
    [pri=20] devc-serial -u1 -Fe 0x1000a000,20
    reopen /dev/ser1
    [pri=20] devf-nor -s0xc8040000,64m -R
    waitfor /dev/fs0p0
    display_msg Welcome to QNX 6.4.0
    [pri=20] devc-pty &
....

Are /dev device names or /proc/boot filesystem layouts changed in 6.4?

Is there a place to read about this?

Thanks

dave
Colin Burgess(deleted)
04/10/2008 8:53 PM
post6655
Re: ifs issue with M6 drop   
They haven't changed.  Rather it would appear that your drivers haven't registered
their devices by the time the waitfor times out.  What would cause that though
is unknown at this time.  Are the device drivers your own?

dave carlson wrote:
> 
> I built my first T2 system today.  I used exactly the "old" working 
> ifs.bld.
> 
> I get:
> 
> Scanning flash at 0xC8040000 (1st 128KB sector)
> Found image        @ 0xC8040000
> Jumping to startup @ 0xC0031B80
> Unable to access "/dev/ser1" (2)
> Unable to access "/dev/fs0p0" (2)
> Welcome to QNX 6.4.0
> Unable to start "devc-pty" (2)
> 
> [+script] .script = {
>     umask 0
>     [pri=20] devc-serial -u1 -Fe 0x1000a000,20
>     reopen /dev/ser1
>     [pri=20] devf-nor -s0xc8040000,64m -R
>     waitfor /dev/fs0p0
>     display_msg Welcome to QNX 6.4.0
>     [pri=20] devc-pty &
> ....
> 
> Are /dev device names or /proc/boot filesystem layouts changed in 6.4?
> 
> Is there a place to read about this?
> 
> Thanks
> 
> dave
> 
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post6651
> 

-- 
cburgess@qnx.com
dave carlson(deleted)
04/11/2008 7:35 AM
post6659
Re: ifs issue with M6 drop   
The drivers for devc and devf are minor bsp variants of the QNX drivers tailors for our addressing, etc.  No big diff.

I was hoping it was something "easy"...  :-)

dave
Colin Burgess(deleted)
04/11/2008 7:46 AM
post6661
RE: ifs issue with M6 drop   
Well,  given that devc-pty didn't work either it's probably not specific to
your drivers.  It must be something simple somewhere...
 
What BSP was it - I'll check to see if there were any gotchas...
 
Colin

  _____  

From: dave carlson [mailto:dcarls07@harris.com]
Sent: Fri 11/04/2008 7:35 AM
To: ostech-core_os
Subject: Re: ifs issue with M6 drop



The drivers for devc and devf are minor bsp variants of the QNX drivers
tailors for our addressing, etc.  No big diff. 

I was hoping it was something "easy"...  :-) 

dave 

_______________________________________________ 
OSTech 
http://community.qnx.com/sf/go/post6659
<http://community.qnx.com/sf/go/post6659>;
dave carlson(deleted)
04/11/2008 9:20 AM
post6669
Re: ifs issue with M6 drop   
It should be common mode "something".

I put the 6.3.2 OS in the same image: same failure.

I put 6.3.2 built devc and devf drivers: same failure.

I am trying to see if the issue with _mcount_ in libc is causing a runtime failure.

(Below is a -static linkage which did not error prior to the M6 install)
  LD        platform/bin/symbols/embed
libc.so: undefined reference to `_mcount_'

mcount.o is missing in both the libcS.a and libc.a so it would not surprise me that my runtime linkage is failing with 
no console (yet).

dave
Thomas Fletcher
04/11/2008 7:34 PM
post6700
Re: ifs issue with M6 drop   
On Thu, Apr 10, 2008 at 5:48 PM, dave carlson <dcarls07@harris.com> wrote:

>
> I built my first T2 system today.  I used exactly the "old" working
> ifs.bld.


Well to start, you should have a waitfor /dev/ser1 to ensure that you don't
continue until the serial driver name has registered its path .. then do the
re-open.

Thomas

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems