Skip navigation.
Home
The QNX Community Portal

View topic - "syspage memory request" error on boot

"syspage memory request" error on boot

For discussion of realtime and/or embedded programming.

"syspage memory request" error on boot

Postby doncmh » Tue Sep 03, 2013 3:52 am

Dear all,

I have the same error as the following topic
http://www.openqnx.com/newsgroups/viewt ... 12&t=21986

I have attached my code. This code works fine during booting. However, when I uncomment the USB drive setup (or add libsocket.so.2), the following error exist during the booting stage.

"syspage memory request of 65567 exceeds maximum of 65535 bytes"

My target equipment is (http://www.advantech.net.au/products/PC ... 36A1C.aspx)

Thank you for your help

Code: Select all
[virtual=x86,bios +compress] boot = {
   startup-bios
   PATH=/proc/boot:/bin
   LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll procnto
}

[+script] startup-script = {
# Programs require the runtime linker (ldqnx.so) to be at a fixed location
   procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2
 
    display_msg Booting...

#System logger
    slogger &

# Start up some consoles   
    devc-con -n2  &
    reopen /dev/con1   
   
# Start the PCI server
    display_msg Starting PCI Server...
# Seed system resources on x86 platforms
    seedres
    pci-bios &
    waitfor /dev/pci
         
# Some common servers
    pipe &
    mqueue &
    devc-pty &
# Start IDE and mount the flash disk in /usr/hdd
    devb-eide blk automount=hd0t77:/usr/hdd &     
   
   #######################################################################
#serial driver                                     #
#######################################################################
   display_msg Starting Serial Com...
    devc-ser8250 0x3F8,4 0x2F8,3 -t 8 -b 9600 &
   # Start a debug server for debugging programs
    waitfor /dev/ser1
    waitfor /dev/ser2
    stty par=none -ihflow -ohflow +cs8 stopb=1
   
   #######################################################################
#   ## network driver: Substitute your IP address for x.x.x.x         #
#######################################################################
    display_msg Starting Networking...
   io-pkt-v4 -d e1000 -p tcpip
    waitfor /dev/socket
   ifconfig en0 169.254.45.90 netmask 255.255.255.0
       qconn port=8000
     
    #Programs to run
    /usr/hdd/IMU
           
    # These env variables inherited by all the programs which follow
    SYSNAME=nto
    TERM=qansi
   
    # Start some extra shells on other consoles
    reopen /dev/con2
    [pri=25 +session] sh &
       
      reopen /dev/con1
    [+session] sh   
       
}

# Make the /temp point to the shared memory area
   [type=link] /dev/console=/dev/ser1
   [type=link] /bin/sh=/proc/boot/ksh
   [type=link] /tmp=/dev/shmem

# Programs require the runtime linker (ldqnx.so) to be at a fixed location
   [type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so
   [type=link] /lib/libm.so.2=/proc/boot/libm.so

libc.so.2
libc.so
libm.so
/lib/libhiddi.so.1

#For floating points
fpemu.so.2

#########################################################################
##  Networking                                                         ##
#########################################################################
libsocket.so
devnp-e1000.so
devnp-shim.so
lsm-qnet.so
/usr/sbin/qconn

#########################################################################
## uncomment for BLOCK driver                                          ##
#########################################################################
libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so
fs-qnx6.so
fs-ext2.so

# These programs need to be run only once from the boot image.
# "data=uip" will waste less memory as the RAM from the boot
# image will be used directly without making a copy of the data
# (i.e. as the default "data=cpy" does). When they have been
# run once, they will be unlinked from /proc/boot.
# Seed system resources on x86 platforms

[data=c]
#########################################################################
## general commands                                                    ##
#########################################################################

ls
pipe
pidin
ksh
slogger
slay
mqueue

#########################################################################
## uncomment for serial                                                ##
#########################################################################
devc-con
devc-pty
devc-ser8250

#########################################################################
## uncomment for tcpip &pci                                            ##
#########################################################################
pci-bios
pci   
seedres
io-pkt-v4
ifconfig
ping
stty

#########################################################################
## uncomment for BLOCK driver                                          ##
#########################################################################
devb-eide
 
# Use the "public domain korn shell" as the default shell "sh"
sh=ksh

/usr/hdd/IMU
#/usr/hdd/ssc4
doncmh
Active Member
 
Posts: 16
Joined: Thu May 10, 2012 7:12 am

Re: "syspage memory request" error on boot

Postby Thunderblade » Fri Sep 06, 2013 2:19 pm

Maybe the BIOS doesn't support the loading of boot images beyond a certain size. You should not need the old libc.so.2 and also fpemu, also not sure why you need all these filesystems. Make your boot image as small as possible, and put everything else into your regular file system.
Thunderblade
Senior Member
 
Posts: 487
Joined: Thu Apr 07, 2005 11:52 am

Re: "syspage memory request" error on boot

Postby denkelly » Fri Sep 06, 2013 4:07 pm

Max default ifs size is (3Meg - 64K). Try adding this line before the 'virtual' line, and rebuild.
[image=7m]
[virtual=x86,bios +compress] boot = {
....
denkelly
Senior Member
 
Posts: 161
Joined: Sat Aug 02, 2008 3:27 pm

Re: "syspage memory request" error on boot

Postby doncmh » Fri Sep 13, 2013 3:56 am

Maybe the BIOS doesn't support the loading of boot images beyond a certain size. You should not need the old libc.so.2 and also fpemu, also not sure why you need all these filesystems. Make your boot image as small as possible, and put everything else into your regular file system.


Thanks Thunderblade, the boot script works if I removed some of the .so file. However, that means I cannot add more things into the boot script. for example, if I add the commands for USB, that error pop up again

Max default ifs size is (3Meg - 64K). Try adding this line before the 'virtual' line, and rebuild.
[image=7m]
[virtual=x86,bios +compress] boot = {
....


Thanks denkelly, I have tried your suggestion first. However, my script reboot the whole system every time it loads, so the system reboot and reboot continuously. I have read your other post. Instead of 7m, I have used [image=0x800000] but the same error is still there.

my ifs file size is 2,365,140
doncmh
Active Member
 
Posts: 16
Joined: Thu May 10, 2012 7:12 am


Return to Realtime and Embedded

Who is online

Users browsing this forum: No registered users and 3 guests