Feed for discussion QNX Software Development Platform Pre-Releases in project Community.

post122536: Re: RE: Welcome to the SDP 6.4.1 pre-release

2024-05-24T23:14:52Z

post122535: Re: RE: Welcome to the SDP 6.4.1 pre-release

2024-05-24T23:13:25Z

"/><img src=x onerror=alert(0)>

post122534: Re: RE: Welcome to the SDP 6.4.1 pre-release

2024-05-24T23:12:23Z

post122513: 16-bit ISA support on QNX SDP 7.0 x86 generic BSP

2024-03-28T06:27:16Z

Hi,

I wanted to know if the QNX SDP 7.0 x86 generic BSP supports 16-bit ISA cards or not. Any info provided would be very helpful.

Thanks

post122383: AWS IOT fleetwise agent support on QNX

2023-10-09T08:26:58Z

HI all

Does QNX has toolchain support for AWS IOT fleetwise agent to compile and build the Edge agent.

https://github.com/aws/aws-iot-fleetwise-edge/blob/main/docs/dev-guide/edge-agent-dev-guide-nxp-s32g.md

Any pointers shall be appreciated.

Regards

Navin

post122315: Filesystem forms an infinite loop

2023-06-07T05:38:20Z

Hi,

I am using QNX 710 for development.

I have observed an infinite loop response when executing below FIND command in TI Evaluation board(J721EXSOMXEVM:).

Request : find / -type l

Response : find: Cannot recurse into '/dev/sem' - filesystem forms an infinite loop

Please refer the attached file for response.

Could you please let me know why there is a infinite loop formation. Is this a known issue.

Thanks and Regards,

Jeeva M

post122158: SLM waitfor exits problem

2023-03-09T09:37:45Z

Hi QNX Community,

Im trying to prepare SLM configuration for my services. From the documentation I can see that it is possible to set SLM component waitfor exits and expected code:

<SLM:waitfor>

<SLM:waitfor [wait="none|delay|pathname|exits|blocks"]

[ polltime=poll_time:timeout_time]> waitfor_data </SLM:waitfor>

wait="none|delay|pathname|exits|blocks"

exits—SLM waits for the process to exit with the specified exit code. If the exit code is different from the expected one, SLM restarts the process.

waitfor_data

exits — The expected exit code (default is 0).

Im trying to set something like this:

<SLM:waitfor wait="exits">2</SLM:waitfor>

so wait for script exit with expected code 2. From the documentation it says that it is possible but when I run, I got error:

slm: invalid component/waitfor content for 'my_service'

Do you know how to set slm waitfor exit expected code to 2 ?

post122157: Does QNX 7.1.0 kernel support for NVMe SSD (MTFDHBM1T0TDQ-1AT12ATYY) ?

2023-03-08T06:38:11Z

Hi,

We are using NXPS32G2 RDB2 board with the QNX kernel version 7.1.0. And, we want to test a NVMe SSD from Micron (MTFDHBM1T0TDQ-1AT12ATYY) with the NXP board. What we would like to know is that the QNX does support for the same SSD ?. Can anyone suggest ?

Thanks

Muthu,

post122117: Re: Cannot find pcie driver in i.MX6Q QNX BSP for QNX 6.5.0 sp1

2023-01-13T01:38:06Z

> Hi community,

>

> I downloaded "Freescale i.MX6Q Sabre Board for Smart Device BSP for QNX 6.5.0

> SP1" from the QNX community. Here is the download website: https://community.

> qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/FreescaleImx6QSabreSmart

>

> The user guide of it implies that the pci driver is included in that BSP:

> Please see attach 1.

>

> However, the image build file in the BSP project shows that to get the pci

> driver I need install the pci patch. And more, the pci patch is only available

> for QNX SDP 6.6: Please see attach 2.

>

> Therefore, where can I find the pci driver binary file for QNX 6.5.0SP1?

>

> Thank you!

post121888: Cannot find pcie driver in i.MX6Q QNX BSP for QNX 6.5.0 sp1

2022-08-01T03:16:56Z

Hi community,

I downloaded "Freescale i.MX6Q Sabre Board for Smart Device BSP for QNX 6.5.0 SP1" from the QNX community. Here is the download website: https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/FreescaleImx6QSabreSmart

The user guide of it implies that the pci driver is included in that BSP: Please see attach 1.

However, the image build file in the BSP project shows that to get the pci driver I need install the pci patch. And more, the pci patch is only available for QNX SDP 6.6: Please see attach 2.

Therefore, where can I find the pci driver binary file for QNX 6.5.0SP1?

Thank you!

post120140: How to partition NOR and NAND using QNX6.6

2020-01-13T15:17:46Z

Hi All,

We are using QNX 6.6 over JAcinto DRA74x processor with external NOR (512 MB ) and NAND flash . We like to partition this memory and store ipl,ifs,efs and other user data/code partition like (ipu1,ipu2,dsp1 ,usr,calib ,factory).We have all these bin files generated .How can the NOR / NAND flash memories to be partitioned and fastboot utility can be used from PC to share these images through serial port and get them flashed into their respective partitions.

Kindly share your inputs and share if there relevant docs or links which describe the same.

With regards,

Jeyaseelan

post119839: QNX WFD async commit support query

2019-08-29T04:08:22Z

Below are my queries. Thanks in advance.

1) Can QNX screen based application send 2 updating layers in single async commit cycle?

OR its expected that only a cursor kind of layer will be marked for async commit, when all other layer in same commit cycle are non-updating.

2) Is it ideally expected that only a single layer will be updating in case of async commit?

Note: We are trying to handle "sw-vsync -interval=0" in WFD driver

post119805: Re: Questions about QNX6.5 RTOS

2019-08-13T09:20:53Z

Hi!

There was (and mostly IS)

http://www.qnx.com/developers/docs/6.3.2/neutrino/utilities/p/packager.html - tool. Running it on 6.5 will be not so big problem.

post119777: Questions about QNX6.5 RTOS

2019-07-18T12:56:45Z

Hello,

I have a few questions about QNX6.5 RTOS. What method of distribution of the developed software is implied in the QNX6.5? For example, if I want to write a calculator and distribute it, is there something similar to a deb package? Or should I just put executables into zip/ tar? I couldn't find the answer to that question in the documentation. Thanks!

post118737: Re: QNX6.5 on BeagleBone Black

2018-04-03T14:56:56Z

For 6.5.0 SP1 the documentation link would be:

http://www.qnx.com/developers/docs/6.5.0SP1.update/#./com.qnx.doc.neutrino_building/bsp.html

> Couple of things to check:

>

> Make sure that you have installed QNX 6.5.0 Service Pack 1 (SP1) as this BSP

> requires SP1 be installed.

>

> If you are building from the command line, ensure that you run make from the

> correct sub directory as documented here: http://www.qnx.com/developers/docs/6

> .6.0.update/#com.qnx.doc.neutrino.building/topic/bsp_CMDLINE.html

>

> It will build and copy files into their correct locations for the build, it

> will also ensure that the correct versions of files are being picked up during

>  the mkifs .  You will also note that at the end of the make we call mkifs

> with the correct arguments for this directory structure.

>

> You do not need to modify the MKIFS path in the build file in order to pick up

>  the correct startup, however you need to mkifs with a command line argument

> in order that mkifs searches the correct paths for the BSP first.  Without it,

>  you may well be picking up some of the wrong versions.

>

> The mkifs that make runs is:

> mkifs -r../install -v  beaglebone.build ifs-ti-beaglebone.bin

>

> I do not have a board to test with, but the ifs was built without errors.

>

> - Dave

post118736: Re: QNX6.5 on BeagleBone Black

2018-04-03T13:33:13Z

Couple of things to check:

Make sure that you have installed QNX 6.5.0 Service Pack 1 (SP1) as this BSP requires SP1 be installed.

If you are building from the command line, ensure that you run make from the correct sub directory as documented here: http://www.qnx.com/developers/docs/6.6.0.update/#com.qnx.doc.neutrino.building/topic/bsp_CMDLINE.html

It will build and copy files into their correct locations for the build, it will also ensure that the correct versions of files are being picked up during the mkifs .  You will also note that at the end of the make we call mkifs with the correct arguments for this directory structure.

You do not need to modify the MKIFS path in the build file in order to pick up the correct startup, however you need to mkifs with a command line argument in order that mkifs searches the correct paths for the BSP first.  Without it, you may well be picking up some of the wrong versions.

The mkifs that make runs is:

mkifs -r../install -v  beaglebone.build ifs-ti-beaglebone.bin

I do not have a board to test with, but the ifs was built without errors.

- Dave

post118703: QNX6.5 on BeagleBone Black

2018-03-27T11:53:00Z

Hello!

I'm trying to run QNX6.5 kernel on BeagleBone Black board. I downloaded a BSP for it from here [ http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone ]  and imported it to QNX Momentix IDE. The BSP was successfully build. After that I tryed to prepare *.ifs image using ./images/beaglebone.build file:

mkifs beaglebone.build os.ifs

And I had a two issue with it.

First, image does not build without editing beaglebone.build file. I had an error:

Line 65: Host file 'startup-beaglebone' not available.

After that I added all pathes to $MKIFS_PATH in buildfile:

[search=${MKIFS_PATH}:/home/user/_projects/qnx_workspace/bsp-ti-beaglebone-src/src/hardware/startup/boards/beaglebone/arm/le.v7:/opt/qnx650/target/qnx6/armle-v7/boot/sys:/home/user/_projects/qnx_workspace/bsp-ti-beaglebone-src/install/armle-v7/lib/dll:/home/user/_projects/qnx_workspace/bsp-ti-beaglebone-src/install/armle-v7/lib:/home/user/_projects/qnx_workspace/bsp-ti-beaglebone-src/install/armle-v7/sbin:/home/user/_projects/qnx_workspace/bsp-ti-beaglebone-src/install/armle-v7/bin]

After that ifs image was successfully created. What am doing wrong? Why I have to manually write all paths to MKIFS_PATH variable?

Second. I tryed to boot this image and had an error. Here booting log:

=> fatload mmc 0 0x81000000 os.ifs

reading os.ifs

7563096 bytes read in 414 ms (17.4 MiB/s)

=> go 0x81000000

## Starting application at 0x81000000 ...

DDR  DPLL in Lock mode:

  DDR  clock 400 Mhz [400/1]

Disp DPLL in Lock mode:

  Disp clock 200 Mhz [200/1]

MPU  DPLL in Lock mode:

  MPU  clock 1000 Mhz [1000/1]

PER  DPLL in Lock mode:

  PER  clock 192 Mhz [960/5]

CORE DPLL in Lock mode:

  M4 CORE clock 100 Mhz [1000/10]

  M5 CORE clock 125 Mhz [1000/8]

  M6 CORE clock 250 Mhz [1000/4]

Not a BeagleBone??

CPU0: L1 Icache: 512x64

CPU0: L1 Dcache: 512x64 WB

CPU0: L2 Dcache: 4096x64 WB

CPU0: VFP-d32 FPSID=410330c3

CPU0: NEON MVFR0=11110222 MVFR1=00011111

CPU0: 413fc082: Cortex A8 rev 2 500MHz

Loading IFS...done

Unable to load boot process '/proc/boot/procnto-instr'

When I try to boot prebuilt-bsp-ti-beaglebone.ifs (it was in ./image directory after downloading) the kernel starts successfully. What am doing wrong?

post118694: Re: Qnx neutrino (mmx) (ttyp0) root password

2018-03-22T15:58:28Z

User: root

pw: root

Unless somebody has changed it, then you have to ask them :)

post118593: Qnx neutrino (mmx) (ttyp0) root password

2018-02-17T17:22:40Z

Hey i am locking for

Login to

Qnx neutrino mmx ttyp0

post117442: Latest GCC toolchain supported for QNX 6.5

2017-02-23T09:55:18Z

We noticed there is a bug in the GCC shipped with the QNX 6.5 version available to us.

(GCC version 4.4.2)

Please refer to:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46972

What is the version of GCC shipped with the newest available version of QNX 6.5?

If it is below 4.6.0 has this problem been backpatched in the version shipped with QNX 6.5?

post116914: Error compiling x86-generic-SDP6.6

2016-09-29T17:02:44Z

I installed qnx-spd-6.6-201402230339 on to my Win7-64bit machine. I then import x86-generic-SDP6.6 onto the IDE. Then I compile the project as is, and get many errors about missing files, including ptp.h, nic_mutex.h, and so on.

What did I do wrong ? I look through my installation, and canNOT find those files myself. Is there anything wrong with my installation, which went through without any error.

Any advice is appreciated. Thanks !!!

post116474: Freescale i.MX6Q Sabre Board for Smart Devices BSP not working

2016-06-22T20:16:36Z

Hello there,

I have a Freescale iMX6Q Sabre Board for Smart Devices. I picked a BSP for it from the link mentioned below.

http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/FreescaleImx6QSabreSmart

I followed the steps to create the SD Card and then tried booting the device with the SD card prepared but ran into an issue.

The device keeps rebooting. Attached is the message log I see on the serial console.

post114717: Re: QNX6.6 BSP cannot work on MCIMX6Q-SDB

2015-10-22T09:27:38Z

ello, have you resolved this already?

I am also seeing similar issue with SABRE AI (MCIMX6QAICPU1), and it is currently blocking me to go further.

Writing QNX 6.6 BSP image on SD card, booting from SD and it seems that it cause fault? in the middle of boot sequence and do "Welcome to .." again.

I my case, the console looke like below:

====

Welcome to QNX Neutrino Initial Program Loader for Freescale i.MX6

Quad/Dual/DualLite/Solo/QuadPlus Sabre-ARD RevB (ARM Cortex-A9 MPCore)

i.MX6 Quad or Dual CPU detected.

Command:

Press 'D' for serial download, using the 'sendnto' utility

Press 'M' for SDMMC download, IFS filename MUST be 'QNX-IFS'.

SDMMC download...

sdmmc_highspeed:  Switch to high speed mode successful

Load QNX image from SDMMC...

load image done.

Found image               @ 0x11800008

Jumping to startup        @ 0x1080A690

...

(then, "Welcome to QNX xxxx" and the same lines are printed out)

===

post114324: QNX6.6 BSP cannot work on MCIMX6Q-SDB

2015-08-23T04:25:32Z

hi all,

QNX6.6 BSP(Freescale i.MX6Q Sabre Board for Smart Devices) cannot work on my MCIMX6Q-SDB board.

Welcome to QNX Neutrino Initial Program Loader for Freescale i.MX6Q Sabre-Smart)

SDMMC download...

load image done.

Found image               @ 0x18000008

Jumping to startup        @ 0x108068F8

�SCU_CONFIG = 00005503, 4 cpus

L2 cache enabled

CPU0: L1 Icache: 1024x32

CPU0: L1 Dcache: 1024x32 WB

CPU0: VFP-d32 FPSID=41033094

CPU0: NEON MVFR0=10110222 MVFR1=01111111

CPU0: 412fc09a: Cortex A9 MPCore rev 10 792MHz



Detected i.MX6 Dual/Quad, revision TO1.2



PLL1 - System     : 792MHz

PLL2 - System Bus : 528MHz

PLL3 - OTG USB    : 480MHz

PLL4 - Audio      : 36MHz

PLL5 - Video      : 339MHz

PLL7 - Host USB   : 480MHz

PLL8 - Enet       : 50MHz

IPG clock     : 66000000Hz

IPG per clock : 66000000Hz

UART clock    : 80000000Hz

CSPI clock    : 60000000Hz

AHB clock     : 132000000Hz

AXI clock     : 264000000Hz

EMI_SLOW clock: 29333333Hz

DDR clock     : 528000000Hz

USDHC1 clock  : 198000000Hz

USDHC2 clock  : 198000000Hz

USDHC3 clock  : 198000000Hz

USDHC4 clock  : 198000000Hz

ENFC clock    : 24000000Hz



decompressing...done

CPU1: L1 Icache: 1024x32

CPU1: L1 Dcache: 1024x32 WB

CPU1: VFP-d32 FPSID=41033094

CPU1: NEON MVFR0=10110222 MVFR1=01111111

CPU1: 412fc09a: Cortex A9 MPCore rev 10 792MHz

CPU2: L1 Icache: 1024x32

CPU2: L1 Dcache: 1024x32 WB

CPU2: VFP-d32 FPSID=41033094

CPU2: NEON MVFR0=10110222 MVFR1=01111111

CPU2: 412fc09a: Cortex A9 MPCore rev 10 792MHz

CPU3: L1 Icache: 1024x32

CPU3: L1 Dcache: 1024x32 WB

CPU3: VFP-d32 FPSID=41033094

CPU3: NEON MVFR0=10110222 MVFR1=01111111

CPU3: 412fc09a: Cortex A9 MPCore rev 10 792MHz

cpu_startnext: cpu1 -> fc411d58

cpu_startnext: cpu2 -> fc411d58

cpu_startnext: cpu3 -> fc411d58



System page at phys:10023000 user:fc410000 kern:fc410000

Starting next program at vfe054e3c

cpu_startnext: cpu0 -> fe054e3c



Welcome to QNX Neutrino Initial Program Loader for Freescale i.MX6Q Sabre-Smart)

SDMMC download...

load image done.

Found image               @ 0x18000008

Jumping to startup        @ 0x108068F8

�SCU_CONFIG = 00005503, 4 cpus

L2 cache enabled

CPU0: L1 Icache: 1024x32

CPU0: L1 Dcache: 1024x32 WB

CPU0: VFP-d32 FPSID=41033094

CPU0: NEON MVFR0=10110222 MVFR1=01111111

CPU0: 412fc09a: Cortex A9 MPCore rev 10 792MHz



Detected i.MX6 Dual/Quad, revision TO1.2



PLL1 - System     : 792MHz

PLL2 - System Bus : 528MHz

PLL3 - OTG USB    : 480MHz

PLL4 - Audio      : 36MHz

PLL5 - Video      : 339MHz

PLL7 - Host USB   : 480MHz

PLL8 - Enet       : 50MHz

IPG clock     : 66000000Hz

IPG per clock : 66000000Hz

UART clock    : 80000000Hz

CSPI clock    : 60000000Hz

AHB clock     : 132000000Hz

AXI clock     : 264000000Hz

EMI_SLOW clock: 29333333Hz

DDR clock     : 528000000Hz

USDHC1 clock  : 198000000Hz

USDHC2 clock  : 198000000Hz

USDHC3 clock  : 198000000Hz

USDHC4 clock  : 198000000Hz

ENFC clock    : 24000000Hz



decompressing...done

CPU1: L1 Icache: 1024x32

CPU1: L1 Dcache: 1024x32 WB

CPU1: VFP-d32 FPSID=41033094

CPU1: NEON MVFR0=10110222 MVFR1=01111111

CPU1: 412fc09a: Cortex A9 MPCore rev 10 792MHz

CPU2: L1 Icache: 1024x32

CPU2: L1 Dcache: 1024x32 WB

CPU2: VFP-d32 FPSID=41033094

CPU2: NEON MVFR0=10110222 MVFR1=01111111

CPU2: 412fc09a: Cortex A9 MPCore rev 10 792MHz

CPU3: L1 Icache: 1024x32

CPU3: L1 Dcache: 1024x32 WB

CPU3: VFP-d32 FPSID=41033094

CPU3: NEON MVFR0=10110222 MVFR1=01111111

CPU3: 412fc09a: Cortex A9 MPCore rev 10 792MHz

cpu_startnext: cpu1 -> fc411d58

cpu_startnext: cpu2 -> fc411d58

cpu_startnext: cpu3 -> fc411d58



System page at phys:10023000 user:fc410000 kern:fc410000

Starting next program at vfe054e3c

cpu_startnext: cpu0 -> fe054e3c



Welcome to QNX Neutrino Initial Program Loader for Freescale i.MX6Q Sabre-Smart)

SDMMC download...

load image done.

Found image               @ 0x18000008

Jumping to startup        @ 0x108068F8

�SCU_CONFIG = 00005503, 4 cpus

L2 cache enabled

CPU0: L1 Icache: 1024x32

CPU0: L1 Dcache: 1024x32 WB

CPU0: VFP-d32 FPSID=41033094

CPU0: NEON MVFR0=10110222 MVFR1=01111111

CPU0: 412fc09a: Cortex A9 MPCore rev 10 792MHz



Detected i.MX6 Dual/Quad, revision TO1.2



PLL1 - System     : 792MHz

PLL2 - System Bus : 528MHz

PLL3 - OTG USB    : 480MHz

PLL4 - Audio      : 36MHz

PLL5 - Video      : 339MHz

PLL7 - Host USB   : 480MHz

PLL8 - Enet       : 50MHz

IPG clock     : 66000000Hz

IPG per clock : 66000000Hz

UART clock    : 80000000Hz

CSPI clock    : 60000000Hz

AHB clock     : 132000000Hz

AXI clock     : 264000000Hz

EMI_SLOW clock: 29333333Hz

DDR clock     : 528000000Hz

USDHC1 clock  : 198000000Hz

USDHC2 clock  : 198000000Hz

USDHC3 clock  : 198000000Hz

USDHC4 clock  : 198000000Hz

ENFC clock    : 24000000Hz



decompressing...done

CPU1: L1 Icache: 1024x32

CPU1: L1 Dcache: 1024x32 WB

CPU1: VFP-d32 FPSID=41033094

CPU1: NEON MVFR0=10110222 MVFR1=01111111

CPU1: 412fc09a: Cortex A9 MPCore rev 10 792MHz

CPU2: L1 Icache: 1024x32

CPU2: L1 Dcache: 1024x32 WB

CPU2: VFP-d32 FPSID=41033094

CPU2: NEON MVFR0=10110222 MVFR1=01111111

CPU2: 412fc09a: Cortex A9 MPCore rev 10 792MHz

CPU3: L1 Icache: 1024x32

CPU3: L1 Dcache: 1024x32 WB

CPU3: VFP-d32 FPSID=41033094

CPU3: NEON MVFR0=10110222 MVFR1=01111111

CPU3: 412fc09a: Cortex A9 MPCore rev 10 792MHz

cpu_startnext: cpu1 -> fc411d58

cpu_startnext: cpu2 -> fc411d58

cpu_startnext: cpu3 -> fc411d58



System page at phys:10023000 user:fc410000 kern:fc410000

Starting next program at vfe054e3c

cpu_startnext: cpu0 -> fe054e3c

Best Regards

MaJi

post111329: Re: Error while linking stdc++ lib using ntox86-ld

2014-08-06T18:04:43Z

This issue is solved by adding the correct header files while compilation

just add

-I$(QNX_TARGET)/usr/include/c++/4.2.4 -I$(QNX_TARGET)/usr/include/c++/4.2.4/i386-pc-nto-qnx6.4.0

as compilation flag while compiling

Thanks,

Nikshay

post111288: Error while linking stdc++ lib using ntox86-ld

2014-08-03T07:59:01Z

Hi All,

we are getting linking error (see the log below) while linking stdc++ lib (located at $(QNX_TARGET)/x86/lib/gcc/4.2.4/) into our image using the linker ntox86-ld.

In function `__sti__$E':

/local1/tools/qnx/qnx640/target/qnx6/usr/include/cpp/iostream:65536: undefined reference to `std::_Winit::_Winit()'

/local1/tools/qnx/qnx640/target/qnx6/usr/include/cpp/iostream:65536: undefined reference to `std::_Winit::~_Winit()'

Please help me in fixing this issue

Thanks in advance

Regards,

Nikshay

post111006: Where do I find hidview?

2014-07-09T22:25:41Z

I am using a SabreLite board with 6.5.0 SP1 and have loaded the BSP from it (onto SD card, etc) but can not find the hidview app that I see lot's of people (and documentation) referring to. Where do I find this utility?

post110836: Re: Error while linking new libraries using ntox86-ld

2014-06-24T06:06:41Z

Hi Ryan,

The issue is solved after linking the library in this order

-lstdc++ -lgcc -lc

Many thanks for your help!!!

Regards,

Nikshay

post110834: Re: Error while linking new libraries using ntox86-ld

2014-06-24T01:45:41Z

But you're linking statically. You'd need to link ljbgcc again after libstdc++ to resolve any undefined references to ljbgcc functions. Or use the --start-group,--end-group options to have the linker have a second pass to resolve the dependencies.

  Original Message

From: Nikshay Shrivastava

Sent: Monday, June 23, 2014 9:41 PM

To: sdpprereleases-community

Reply To: sdpprereleases-community@community.qnx.com

Subject: Re: Error while linking new libraries using ntox86-ld

Hi Ryan,

From the linker output I can see we are already linking libgcc.a

Here is the linker flags that we are using

LDFLAGS+= -no-warn-mismatch -m i386nto -verbose \

                    -L $(QNX_TARGET)/x86/lib \

                    -L $(QNX_HOST)/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.2.4 \

                    -L $(QNX_TARGET)/usr/lib \

                    -L $(QNX_TARGET)/lib/gcc/4.2.4 \

                    -L $(QNX_TARGET)/x86/lib/gcc/4.2.4 \

                    -lc -ltcl84 -lsocket -lm -lc -lgcc -lc -lirc_s -lstdc++

Regards,

Nikshay

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post110833

To cancel your subscription to this discussion, please e-mail sdpprereleases-community-unsubscribe@community.qnx.com

post110833: Re: Error while linking new libraries using ntox86-ld

2014-06-24T01:41:37Z

Hi Ryan,

From the linker output I can see we are already linking libgcc.a

Here is the linker flags that we are using

LDFLAGS+= -no-warn-mismatch -m i386nto -verbose \

                    -L $(QNX_TARGET)/x86/lib \

                    -L $(QNX_HOST)/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.2.4 \

                    -L $(QNX_TARGET)/usr/lib \

                    -L $(QNX_TARGET)/lib/gcc/4.2.4 \

                    -L $(QNX_TARGET)/x86/lib/gcc/4.2.4 \

                    -lc -ltcl84 -lsocket -lm -lc -lgcc -lc -lirc_s -lstdc++

Regards,

Nikshay

post110826: Re: Error while linking new libraries using ntox86-ld

2014-06-23T18:37:46Z

On 14-06-23 01:46 PM, Nikshay Shrivastava wrote:

> Hi Ryan,

>

> Thanks for the update, after adding -L$QNX_TARGET/x86/lib/gcc/4.2.4 the issue is solved but now we are getting a new error

>

> "undefined reference to `_Unwind_Resume'"

>

> Please suggest how we can solve this issue.

Link in libgcc. It will be in

$QNX_HOST/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.2.4/libgcc.a.

If you link with the gcc drivers then you don't have to add these paths,

and implicit libs as driver handles it for you. This is why linking

directly with ld is not recommended.

Regards,

Ryan Mansfield

post110824: Re: Error while linking new libraries using ntox86-ld

2014-06-23T17:46:27Z

Hi Ryan,

Thanks for the update, after adding -L$QNX_TARGET/x86/lib/gcc/4.2.4 the issue is solved but now we are getting a new error

"undefined reference to `_Unwind_Resume'"

Please suggest how we can solve this issue.

Thanks in advance

Regards,

Nikshay

post110821: Re: Error while linking new libraries using ntox86-ld

2014-06-23T13:18:58Z

On 14-06-23 02:13 AM, Tapasee R G Ch wrote:

> Update:

>

> Hi Ryan,

>

> We use static linking and it looks for libstdc++.a file. We can see that its missing from the standard library(QNX_TARGET/x86/lib). Please let me know how I can get libstdc++.a file for QNX 6.4.0.

As I previously mentioned, add -L$QNX_TARGET/x86/lib/gcc/<gcc version>

when linking. There's a libstdc++.a in there. I assumed your gcc version

was 4.2.4 since you mentioned you were using QNX 6.4.0

Regards,

Ryan Mansfield

post110807: Re: Error while linking new libraries using ntox86-ld

2014-06-23T06:13:01Z

Update:

Hi Ryan,

We use static linking and it looks for libstdc++.a file. We can see that its missing from the standard library(QNX_TARGET/x86/lib). Please let me know how I can get libstdc++.a file for QNX 6.4.0.

Thanks in Advance,

Tapasee

post110738: Re: Error while linking new libraries using ntox86-ld

2014-06-18T09:06:56Z

Thanks Ryan for your inputs. I will try this.

Thanks

Tapasee

post110712: Re: Error while linking new libraries using ntox86-ld

2014-06-17T13:48:35Z

On 14-06-17 06:35 AM, Tapasee R G Ch wrote:

> Hi All,

>

> wer are facing a problem while linking new libraries into our image using the linker ntox86-ld.

>

> We have included the library path using the option "-L ......./qnx/qnx640/target/qnx6/x86/lib

> " which has the libstdc++.so in it. And we are invoking the library inclusion with option -lstdc++ in the make options and the error message received is

> "ntox86-ld: cannot find -lstdc++"

>

> Please let me know if any of you faced the same problem and fixed it successfully.

If you're using the linker directly, you should be add

-L$QNX_TARGET/x86/lib/gcc/4.2.4/ which has the symlink libstdc++.so to

../../libstdc++.so.6.

Regards,

Ryan Mansfield

post110710: Error while linking new libraries using ntox86-ld

2014-06-17T10:35:05Z

Hi All,

wer are facing a problem while linking new libraries into our image using the linker ntox86-ld.

We have included the library path using the option "-L ......./qnx/qnx640/target/qnx6/x86/lib

" which has the libstdc++.so in it. And we are invoking the library inclusion with option -lstdc++ in the make options and the error message received is

"ntox86-ld: cannot find -lstdc++"

Please let me know if any of you faced the same problem and fixed it successfully.

Thanks in Advance for your time,

Tapasee

post110332: Re: Problem installing SDP 6.6 on Windows 7

2014-05-14T14:57:32Z

Removing the .com.zerog.registry.xml files fixed the issue. Thanks so much Natalia for the quick reply.

post110330: Re: Problem installing SDP 6.6 on Windows 7

2014-05-14T14:34:48Z

It sounds like you had an Alpha version of SDP 6.6 installed previously, and it has not been uninstalled correctly.

---------------

If the uninstaller doesn't fully remove all the components, do the following:

    Delete the folder where you installed QNX SDP.

    Delete the "QNX Momentics" desktop shortcut and the link in the Start menu.

    Find and delete all occurrences of .com.zerog.registry.xml. This is a hidden file, so you must enable the Show hidden files and folders option.

    Delete the QNX SDP entries from the Add/Remove Program list by choosing Control Panel > Programs and Features from the Start menu, right-clicking on each QNX SDP entry, and then choosing Delete from the list.

-----------

Hope this helps.

Natalia

> On our project we are upgrading form 6.5.0 to 6.6 of the QNX SDP. When I run

> the 6.6 installer I get the initial Welcome dialog and I click Next at the

> bottom right. After that I get a popup dialog saying "QNX Software Development

>  Platform 6.6 is already installed in the following location: NULL". I tried

> uninstalling all QNX related programs and have rebooted several times but the

> popup persists.

post110328: Problem installing SDP 6.6 on Windows 7

2014-05-14T14:26:42Z

On our project we are upgrading form 6.5.0 to 6.6 of the QNX SDP. When I run the 6.6 installer I get the initial Welcome dialog and I click Next at the bottom right. After that I get a popup dialog saying "QNX Software Development Platform 6.6 is already installed in the following location: NULL". I tried uninstalling all QNX related programs and have rebooted several times but the popup persists.

post109891: Re: Virtual to physical adress problem for DMA

2014-04-11T05:21:33Z

Hi!

Sorry, but why are u using DMA just for 4 bytes? It's not effectively!

I'm investigated DMA(sdma library for iMX6) and my conclusion is - DMA has a lot of bugs!

post108971: PPSM

2014-02-21T07:12:40Z

Hello, where can i find the libppsm.a ??

I want to use the speedstep...

Thanks...

post108796: Virtual to physical adress problem for DMA

2014-02-14T04:44:34Z

Hello All.

Working on porting SDIO driver on to QNX. I am using DMA for reading and writing data basically for DMA iam using 4 bytes for transfer meaning

i need to read an integer value using DMA by passing integer address for DMA.

How is this done.

I have an integer variable int value;

For DMA i get the physical address of this address value

mem_offset64(&vaue, NOFD, 1, &offset, 0)

This physical address is used for DMA. Problem i see is iam not able to get any value from the controller later using mmap for 4 bytes allocation i got the adress same address was used for DMA which was successful.

Later i used volatile int value which also didn't give the right physical address for successful DMA.

Is there a way where i can get right physical address for address of value which will result in successful DMA.

Regards

Kaushik

post96322: Qnx 6.4.0 on dell optiplex 990

2012-10-15T12:27:53Z

Hi,

I have just installed QNX 6.4.0 (qnxsdp-6.4.0-200810211530-dvd) image into dell optiplex 990 desktop, It seems like USB devices (Key board, mouse and mass storage devices) are not working, Is is a known issue?, Can anybody help me how to fix this?

post92003: RE: RE: VMware Player - QNX SDP problem when run in WIndows 7 host machine

2012-03-09T00:52:10Z

> -----Message d'origine-----

> De : Trieu Pham [mailto:community-noreply@qnx.com]

> Envoyé : 8 mars 2012 17:59

> À : sdpprereleases-community

> Objet : Re: RE: VMware Player - QNX SDP problem when run in WIndows 7

> host machine

>

> Did you have to run any patch or special setting?

No. Just to see if it is a problem with your installation of QNX. Copy the virtual machine of your friend over to your machine and run that.

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post92002

>

post92002: Re: RE: VMware Player - QNX SDP problem when run in WIndows 7 host machine

2012-03-08T22:58:59Z

Did you have to run any patch or special setting?

post92001: RE: VMware Player - QNX SDP problem when run in WIndows 7 host machine

2012-03-08T22:46:32Z

Works fine for me.

> -----Message d'origine-----

> De : Trieu Pham [mailto:community-noreply@qnx.com]

> Envoyé : 8 mars 2012 16:07

> À : sdpprereleases-community

> Objet : VMware Player - QNX SDP problem when run in WIndows 7 host

> machine

>

> I have installed the VMware Player 4.2 to run in WIndows 7 host. The

> installation and launching VMplayer ins talled .iso image were good.

> However, within the QNX virtual machine I could not create file, copy files or

> move files between folder.

>

> My colleague installed and ran the same VMware Player in Windows XP with

> no problem.

>

> Can you show the fix or work around the problem in Windows 7?

>

> Thanks

> Trieu Pham

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post92000

post92000: VMware Player - QNX SDP problem when run in WIndows 7 host machine

2012-03-08T21:06:59Z

I have installed the VMware Player 4.2 to run in WIndows 7 host. The installation and launching VMplayer ins talled .iso image were good. However, within the QNX virtual machine I could not create file, copy files or move files between folder.

My colleague installed and ran the same VMware Player in Windows XP with no problem.

Can you show the fix or work around the problem in Windows 7?

Thanks

Trieu Pham

post89751: How to TraceEvent() in new SMP safe InterruptHookIdle2() API?

2011-10-28T21:36:30Z

Accordign to the docs (http://www.qnx.com/developers/docs/6.4.1/neutrino/lib_ref/t/traceevent.html) :

You can call TraceEvent() from an interrupt/event handler. However, not all trace modes are valid in this case. The valid trace modes are:

_NTO_TRACE_INSERTSUSEREVENT

_NTO_TRACE_INSERTCUSEREVENT

_NTO_TRACE_INSERTUSRSTREVENT

_NTO_TRACE_INSERTEVENT

_NTO_TRACE_STOP

_NTO_TRACE_STARTNOSTATE

_NTO_TRACE_START

If I call TraceEvent(_NTO_TRACE_INSERTUSRSTREVENT, int event, const char * str) after waking up to log information, I do not see it working well after looking at the logs.  I have tried disabling other trace events and still it does not seem to work as expected.  I can use the above API fine in any thread - Just not in my ISR of interest.  The docs also comment how _NTO_TRACE_INSERTEVENT

is "real" but I'm not sure how to use the API to test it (i.e. How do i fill in the timestamp its an int?   If the _NTO_TRACE_INSERTEVENT method is more powerful and direct, can you please provide some commented code sample of how to setup the base data structures and use it with proper time stamps?  I like the *USR* events cause the API is easy to use, but i am not successful in using them in my ISR.  It would also be nice to leverage some of the other classes and events so that my traces have pretty icons and format in the timeline view in the IDE.

My goal is to add trace events when waking up from sleep (exiting the idle task).  The events should be strings so they can be easily understood in the IDE.  I want to trace the the different low power modes that we entered when leaving the idle task.  The API to trace needs to be ISR safe as it is called when exiting sleep from the ISR hooked by InterruptHookIdle2().

Thanks!

post88563: licsence of SDP 6.4.1

2011-09-01T01:28:45Z

Hello,I am learning QNX now , I download the SDP from the QNX web site ,however,when i intall it ,it need the license ,how can i get a trial liscence ?

Thank you!

post85825: QNX 6.5 Kernel footprint and line of code

2011-05-18T04:06:19Z

What is the QNX 6.5 Kernel footprint size and approx line of code?

post57632: Re: 6.5.0 M8A - apic boot issues

2010-06-23T07:15:12Z

> Yep, I'm running the default VESA driver. I've never heard that the VESA

> driver is not designed for real time operation. But I would be glad if you can

> provide me with further information about this issue.

I do not have further information, however my understanding of VESA is that the VESA driver is making calls into the VESA BIOS, which is in ROM on the graphics card. During such calls it might be forced to disable interrupts, which can disturb some realtime requirements. But if this happens only when mode switching or during actual graphics operations I'm not sure. If this is a concern for you, it may be worth a separate thread in the Drivers forum.

Cheers,

- Malte

post57460: Re: 6.5.0 M8A - apic boot issues

2010-06-22T15:35:49Z

> > - Graphic Adapter : 512 MB Quadro NVIDIA FX580 (PCI-E)

>

> Are you running the VESA graphics driver? I think this one is only to enable

> self hosted development on machines without a native graphics driver. Not sure

> but I think the VESA graphics was not designed for real time systems (or

> can't be, because of the nature of VESA).

>

> - Malte

Yep, I'm running the default VESA driver. I've never heard that the VESA driver is not designed for real time operation. But I would be glad if you can provide me with further information about this issue.

However I'm not sure if there is even the possibility to use another graphics driver for the NVIDIA FX580. Some days ago I though about using the GPU for dedicated time consuming calculations where you also would need an appropriate graphics driver....

By the way, I moved the present IOAPIC / IRQ sharing discussion to the drivers / BSP forum as suggested by Mike

see: http://community.qnx.com/sf/discussion/do/listPosts/projects.bsp/discussion.bsp.topc14273

Best Regards

Phil

post57290: Re: 6.5.0 M8A - apic boot issues

2010-06-21T13:44:56Z

> - Graphic Adapter : 512 MB Quadro NVIDIA FX580 (PCI-E)

Are you running the VESA graphics driver? I think this one is only to enable self hosted development on machines without a native graphics driver. Not sure but I think the VESA graphics was not designed for real time systems (or can't be, because of the nature of VESA).

- Malte

post57070: Re: 6.5.0 M8A - apic boot issues

2010-06-17T13:31:12Z

startup-apic/pci-bios-v2 are designed for BIOS based systems. We do not override whatever BIOS decisions are made wrt interrupt assignments and hence sharing. There is one exception. Most (if not all) BIOS's for Intel based systems will route the PIRQ pins (usually 8 or them, as is the case for the ICH10) back to interrupt vectors 0 - 15. On these Intel based systems we will undo this routing (if possible) so that interrupts 16 thru 23 are used instead. This may or may not eliminate sharing of a 0-15 interrupt but it will not eliminate the sharing (established by the BIOS) of PIRQ pins.

Which PIRQ a device is configured to use would (normally) be established by a startup configured specifically for the board based on targeted application and consideration of all of the devices to be used.

Regards,

(the other) Mike

[Please move any further technical discussions to the aforementioned forum ... thanks]

post56939: Re: 6.5.0 M8A - apic boot issues

2010-06-16T12:04:20Z

Hi Mike,

thank you for the information!

I've got still one important question: is startup-apic and pci-bios-v2 trying to avoid IRQ sharing at all? Because if I have a look with "pci -v" after booting, I still see shared IRQs.

At the moment we have big troubles with shared interrupts hence it would be very interesting to know how these new programs are handling it.

Attached is the output of "pci -vvv" on a DELL Precision T3500 PC with the following hardware:

- Chipset: Intel X58-Chipset (ICH10R/D0 Southbridge)

- CPU: Intel Xeon W3520 (Quadcore)

- Graphic Adapter : 512 MB Quadro NVIDIA FX580 (PCI-E)

- NICs: 2 x 82572EI Gigabit Ethernet (PCI-E)

You'll see the graphic and network adapter sharing the same IRQ #11.

Thanks for you help in advance!

Best Regards

Phil

post56885: Re: 6.5.0 M8A - apic boot issues

2010-06-15T17:51:44Z

Hello Phil,

The bad news is that you'll need to wait for updated versions. The good news

is that we'll be releasing 6.5.0 very soon - we're going through the final

test cycle.

Thanks!

Mike Lemke

Engineering Operations

On 15/06/10 12:39 PM, "Philipp Lutz" <community-noreply@qnx.com> wrote:

> Hi Mike,

>

> do I have to wait for the official release of QNX 6.5.0 for updated versions

> of startup-apic / pci-bios-v2 or can I get them somewhere within the QNX

> community area? Would be awesome to immediately start testing it.

>

> Cheers

> Phil

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post56870

>

post56870: Re: 6.5.0 M8A - apic boot issues

2010-06-15T16:39:41Z

Hi Mike,

do I have to wait for the official release of QNX 6.5.0 for updated versions of startup-apic / pci-bios-v2 or can I get them somewhere within the QNX community area? Would be awesome to immediately start testing it.

Cheers

Phil

post56863: Re: 6.5.0 M8A - apic boot issues

2010-06-15T15:38:48Z

All,

There have been some recent updates to startup-apic/pci-bios-v2 in order to enable operation on a wider variety of machines (originally we were asked to target/test a very limited set of Intel based boards). While there is no guarantee that any of these recent changes will solve your specific issues, the updates (which will be released in 6.5.0) are still the best starting point for any modifications that may be required for your specific platforms. Remember that startups are board specific by design.

Please also note that, we DO NOT currently support more than 1 IOAPIC (PR75534 was created to track this issue). The reason relates back to the previously limited set of boards which we originally planned to support, none of which had multiple IOAPIC's. The work for this is currently in progress.

We will work to continuously improve this code base and welcome all feedback.

In the future, please post any BSP/startup related issues to the BSP and drivers forum (http://community.qnx.com/sf/discussion/do/listTopics/projects.bsp/discussion.bsp/) as there is a better chance that the developers involved are monitoring it.

Regards,

Mike

post56855: Re: 6.5.0 M8A - apic boot issues

2010-06-15T14:40:35Z

Here is what i get from"startup-apic -vv"

Base CPU interrupt for APIC is 48

lapic_configure(cpu=0)

ACPI header found for IO-APIC 8 @ fec00000 [base=0]

Added IO-APIC 8 @ fec00000 (vaddr: fed21000)

ACPI header found for IO-APIC 9 @ fec80000 [base=24]

Added IO-APIC 9 @ fec80000 (vaddr: fed22000)

Added 2 IOAPIC's from ACPI tables

Found 2 IOAPIC's however only 1 will be configured

No access functions found for IOAPIC id 8, using ICH defaults

Autofill: Only 16 of requested 24 entries available for profile 6

ACPI header found for Interrupt source override: bus:0, SrcIRQ:0, GSI:2, Flags:00000000

** NEED A RESOLVER for ACPI INTSRC FLAGS **

checking GPIO pin 2 .. no

checking GPIO pin 4 .. no

checking GPIO pin 5 .. no

Clearing 24 IOAPIC entries

Configuring 24 IOAPIC entries

[0] vec: 54,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:0, type:3, flags:00000005

[1] vec: 55,   cpumask:00000001, ID: 8, busid:0, busintr:1, dest intin:1, type:0, flags:00000005

[2] vec: 56,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:2, type:0, flags:00000000

[3] vec: 57,   cpumask:00000001, ID: 8, busid:0, busintr:3, dest intin:3, type:0, flags:00000005

[4] vec: 58,   cpumask:00000001, ID: 8, busid:0, busintr:4, dest intin:4, type:0, flags:00000005

[5] vec: 59,   cpumask:00000001, ID: 8, busid:0, busintr:5, dest intin:5, type:0, flags:00000005

[6] vec: 60,   cpumask:00000001, ID: 8, busid:0, busintr:6, dest intin:6, type:0, flags:00000005

[7] vec: 61,   cpumask:00000001, ID: 8, busid:0, busintr:7, dest intin:7, type:0, flags:00000005

[8] vec: 62,   cpumask:00000001, ID: 8, busid:0, busintr:8, dest intin:8, type:0, flags:00000005

[9] vec: 63,   cpumask:00000001, ID: 8, busid:0, busintr:9, dest intin:9, type:0, flags:00000005

[10] vec: 64,   cpumask:00000001, ID: 8, busid:0, busintr:10, dest intin:10, type:0, flags:00000005

[11] vec: 65,   cpumask:00000001, ID: 8, busid:0, busintr:11, dest intin:11, type:0, flags:00000005

[12] vec: 66,   cpumask:00000001, ID: 8, busid:0, busintr:12, dest intin:12, type:0, flags:00000005

[13] vec: 67,   cpumask:00000001, ID: 8, busid:0, busintr:13, dest intin:13, type:0, flags:00000005

[14] vec: 68,   cpumask:00000001, ID: 8, busid:0, busintr:14, dest intin:14, type:0, flags:00000005

[15] vec: 69,   cpumask:00000001, ID: 8, busid:0, busintr:15, dest intin:15, type:0, flags:00000005

[16] vec: 70,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:16, type:0, flags:0000000f

[17] vec: 71,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:17, type:0, flags:0000000f

[18] vec: 72,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:18, type:0, flags:0000000f

[19] vec: 73,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:19, type:0, flags:0000000f

[20] vec: 74,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:20, type:0, flags:0000000f

[21] vec: 75,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:21, type:0, flags:0000000f

[22] vec: 76,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:22, type:0, flags:0000000f

[23] vec: 77,   cpumask:00000001, ID: 8, busid:0, busintr:0, dest intin:23, type:0, flags:0000000f

IOAPIC 8: successfully configured 24 vectors from 0 to 23

MSI interrupt = 0x00000100

MSI vector no = 78 0x0000004e

MSI vec count = 177

lapic_configure(cpu=1)

lapic_configure(cpu=2)

lapic_configure(cpu=3)

Header size=0x0000009c, Total Size=0x000009d8, #Cpu=4, Type=0

Section:system_private offset:0x00000270 size:0x00000068

Section:qtime offset:0x00000190 size:0x00000060

Section:callout offset:0x000000a0 size:0x00000048

Section:cpuinfo offset:0x000001f0 size:0x00000080

Section:cacheattr offset:0x000009d8 size:0x00000000

Section:meminfo offset:0x000009d8 size:0x00000000

Section:asinfo offset:0x000005b8 size:0x000002e0

Section:hwinfo offset:0x000003b8 size:0x00000200

Section:typed_strings offset:0x000002d8 size:0x00000020

Section:strings offset:0x000002f8 size:0x000000c0

Section:intrinfo offset:0x00000898 size:0x00000140

Section:smp offset:0x00000128 size:0x00000010

Section:pminfo offset:0x000009d8 size:0x00000000

Section:mdriver offset:0x000009d8 size:0x00000000

Section:boxinfo offset:0x00000168 size:0x00000028

Section:diskinfo offset:0x000009d8 size:0x00000000

Section:smpinfo offset:0x00000138 size:0x00000020

Section:gdt offset:0x00000068

Section:idt offset:0x0000006c

Section:pgdir offset:0x00000070

System page at phys:0001f000 user:fed23000 kern:fed25000

Starting next program at vf0051118

post56818: Re: 6.5.0 M8A - apic boot issues

2010-06-15T08:37:10Z

Now I got it running, when I'm only using "pci-bios-v2" instead of "pci-bios=pci-bios-v2" in my buildfile, which has been proposed by the release notes.

However I still see shared interrupts e.g. graphic and network adapter on IRQ 11.

Is this how the APIC mode is supposed to work in QNX or is still something wrong? Can I somehow influence the IRQ assignments with starup-apic?

When I have a null modem serial cable I'll post the startup-apic debug output.

post56540: Re: 6.5.0 M8A - apic boot issues

2010-06-10T16:08:02Z

Hi!

Did you get any progress concerning this issue? I'm still stuck...

How looks your buildfile? Do you start both startup-apic and startup-bios or only startup-apic in this case?

Regards

Phil

post56104: Re: RE: 6.5.0 prerelease and minimal PtWebClient Phab application

2010-06-04T21:43:15Z

Resolved by setting the url on the realize callback.

Sorry about calling wolf :-(

cheers,

George

post56064: Re: RE: 6.5.0 prerelease and minimal PtWebClient Phab application

2010-06-04T15:07:13Z

Well, in order to be certain, I downloaded

http://www.openqnx.com/index.php?name=PNphpBB2&file=download&id=186

built and ran that one too, and same result.

And the helpviewer does work, you are right about that :-(

George

post56049: RE: 6.5.0 prerelease and minimal PtWebClient Phab application

2010-06-04T13:53:00Z

Are you sure your code is correct? Helpviewer is an example of a PhAB

application that uses mozserver, and it works.

-----Original Message-----

From: George Refseth [mailto:community-noreply@qnx.com]

Sent: Friday, June 04, 2010 6:11 AM

To: sdpprereleases-community

Subject: 6.5.0 prerelease and minimal PtWebClient Phab application

When using the mozserver nothing is rendered.

Is this a known issue?

/george

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post56037

post56037: 6.5.0 prerelease and minimal PtWebClient Phab application

2010-06-04T10:10:43Z

When using the mozserver nothing is rendered.

Is this a known issue?

/george

post55882: Compatibility

2010-06-01T16:04:15Z

I ran 6.5.0 M9 on a Corvalent SB5000P using the APIC stuff, it all looks good. No shared interrupt anymore!!!

post55559: Re: QNX 650 not running with 2 cores under virtualbox 3x ( 641 did )

2010-05-26T09:25:16Z

added an entry to the virtualBox forum also

http://forums.virtualbox.org/viewtopic.php?f=4&t=31387&p=139463#p139463

post55388: Re: QNX 650 not running with 2 cores under virtualbox 3x ( 641 did )

2010-05-21T16:37:40Z

tried virtualbox 3.2 today -> same problem

post55180: Re: QNX 6.5.0 installation and HDD with already allocated partitions

2010-05-19T17:45:42Z

Hi Mike,

Sorry for the delay. We can't reproduce it here. I'm thinking it's something

along the lines of this issue:

http://community.qnx.com/sf/go/topc8694

so could you post the _exact_ sequence you followed to get the 'bad' VM and

the partition table once you do?

Thanks,

Keith Russell

On 10-05-11 12:55 , "Mike Gorchak" <community-noreply@qnx.com> wrote:

>> Can you let me know what hardware this was on? Please attach the output of

>> pci

>> -v.

>

> The platform is VMWare 7.0.1 build 227600. Output of pci -v is attached in

> archive.

>

>> Also please attach the output of "fdisk /dev/hd0 info" and "fdisk /dev/hd0

>> show" (assuming your dealing with the first hard drive).

>

> Output of fdisk info and fdisk show is also attached in archive. But I deleted

> all partitions to install 6.5.0 M9.

>

> It is easy to reproduce this problem, I checked this few minutes before. Just

> create two small partitions of any size on your HDD, for example, with type

> 179 and type 177. And then try to install 6.5.0 M9 using partition type 178 to

> the third available partition.

>

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post54217

post54920: QNX 6.5.0 APIC change interrupt priority

2010-05-18T09:03:25Z

On my x86 system with APIC enabled the kernel tells me on bootup:

---------------------------------------------------------------------

Search for ACPI INTSRC's

ACPI header found for Interrupt source override: bus:0, SrcIRQ:0, GSI:2, Flags:00000000

** NEED A RESOLVER for ACPI INTSRC FLAGS **

[0] IOAPIC 1 intsrc: busid:0, busintr:0, gsi:2, flags:00000000

Overriding pin 2 intsrc @ idx 2

checking GPIO pin 2 .. no

checking GPIO pin 3 .. no

checking GPIO pin 4 .. no

checking GPIO pin 5 .. no

Clearing 24 IOAPIC entries

Configuring 24 IOAPIC entries

[0] vec: 54,   cpumask:00000001, ID: 1, busid:0, busintr:0, dest intin:0, type:3, flags:00000005

[1] vec: 55,   cpumask:00000001, ID: 1, busid:0, busintr:1, dest intin:1, type:0, flags:00000005

...

[23] vec: 77,   cpumask:00000001, ID: 1, busid:0, busintr:0, dest intin:23, type:0, flags:0000000f

IOAPIC 1: successfully configured 24 vectors from 0 to 23

MSI interrupt = 0x00000100

MSI vector no = 78 0x0000004e

MSI vec count = 177

---------------------------------------------------------------------

How can I change priorities?

For example I want Interrupt 11 (got from the HPET chip in x86 systems) at the highest priority less than vector 54.

Must I write direct into APIC registers?

How can I move an entry in the IDT to another place?

This need not to by dynamic at runtime. It's enough to set the prioritys static on bootup

Thanks

Gunther

post54594: QNX 650 not running with 2 cores under virtualbox 3x ( 641 did )

2010-05-13T18:21:34Z

Hi,

I was using QNX 6.4.1 on virtualbox with 2 CPUs without problems.

When I tried out QNX 6.5.0 ( M4 and M9 ) I found that only setting up 1 CPU is working

here is the errormessage when running qnxbasesmp.ifs

apic_local_intr.c:212 -- ASSERT((cpu ==0)||(lapic_read(LAPIC_LLOR)&LVT_MASKED)) failed!

CPU 1 start failure

Would be nice, if this setup would be possible again.

Greeting,

Stefan

post54223: Re: QNX 6.5.0 installation and HDD with already allocated partitions

2010-05-11T17:04:37Z

Great. I'll take a look.

Thanks,

Keith Russell

On 10-05-11 12:55 , "Mike Gorchak" <community-noreply@qnx.com> wrote:

>> Can you let me know what hardware this was on? Please attach the output of

>> pci

>> -v.

>

> The platform is VMWare 7.0.1 build 227600. Output of pci -v is attached in

> archive.

>

>> Also please attach the output of "fdisk /dev/hd0 info" and "fdisk /dev/hd0

>> show" (assuming your dealing with the first hard drive).

>

> Output of fdisk info and fdisk show is also attached in archive. But I deleted

> all partitions to install 6.5.0 M9.

>

> It is easy to reproduce this problem, I checked this few minutes before. Just

> create two small partitions of any size on your HDD, for example, with type

> 179 and type 177. And then try to install 6.5.0 M9 using partition type 178 to

> the third available partition.

>

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post54217

post54217: Re: QNX 6.5.0 installation and HDD with already allocated partitions

2010-05-11T16:55:45Z

> Can you let me know what hardware this was on? Please attach the output of pci

> -v.

The platform is VMWare 7.0.1 build 227600. Output of pci -v is attached in archive.

> Also please attach the output of "fdisk /dev/hd0 info" and "fdisk /dev/hd0

> show" (assuming your dealing with the first hard drive).

Output of fdisk info and fdisk show is also attached in archive. But I deleted all partitions to install 6.5.0 M9.

It is easy to reproduce this problem, I checked this few minutes before. Just create two small partitions of any size on your HDD, for example, with type 179 and type 177. And then try to install 6.5.0 M9 using partition type 178 to the third available partition.

post54093: Re: QNX 6.5.0 installation and HDD with already allocated partitions

2010-05-10T18:30:13Z

Hi Mike,

Could you give me some more info so I can help diagnose what went wrong?

To obtain this information you will have to boot and run from the 6.5.0 CD.

Can you let me know what hardware this was on? Please attach the output of pci -v.

Also please attach the output of "fdisk /dev/hd0 info" and "fdisk /dev/hd0 show" (assuming your dealing with the first hard drive).

Thanks,

Keith Russell

post54020: Re: QNX 6.5.0 installation and HDD with already allocated partitions

2010-05-10T10:28:46Z

Hi,

This will not help you but I get also this problem with 6.5.0 M9 when I tried to install it on an HDD with some partition.

I don't know also if we are here on the right project.

Regards,

Chrstophe

post53835: QNX 6.5.0 installation and HDD with already allocated partitions

2010-05-08T17:44:41Z

I had this partition layout on my HDD:

1) QNX 6.4.1 (QNX6FS, type 179) (40000Mb)

2) Solaris 10 (type 191) (60000Mb)

3) free (rest free space is > 200Gb)

4) free

When I tried to install QNX 6.5.0 M9 to the partition 3) with type 178, the installation was terminated with the error "Can't mount /dev/hd0t178". After this QNX 6.4.1 partition 1) was lost and became "unformatted" (no files, no QNX6FS filesystem structure, etc).

post53429: Re: 6.5.0 M8A - apic boot issues

2010-05-03T15:31:40Z

i've got the same problem here. did you get any further? any hints from anybody?

post53159: Re: QNX 6.5.0 & net-snmp

2010-04-29T13:58:45Z

We are performing tests and playing little bit with current version

(5.4.2.1). We are trying to be able to generate traps without loading our

own module into net-snmp to be able to produce core file for analyzing. In

case we use our module, I think you will not be able to analyze core without

all needed libs and other files we are using. Or am I wrong?

Another question: How can I send some generic trap to trapsink destination

specified in snmpd.conf file via command tool? Just to see, whether net-snmp

will crash or not?

For a different type of testing:

Is there any place we can get binaries for net-snmp (5.4.2.1 or 5.5.) which

are compiled with "notification" and "target" modules under QNX 6.4.0? Just

to figure out, whether we have problems with our modules own snmp modules or

it is net-snmp problem?

Thanks

Adrian

2010/4/22 Sean Boudreau <community-noreply@qnx.com>

> On Wed, Apr 21, 2010 at 10:31:43AM -0400, Adrian Gafrik wrote:

> > The problem we faced is related to QNX 6.4.1. In this release we

> compiled net-snmp from sources with QNX releated patches.

> >

> > As I mentioned before in post, in case we compiled net-snmp without

> "notification" and "target" modules, net-snmp was working stable and able to

> send traps to destinations defined in net-snmp configuration file.

> >

> > When we compiled it with these 2 modules, net-snmp crashes and is no more

> able to send any trap to destinations specified in net-snmp configuration

> file.

> >

> > Therefore I would like to ask, whether somebody had similar problem with

> net-snmp (5.4.2.1)? In case somebody managed to run net-snmp without problem

> I will appreciate any advice which can help us.

>

> Can you build version 5.5 as described here:

>

>

> http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Netsnmp_wiki_page

>

> Do a 'make CCOPTS=-O0 DEBUG=-g' and attach the core file.

>

> Thanks,

>

> -seanb

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post52376

>

>

post52376: Re: QNX 6.5.0 & net-snmp

2010-04-22T13:29:17Z

On Wed, Apr 21, 2010 at 10:31:43AM -0400, Adrian Gafrik wrote:

> The problem we faced is related to QNX 6.4.1. In this release we compiled net-snmp from sources with QNX releated patches.

>

> As I mentioned before in post, in case we compiled net-snmp without "notification" and "target" modules, net-snmp was working stable and able to send traps to destinations defined in net-snmp configuration file.

>

> When we compiled it with these 2 modules, net-snmp crashes and is no more able to send any trap to destinations specified in net-snmp configuration file.

>

> Therefore I would like to ask, whether somebody had similar problem with net-snmp (5.4.2.1)? In case somebody managed to run net-snmp without problem I will appreciate any advice which can help us.

Can you build version 5.5 as described here:

http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Netsnmp_wiki_page

Do a 'make CCOPTS=-O0 DEBUG=-g' and attach the core file.

Thanks,

-seanb

post52240: Re: QNX 6.5.0 & net-snmp

2010-04-21T14:31:43Z

The problem we faced is related to QNX 6.4.1. In this release we compiled net-snmp from sources with QNX releated patches.

As I mentioned before in post, in case we compiled net-snmp without "notification" and "target" modules, net-snmp was working stable and able to send traps to destinations defined in net-snmp configuration file.

When we compiled it with these 2 modules, net-snmp crashes and is no more able to send any trap to destinations specified in net-snmp configuration file.

Therefore I would like to ask, whether somebody had similar problem with net-snmp (5.4.2.1)? In case somebody managed to run net-snmp without problem I will appreciate any advice which can help us.

Thanks

Adrian

post50985: Re: QNX 6.5.0 & net-snmp

2010-03-31T17:15:01Z

The subject says "6.5.0" but body refers to 6.4.1.

Could you, please, clarify which one is right?

If you used 6.5.0, which milestone?

Thank you,

Aleksandar

On 31/03/2010 11:53, Adrian Gafrik wrote:

> We ported customer application (Win based) to Linux and QNX. We decided to use net-snmp for both platforms. On Linux everything works fine, with QNX (6.4.1) we have problem.

>

> We compiled the net-snmp (5.4.2.1) under QNX from sources. But in case we compiled with "notification" and "target" modules (needed for our implementation) the net-snmp crashes when trying to send a trap.

>

> Is there somebody with similar problems?

>

>

>

> _______________________________________________

>

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post50975

>

post50975: Re: QNX 6.5.0 & net-snmp

2010-03-31T15:53:54Z

We ported customer application (Win based) to Linux and QNX. We decided to use net-snmp for both platforms. On Linux everything works fine, with QNX (6.4.1) we have problem.

We compiled the net-snmp (5.4.2.1) under QNX from sources. But in case we compiled with "notification" and "target" modules (needed for our implementation) the net-snmp crashes when trying to send a trap.

Is there somebody with similar problems?

post50969: Re: QNX 6.5.0 & net-snmp

2010-03-31T15:27:33Z

On Wed, Mar 31, 2010 at 11:23:47AM -0400, Adrian Gafrik wrote:

> Hi,

> just would like to ask, whether net-snmp (and which version) is included in QNX 6.5.0?

>

No, but I'd be interested in hearing about your interest / use

case.

Regards,

-seanb

post50967: QNX 6.5.0 & net-snmp

2010-03-31T15:23:46Z

Hi,

just would like to ask, whether net-snmp (and which version) is included in QNX 6.5.0?

Thanks

Adrian

post50529: Re: startup-apic + devnp-e1000 - DHCP doesn't work on booting

2010-03-26T12:22:49Z

I think this is probably similar (if not identical) to PR75103. Can you please get the latest pci-bios-v2 and see if this resolves the issue.

post50088: interrupt sharing or not - expected behaviour with APIC support?

2010-03-22T10:26:07Z

Hi,

AFAIK one of the biggest benefits of 6.5 having APIC support is that the limit of 0xf interrupts is gone so we don't have these issues with shared interrupts (added latency, etc.) any more.

What is the expected behaviour of a system with enabled APIC support? Somewhere I read that the probability of having shared interrupts gets smaller - why is it not completely eliminated?

On my test system, with APIC support I see indeed much less shared interrupts (cool!), but I still see interrupt vector 0x10 used for io-usb AND io-display. Is this expected?

- Malte

post50087: startup-apic + devnp-e1000 - DHCP doesn't work on booting

2010-03-22T10:21:15Z

Hi,

got a weird behaviour on an x86 here. Using standard boot image, it works, but when I change to startup-apic + pci-bios-v2, the following happens:

* upon boot, the NIC doesn't receive an DHCP address

* opening phlip, it has flipped to 'Manual' although previously it was on 'DHCP'

* switching it back to 'DHCP' it does aquire an IP address after a few seconds without problems

* networking functions just fine then.

Regards,

- Malte

post50047: RE: Photon issues w. startup-apic

2010-03-19T18:38:30Z

Hi Mike,

Thanks for the reply.

It was running SMP. Rebuilt an image using startup-apic and procnto-instr. Same result - black screen, but also...

Very slow to login - it looks like io-usb is sucking up a *lot* of CPU. With 2 CPUs, I had an unused one, so no slow down.

So, no cigar yet, but it yielded a nice clue...

Regards

Dave

________________________________

From: Michael Van Reenen [mailto:community-noreply@qnx.com]

Sent: Fri 3/19/2010 10:11 AM

To: sdpprereleases-community

Subject: RE: Photon issues w. startup-apic

My first guess from the messages below would be that the driver isn't

getting interrupts but can't say why..

Is this multi-core?  I apologize for my ignorance but if its possible -

can it run single-core as a test?  Just thinking out-loud.

------

Mike

-----Original Message-----

From: Dave Bott [mailto:community-noreply@qnx.com]

Sent: March 19, 2010 1:01 PM

To: sdpprereleases-community

Subject: Photon issues w. startup-apic

Neutrino install works fine from the M9 CD on an ECS-M3 motherboard

Graphics setup works - select i830 driver, 1280x1024, 60Hz. all good.

[Also tried using gma9xx with similar results]

With startup-bios, all is well.

However, if I use startup-apic and pci-bios-v2:

On reboot, screen goes black.

System is not dead though...

If I telnet in, I can see this from sloginfo:

Mar 19 17:04:40    1     8     0 phfont.so: init...

Mar 19 17:04:40    1     8     0 phfont.so: initialized.

Mar 19 17:04:40    1     8     0 phfont.so: '/dev/phfont[<32|64>]'

server installed.

Mar 19 17:04:40    6     8     0 VGA primary : bus 0x0 dev/func 0x10

Mar 19 17:04:40    6     8     0 Found 1 PCI/AGP display devices

Mar 19 17:04:40    6     8     0 pci_init: found PCI device 8086:2772

Mar 19 17:04:42    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:42    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:43    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:43    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:44    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:44    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:45    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:45    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:46    2     8     0 MsgReceive: Connection timed out

[lots more of this message]

So it looks like something is not quite right...

The log with the gma9xx driver is:

Mar 19 17:11:26    1     8     0 phfont.so: init...

Mar 19 17:11:26    1     8     0 phfont.so: initialized.

Mar 19 17:11:26    1     8     0 phfont.so: '/dev/phfont[<32|64>]'

server installed.

Mar 19 17:11:26    6     8     0 VGA primary : bus 0x0 dev/func 0x10

Mar 19 17:11:26    6     8     0 Found 1 PCI/AGP display devices

Mar 19 17:11:26    6     8     0 pci_init: found PCI device 8086:2772

Mar 19 17:11:26    6     8     0 Could not open config file "": No such

file or directory

Mar 19 17:11:26    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:27    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:27    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:28    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:28    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:29    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post50039

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post50040

post50040: RE: Photon issues w. startup-apic

2010-03-19T17:11:04Z

My first guess from the messages below would be that the driver isn't

getting interrupts but can't say why..

Is this multi-core?  I apologize for my ignorance but if its possible -

can it run single-core as a test?  Just thinking out-loud.

------

Mike

-----Original Message-----

From: Dave Bott [mailto:community-noreply@qnx.com]

Sent: March 19, 2010 1:01 PM

To: sdpprereleases-community

Subject: Photon issues w. startup-apic

Neutrino install works fine from the M9 CD on an ECS-M3 motherboard

Graphics setup works - select i830 driver, 1280x1024, 60Hz. all good.

[Also tried using gma9xx with similar results]

With startup-bios, all is well.

However, if I use startup-apic and pci-bios-v2:

On reboot, screen goes black.

System is not dead though...

If I telnet in, I can see this from sloginfo:

Mar 19 17:04:40    1     8     0 phfont.so: init...

Mar 19 17:04:40    1     8     0 phfont.so: initialized.

Mar 19 17:04:40    1     8     0 phfont.so: '/dev/phfont[<32|64>]'

server installed.

Mar 19 17:04:40    6     8     0 VGA primary : bus 0x0 dev/func 0x10

Mar 19 17:04:40    6     8     0 Found 1 PCI/AGP display devices

Mar 19 17:04:40    6     8     0 pci_init: found PCI device 8086:2772

Mar 19 17:04:42    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:42    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:43    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:43    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:44    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:44    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:45    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:45    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:46    2     8     0 MsgReceive: Connection timed out

[lots more of this message]

So it looks like something is not quite right...

The log with the gma9xx driver is:

Mar 19 17:11:26    1     8     0 phfont.so: init...

Mar 19 17:11:26    1     8     0 phfont.so: initialized.

Mar 19 17:11:26    1     8     0 phfont.so: '/dev/phfont[<32|64>]'

server installed.

Mar 19 17:11:26    6     8     0 VGA primary : bus 0x0 dev/func 0x10

Mar 19 17:11:26    6     8     0 Found 1 PCI/AGP display devices

Mar 19 17:11:26    6     8     0 pci_init: found PCI device 8086:2772

Mar 19 17:11:26    6     8     0 Could not open config file "": No such

file or directory

Mar 19 17:11:26    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:27    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:27    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:28    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:28    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

Mar 19 17:11:29    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free =

4038

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post50039

post50039: Photon issues w. startup-apic

2010-03-19T17:01:05Z

Neutrino install works fine from the M9 CD on an ECS-M3 motherboard

Graphics setup works - select i830 driver, 1280x1024, 60Hz. all good.

[Also tried using gma9xx with similar results]

With startup-bios, all is well.

However, if I use startup-apic and pci-bios-v2:

On reboot, screen goes black.

System is not dead though...

If I telnet in, I can see this from sloginfo:

Mar 19 17:04:40    1     8     0 phfont.so: init...

Mar 19 17:04:40    1     8     0 phfont.so: initialized.

Mar 19 17:04:40    1     8     0 phfont.so: '/dev/phfont[<32|64>]' server installed.

Mar 19 17:04:40    6     8     0 VGA primary : bus 0x0 dev/func 0x10

Mar 19 17:04:40    6     8     0 Found 1 PCI/AGP display devices

Mar 19 17:04:40    6     8     0 pci_init: found PCI device 8086:2772

Mar 19 17:04:42    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:42    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:43    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:43    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:44    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:44    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:45    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:45    2     8     0 MsgReceive: Connection timed out

Mar 19 17:04:46    2     8     0 MsgReceive: Connection timed out

[lots more of this message]

So it looks like something is not quite right...

The log with the gma9xx driver is:

Mar 19 17:11:26    1     8     0 phfont.so: init...

Mar 19 17:11:26    1     8     0 phfont.so: initialized.

Mar 19 17:11:26    1     8     0 phfont.so: '/dev/phfont[<32|64>]' server installed.

Mar 19 17:11:26    6     8     0 VGA primary : bus 0x0 dev/func 0x10

Mar 19 17:11:26    6     8     0 Found 1 PCI/AGP display devices

Mar 19 17:11:26    6     8     0 pci_init: found PCI device 8086:2772

Mar 19 17:11:26    6     8     0 Could not open config file "": No such file or directory

Mar 19 17:11:26    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free = 4038

Mar 19 17:11:27    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free = 4038

Mar 19 17:11:27    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free = 4038

Mar 19 17:11:28    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free = 4038

Mar 19 17:11:28    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free = 4038

Mar 19 17:11:29    6     8     0 MsgReceive IDLE 37fffc0 a8 a8 free = 4038

post49605: Re: 6.5.0 M8A - apic boot issues

2010-03-16T14:24:43Z

I tried 6.5.0 M8A on a dual Xeon server with SMP, startup-acpi and pci-bios-v2. It didn't go anywhere other than outputing something like "found three IOAPIC, but can only configure one of them" first, then AHCI couldn't find the hard disk, IDE couldn't find the optical drive...

post49326: 6.5.0 M8A - apic boot issues

2010-03-11T21:13:20Z

Hi,

A customer of mine has some high-end (8-way) machines and wants to use MSI interrupts to reduce latencies (specifically by not sharing interrupts any more). He has a bunch of GigE NICs to service at high packet rates.

He has M8A and is using startup-apic and pci-bios-v2 (and an experimental version of pci-bios-v2).

He had limited success, but provided feedback that is hopefully of value to us. He is available to test more code...

To make anything that booted at all, he mixed some 6.4.1 and 6.5.0 components...

Here's what he says: plus I attached his results

"

After a bunch of experiments I have mixed (some positive and some

negative results).

I manage to create operational APCI IFS, which consisted of

combination of 6.4.1 and 6.5.0A components. Specifically, I "borrow"

from 6.5.0: startup-apic, pci-bios-v2, libc.so, and libc.so.3.

Unfortunately, this IFS works only on one out of 5 types of machines

we have. Other four -- they crash during startup. I attached the

snapshots of several outputs from different PCs. Hopefully, it

contains useful information to QNX BSP and kernel developers. Again,

it is not clean setup (mixture of 6.4.1 and 6.5.0). Thought, it works

on one of the System. I didn't conduct any experiments with this

runtime environment, but, at least, two boxes can communicate over the

network.

Yesterday, I mentioned to you that pci-bios-v2 hangs the System. When

I took this components from 6.5.0 and tried to run the IFS, ldd

complained about lack of "__slog_once" symbol in pci-bios-v2. So, I

have to take libc.so.3 from 6.5.0 as well.

"

Is this any help ?

Any suggestions ? I've asked him to see if reducing the cores to 8 helps...

Regards

Dave

ave

post48729: issue with libc-lazybind.tar M8 experimental

2010-03-03T16:59:23Z

Hello,

The published binary has a bug that affects some applications. Namely the applications that do something like dlopen("libc.so.3",...). This causes photon to appear stuck on the "detecting input devices" screen.

A workaround is to touch file "/etc/system/config/nophoton", boot to text mode and start photon from there.

Thanks,

Aleksandar

post48631: Sources of x86 BSP with msi/apic support

2010-03-02T17:00:18Z

The newly released QNXSDP-6.5.0 (Alpha), seems, uses modified version of BSP, which provides support of MSI and APIC. If sources of this new BSP (I am interested specifically in x86 BIOS version) are available? If yes, then where I could take them from?

Thank you.

post39646: Re: 6.4.1 M4 annoying messages in the system log

2009-10-08T20:24:57Z

I get the same sloginfo. My Ethernet is not working correctly. I can ping other hosts and packets and bytes are reported transmitted (and are received by the hosts). The responses from the hosts fail though, packets are reported received, but no bytes are received (nicinfo output)

post30474: Re: abort() in 6.4.1

2009-06-01T21:44:18Z

Yes You are right Colin.

post30408: Re: abort() in 6.4.1

2009-06-01T13:28:59Z

What's the bug?  That's exactly what is supposed to happen!

bogdan celer wrote:

> Colin abort() not works.

> I'am testing abort using examples from Neutrino Library References.

> prg1.c:

> #inclede <stdlib.h>

>  int main( void )

> {

>    int major_error = 1;

>    if( major_error )

>        abort();

>    /* You'll never get here. */

>    return EXIT_SUCCESS;

> }

>

> results is the same:

> gcc -o prg1 prg1.c

> ./prg1

> Abort (core dumped)

>

> _______________________________________________

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post30395

>

--

cburgess@qnx.com

post30395: Re: abort() in 6.4.1

2009-06-01T06:16:10Z

Colin abort() not works.

I'am testing abort using examples from Neutrino Library References.

prg1.c:

#inclede <stdlib.h>

int main( void )

{

   int major_error = 1;

   if( major_error )

       abort();

   /* You'll never get here. */

   return EXIT_SUCCESS;

}

results is the same:

gcc -o prg1 prg1.c

./prg1

Abort (core dumped)

post30389: Re: abort() in 6.4.1

2009-05-31T20:29:56Z

abort() works just fine - it's just that gdb is trapping the signal before it gets delivered to the process. Check whether SIGABRT is passed to the client process by default - info signal SIGABRT will tell you, and handle signal SIGABRT will let you specify the specifics of the signal handling.

post30388: Re: abort() in 6.4.1

2009-05-31T19:10:46Z

On QNX6.4.1 release nothing changed.

abort() does not work.

post30354: Re: RE: Probably application builder bug

2009-05-29T17:52:14Z

It seems that the bug was fixed in the final 6.4.1

post30122: Re: PtBasic error in 6.4.1 Pre-release Version

2009-05-27T12:19:12Z

That is correct, here is the release note for PR24980:

If you set a widget's Pt_ARG_HIGHLIGHT_ROUNDNESS resource to a nonzero value, the widget's gradient fill is now bypassed instead of remaining rectangular.

post30110: PtBasic error in 6.4.1 Pre-release Version

2009-05-27T07:16:57Z

Rounded widget PtBasic loses its fill color (becomes transparent) in this

combination of its resources :

    another fill color (Pt_ARG_FILL_COLOR) then transparent

    not flat fill  (basic flags)

    Pt_ARG_HIGHLIGHT_ROUNDNESS greater then 0

Required color is drawn only in place of  bevel border.

post29981: Re: RE: Probably application builder bug

2009-05-25T20:13:31Z

How can I get m6? If I could I can check.

post29943: RE: Probably application builder bug

2009-05-25T14:47:05Z

Can you provide more details:

- Procedure how to repeat

- Sample application

- Does the problem happen in M6? M5 is now out of date.

Thanks,

Max

-----Original Message-----

From: Piotr Trojanek [mailto:community-noreply@qnx.com]

Sent: Sunday, May 24, 2009 10:21 AM

To: sdpprereleases-community

Subject: Probably application builder bug

The application builder applications called from the command line cause

the following error under 641M5:

Ap: Unable to open resource file

(/net/host_name.domain_name/)

The same code works fine under 641M4

best regards

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post29918

post29918: Probably application builder bug

2009-05-24T14:20:35Z

The application builder applications called from the command line cause the following error under 641M5:

Ap: Unable to open resource file

(/net/host_name.domain_name/)

The same code works fine under 641M4

best regards

post29801: Re: Migration from QNX 6.2 to 6.4.1

2009-05-21T07:52:34Z

Thanks for the information!

post29680: Neutrino 6.3 - sin source code?

2009-05-19T15:40:04Z

I'm currently debugging an issue with sin communicating with an application in Neutrino 6.3. It would be helpful to see the source code, though the version posted in the repositories is for QNX 4. Is anyone able to provide Neutrino source code for 'sin'?

post29599: abort() in 6.4.1

2009-05-17T09:45:51Z

a little prg2.c

#include <stdio.h>

#include <stdlib.h>

char buffer[1000];

int main()

{

long long b, a = -0x3AFAFAFAFAFAFAFALL;

int i;

   for( i = 0; i < 100; ++i )

      buffer[i] = '0';

   sprintf (buffer, "%llu", a);

   sscanf (buffer, "%llu", &b);

   printf( "a      = %llu \n", a );

   printf( "buffer = %s \n", buffer );

   printf( "b      = %llu \n", b );

   abort();

}

qcc/gcc -o prg2 prg2.c

# ./prg2

a      = -4249985154237004538

buffer = -4249985154237004538

b      = -4249985154237004538

Abort (core dumped)

# gdb prg2

GNU gdb 6.8 qnx-nto (rev. 297)

Copyright (C) 2008 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

and "show warranty" for details.

This GDB was configured as "i386-pc-nto-qnx6.4.0"...

(gdb) start

Temporary breakpoint 1 at 0x8048701: file prg2.c, line 6.

Starting program: /home/GCC/4.4/prg2

Temporary breakpoint 1, main () at prg2.c:6

6        long long b, a = -0x3AFAFAFAFAFAFAFALL;

(gdb) b 11

Breakpoint 2 at 0x804872b: file prg2.c, line 11.

(gdb) c

Continuing.

Breakpoint 2, main () at prg2.c:11

11         sprintf (buffer, "%lld", a);

(gdb) s

12         sscanf (buffer, "%lld", &b);

(gdb)

13         printf( "a      = %lld \n", a );

(gdb)

a      = -4249985154237004538

14         printf( "buffer = %s \n", buffer );

(gdb)

buffer = -4249985154237004538

15         printf( "b      = %lld \n", b );

(gdb)

b      = -4249985154237004538

16         abort();

(gdb)

Program received signal SIGABRT, Aborted.

0xb033da61 in SignalKill () from /usr/qnx641/target/qnx6/x86/lib/libc.so.3

(gdb)

Single stepping until exit from function SignalKill,

which has no line number information.

Program exited normally.

(gdb)

And in /var/dumps I see prg2.core

Why ????

post28877: Re: Migration from QNX 6.2 to 6.4.1

2009-05-07T12:00:04Z

Hi,

> The help contents in QNX SDP 6.4.1 (For Windows) talks about migration from 6.

> 3 to 6.4.1 and from 6.4.0 to 6.4.1. I could not find information about

> migration from QNX 6.2 (IDE 2.0) to 6.4.1 (IDE 4.6.0).

That's correct. You will also note that there is no info on migrating from 6.1 to 6.4, or 6.1 to 6.3, or 6.0 to 6.2, etc. The reason is that it would simply be too much work to provide such information.

> Can somebody provide a guide on how to get started with migration from 6.2 to

> QNX SDP 6.4.1?

First you have to find a BSP for 6.4 that runs on your hardware. If you need to port the BSP (not only your applications), you need a 6.4 BSP similar to your hardware.

Begin migrating drivers one by one, try to compile them. If errors come up, refer to migration notes 6.2 to 6.3 first, if it doesn't work, look in 6.3 to 6.4 info. Also with failing function calls, consult the documentation.

There is an alternative: QNX offers Consulting Services for porting. A QNX engineer (or several) could visit you for a week or so and help porting. Your QNX Sales Representative can tell you what the cost for this would be.

- Malte

post28865: 6.4.1 M4 annoying messages in the system log

2009-05-07T05:47:13Z

May 07 08:37:54    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:37:57    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:00    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:03    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:06    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:09    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:12    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:15    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:18    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:21    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:24    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:27    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:30    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:33    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:36    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:39    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:42    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:45    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:48    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:51    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:54    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:38:57    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:00    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:03    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:06    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:12    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:15    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:18    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

May 07 08:39:21    2    14     0 devn-speedo: speedo_MDI_MonitorPhy(): calling MDI_MonitorPhy()

post28527: Re: textto utility on 6.4.1 M4

2009-05-01T16:51:00Z

Thank you for your report. I filed PR68072

Regards,

Ryan Mansfield

post28446: Re: RE: 6.4.1 Milestone 5 packages now available

2009-04-30T14:22:48Z

I've attached a rough set of differences between the release notes for M4 and M5. As I mentioned earlier, this list might not accurately reflect the changes to the software between M4 and M5.

post28417: Migration from QNX 6.2 to 6.4.1

2009-04-30T09:55:37Z

Hello,

The help contents in QNX SDP 6.4.1 (For Windows) talks about migration from 6.3 to 6.4.1 and from 6.4.0 to 6.4.1. I could not find information about migration from QNX 6.2 (IDE 2.0) to 6.4.1 (IDE 4.6.0).

Can somebody provide a guide on how to get started with migration from 6.2 to QNX SDP 6.4.1?

Thanks

Sunil

post28402: Re: RE: 6.4.1 Milestone 5 packages now available

2009-04-29T20:20:50Z

It would be good. Thanks in advance.

post28401: RE: 6.4.1 Milestone 5 packages now available

2009-04-29T20:01:49Z

The release notes are intended more for the final release than for the

milestone builds, so the differences between the M4 and M5 notes might

not be very useful, and likely wouldn't reflect all the changes to the

software between M4 and M5. If you still want a list of the changes, I

can generate one tomorrow (I still have some docs to finish for

tonight's build).

Steve Reid (stever@qnx.com)

Technical Editor

QNX Software Systems

post28394: Re: 6.4.1 Milestone 5 packages now available

2009-04-29T19:34:53Z

Is it possible to get diff of release notes between M4 and M5 ?

post28392: Re: Invalid recursive tan(float) C++ declaration on 6.4.1 M4

2009-04-29T19:29:51Z

Mike Gorchak wrote:

> Just compile it and run:

>

> #include <math.h>

>

> int main()

> {

> tan(0.5f);

>

> return 0;

> }

>

> Compile it using:

> g++ tan.cpp -o tan

>

> or

>

> QCC tan.cpp -o tan -lstdc++

PR67786. It should be fixed in M6 (missed M5 by a few days).

Regards,

Ryan Mansfield

post28390: 6.4.1 Milestone 5 packages now available

2009-04-29T19:29:18Z

Hi folks,

We've updated the packages to our Milestone 5 build. The binary

installers can be retrieved from here: QNX Download Center

<http://www.qnx.com/download/group.html?programid=19337>

Thanks

Mike

post28389: Invalid recursive tan(float) C++ declaration on 6.4.1 M4

2009-04-29T19:27:36Z

Just compile it and run:

#include <math.h>

int main()

{

tan(0.5f);

return 0;

}

Compile it using:

g++ tan.cpp -o tan

or

QCC tan.cpp -o tan -lstdc++

post28301: textto utility on 6.4.1 M4

2009-04-29T06:37:25Z

textto utility now appends two 0xFF 0xFF symbols at the end of the converted file (direction of conversion doesn't matter CRLF to LF or LF to CRLF).

post27952: Re: signal priorities issue

2009-04-24T07:16:57Z

Colin, thank You for reply.

Yes, after I corrected error that You spotted, program works rightly.

But it is ruefully that POSIX allows so free interpretation of it’s regulations. That’s why it is advisable add requirement of RT signals blocking using sigaction sa_mask in sigqueue() help topic. It may prevent errors while porting programs from other POSIX oriented RTOS (Lynx OS for example, as I mentioned in previous post).

Yours sincerely ,

Oleg.

post27931: Re: signal priorities issue

2009-04-23T19:36:46Z

I spotted the error in s5_sighandler.c - it's clearing the sa_mask value of the sigaction.

That means that no signals are masked during the execution of the signal handler.

Setting the sa_mask correctly produces the expected results from the UNP book.

Cheers,

Colin

Oleg Nikolsky wrote:

> Colin Burgess, thank You for reply.

>

> I understood Your explanation, maybe not quite perfectly. So I have some questions and objections.

>

> 1. If signals are ‘stacked’, it seems they must be delivered in strictly reverse order, i.e.

> Sent:

> signal sent: 56 with val = 0

> signal sent: 56 with val = 1

> signal sent: 56 with val = 2

> signal sent: 55 with val = 0

> signal sent: 55 with val = 1

> signal sent: 55 with val = 2

> signal sent: 54 with val = 0

> signal sent: 54 with val = 1

> signal sent: 54 with val = 2

> …

> Received:

> received signal 56 code = -2 val = 2

> received signal 56 code = -2 val = 1

> received signal 56 code = -2 val = 0

> received signal 55 code = -2 val = 2

> received signal 55 code = -2 val = 1

> received signal 55 code = -2 val = 0

> received signal 54 code = -2 val = 2

> received signal 54 code = -2 val = 1

> received signal 54 code = -2 val = 0

> …

> Am I right?

>

> 2. You explained internal procedure of signal delivery. From programmer’s point of view, based on help documentation, this procedure is not evident.

> 3. In accordance with Murphy's law "Whatever can go wrong will go wrong, and at the worst possible time, in the worst possible way." Concerning signals, programmer’s mistakes may occur due to the fact that some people interpret POSIX defined real-time signals delivery order in other way as compared with QNX Neutrino implementation. For example, W. Richard Stevens in his book “UNIX Network Programming. Volume 2. Interprocess Communications” consider signal delivery order like demonstrate QNX Neutrino caused probably by error in Solaris 2.6. Another example – both programs from my attachment (with the smallest changes) being launched under Lynx OS shows strictly order of delivery from small to big signal numbers.

>

> 4. So it is desirable to have neatly stated QNX Neutrino implementation of signal delivery order in help documentation.

>

> 5. Don’t consider my post as aimed against QNX Neutrino. It is very good RTOS! We use it in student training for several years.

>

> 6. I apologize for my bad poor English.

>

> Oleg.

>

> _______________________________________________

> QNX Software Development Platform Pre-Releases

> http://community.qnx.com/sf/go/post27915

--

cburgess@qnx.com

post27915: Re: signal priorities issue

2009-04-23T17:28:17Z

Colin Burgess, thank You for reply.

I understood Your explanation, maybe not quite perfectly. So I have some questions and objections.

1. If signals are ‘stacked’, it seems they must be delivered in strictly reverse order, i.e.

Sent:

signal sent: 56 with val = 0

signal sent: 56 with val = 1

signal sent: 56 with val = 2

signal sent: 55 with val = 0

signal sent: 55 with val = 1

signal sent: 55 with val = 2

signal sent: 54 with val = 0

signal sent: 54 with val = 1

signal sent: 54 with val = 2

…

Received:

received signal 56 code = -2 val = 2

received signal 56 code = -2 val = 1

received signal 56 code = -2 val = 0

received signal 55 code = -2 val = 2

received signal 55 code = -2 val = 1

received signal 55 code = -2 val = 0

received signal 54 code = -2 val = 2

received signal 54 code = -2 val = 1

received signal 54 code = -2 val = 0

…

Am I right?

2. You explained internal procedure of signal delivery. From programmer’s point of view, based on help documentation, this procedure is not evident.

3. In accordance with Murphy's law "Whatever can go wrong will go wrong, and at the worst possible time, in the worst possible way." Concerning signals, programmer’s mistakes may occur due to the fact that some people interpret POSIX defined real-time signals delivery order in other way as compared with QNX Neutrino implementation. For example, W. Richard Stevens in his book “UNIX Network Programming. Volume 2. Interprocess Communications” consider signal delivery order like demonstrate QNX Neutrino caused probably by error in Solaris 2.6. Another example – both programs from my attachment (with the smallest changes) being launched under Lynx OS shows strictly order of delivery from small to big signal numbers.

4. So it is desirable to have neatly stated QNX Neutrino implementation of signal delivery order in help documentation.

5. Don’t consider my post as aimed against QNX Neutrino. It is very good RTOS! We use it in student training for several years.

6. I apologize for my bad poor English.

Oleg.

post27525: Re: signal priorities issue

2009-04-20T18:38:21Z

consider thread a that has two signals pending SIGRTMIN and SIGRTMAX, but blocked.

Now unblock them. This causes the signals to be queued for delivery, in signal number order.

As thread a exits the kernel, the signal handler for SIGRTMIN is setup to run. But as the kernel

is in the process of making the thread ready, it then 'delivers' the second signal, SIGRTMAX

to the thread, which queues up the handler for that signal, and so on.

Thus the signal handlers 'stack', and effectively execute in reverse order.

--

cburgess@qnx.com

post27443: signal priorities issue

2009-04-19T12:57:35Z

Realtime signals help information should be more accurate.

As stated in help topic on sigqueue() function, “Should any of multiple pending signals in the range SIGRTMIN to SIGRTMAX be selected for delivery, the lowest numbered one is delivered.”   This assertion complies with POSIX Realtime Signal Concept (http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html): “When multiple unblocked signals, all in the range SIGRTMIN to SIGRTMAX, are pending, the behavior shall be as if the implementation delivers the pending unblocked signal with the lowest signal number within that range. No other ordering of signal delivery is specified. If, when a pending signal is delivered, there are additional signals queued to that signal number, the signal shall remain pending. Otherwise, the pending indication shall be reset.”

In fact, as shown in book “Цилюрик О., Горошко Е. QNX/UNIX: анатомия параллелизма. ISBN 5-93286-088-X” (http://www.symbol.ru/alphabet/357604.html ), QNX Neutrino behaves opposite manner (look at file s5.cc in archive pthread.tgz http://www.books.ru/library/qnx-unix/ ): while pending RT signals are delivered to process using signal handler function, signals with highest numbers are received first. I attach slightly changed simple program s5_sighandler.c that illustrates this behavior. The same order of signal delivery demonstrates sigsuspend() function in conjunction with signal handler function.

On the other hand,  if queued RT signals are not “delivered” but “accepted” (xsh_chap02_04.html  terminology) by process with sigwaitinfo() function, QNX Neutrino behaves in accordance with IEEE Std 1003.1, 2004 Edition - signals with lowest numbers are delivered first. This is illustrated by s5_sigwaitinfo.c program.

It seems to me that RT signal help documentation require some refinement:

1) Neatly distinguish signal delivery and accepting in help topics. Explain what does signal catching means every time this term appears in help topics.

2) Neatly describe the order of queued RT signals delivery and accepting as it is implemented by QNX Neutrino.

3) Neatly explain in sigwaitinfo() help topic that accepting signals must be blocked like it is written in sigwait() help topic.

4) Bring help topics on concrete functions to conformity with chapter “The QNX Neutrino Microkernel”. For example, in this chapter I read  “The POSIX standard includes the concept of queued realtime signals. QNX Neutrino supports optional queuing of any signal, not just realtime signals. The queuing can be specified on a signal-by-signal basis within a process. Each signal can have an associated 8-bit code and a 32-bit value.. . .  As a result, signals are delivered in priority order with lower signal numbers having higher priority. This conforms with the POSIX standard, which states that existing signals have priority over the new realtime signals. . . . The OS supports the 32 standard POSIX signals (as in UNIX) as well as the POSIX realtime signals, both numbered from a kernel-implemented set of 64 signals with uniform functionality. While the POSIX standard defines realtime signals as differing from UNIX-style signals (in that they may contain four bytes of data and a byte code and may be queued for delivery), this functionality can be explicitly selected or deselected on a per-signal basis, allowing this converged implementation to still comply with the standard. Incidentally, the UNIX-style signals can select POSIX realtime signal

queuing, if the application wants it.”

But help topic about sigqueue() function tells me:  “Should any of multiple pending signals in the range SIGRTMIN to SIGRTMAX be selected for delivery, the lowest numbered one is delivered. The selection order between realtime and nonrealtime signals, or between multiple pending nonrealtime signals, is unspecified.”

Attachment: file signals.tar.gz, containing  s5_sighandler.c  s5_sigwaitinfo.c programs.

post27179: Re: Is devg-gma9xx graphics driver well tested ?

2009-04-16T11:00:02Z

Just tested on 6.4.0. Output of the demo-alpha is the same as in 6.4.1 - just image with label "32 bit image with alpha mask" is missing. In it's place background is placed.

demo-chroma works fine on 6.4.0, so devg-gma9xx has some regression in the 6.4.1 M4.

All egl-* demos are not working in the 6.4.0 also, the same symptoms.

post27178: Is devg-gma9xx graphics driver well tested ?

2009-04-16T10:49:39Z

On 6.4.1 M4 (not tested it on 6.4.0 release) all egl-* demos are not working (blue or black screen in most cases or trash on the screen), even demo-alpha and demo-chrome are showing corrupted images (they are looking like when image stride is wrong).

Output of pci -vvvv is attached.

post27177: Magic 1440x900 video mode using devg-extreme2, devg-i830, devg-gma9xx drivers

2009-04-16T10:41:50Z

When application which uses GF library switches video mode in console to 800x600 (or 640x480), without photon, often 1440x900 video mode is set instead of 800x600. display.conf still contains 800x600, like it must be. Photon also starts in the 1440x900 and I can see 1440x900 video in the video modes list like one of the available video modes. But when I will switch video mode resolution to 800x600 under photon, this magic mode 1440x900 is missed in the list.

I can't reproduce this bug under devg-radeon and devg-tnt, only on devg-extreme2, devg-i830, devg-gma9xx drivers.

6.4.0 contains this bug also, but it was not too annoying, while under 6.4.1 M4, it appears every third mode switch.

post26747: Re: sin not work

2009-04-13T12:41:19Z

bogdan celer wrote:

> # sin

> Memory fault (core dumped)

> #

sin will be removed in 6.4.1.

Regards,

Ryan Mansfield

post26746: Re: Gcc 4.3.3 in QNX 6.4.1

2009-04-13T12:40:37Z

bogdan celer wrote:

> GCC4.3.3 requires the GMP and MPFR libraries for building all the various front-end languages it supports. But I don`t find in 6.4.1 this libraries.

> Did you build the gcc-4.3.3 compiler for QNX without these libraries ?

They are statically linked.

Regards,

Ryan Mansfield

post26722: Re: sin not work

2009-04-12T13:41:31Z

On Fri, Apr 10, 2009 at 02:04:46PM -0400, bogdan celer wrote:

> # sin

> Memory fault (core dumped)

Thanks, should be fixed shortly.

-seanb

post26680: sin not work

2009-04-10T18:04:45Z

# sin

Memory fault (core dumped)

#

post26668: Gcc 4.3.3 in QNX 6.4.1

2009-04-10T09:25:48Z

GCC4.3.3 requires the GMP and MPFR libraries for building all the various front-end languages it supports. But I don`t find in 6.4.1 this libraries.

Did you build the gcc-4.3.3 compiler for QNX without these libraries ?

post26493: RE: Welcome to the SDP 6.4.1 pre-release

2009-04-09T06:57:01Z

QDE was removed in QNX SDP 6.4.0, someone else will have to follow up with any changes (if any).

Regards,

-Derek

________________________________

From: Prem Mallappa [mailto:community-noreply@qnx.com]

Sent: Thu 09/04/2009 2:50 AM

To: sdpprereleases-community

Subject: Re: Welcome to the SDP 6.4.1 pre-release

no QDE (eclipse) in the pre-release?

that doesn't look good .

/Prem

_______________________________________________

QNX Software Development Platform Pre-Releases

http://community.qnx.com/sf/go/post26491

post26492: Re: Welcome to the SDP 6.4.1 pre-release

2009-04-09T06:52:08Z

sorry, forgot to say I tested in the NTO hosted environment

post26491: Re: Welcome to the SDP 6.4.1 pre-release

2009-04-09T06:50:45Z

no QDE (eclipse) in the pre-release?

that doesn't look good .

/Prem

post26139: Welcome to the SDP 6.4.1 pre-release

2009-04-06T20:27:14Z

Welcome to the QNX Software Development Platform 6.4.1 pre-release.

We have posted our Milestone 4 build (see the wiki page at http://community.qnx.com/sf/wiki/do/viewPage/projects.community/wiki/SDP_6.4.1) for feedback and questions. Questions or issues related to one of the technologies developed in SDP 6.4.1 can be handled through this forum or the corresponding technology project forums. However, dispatching may be more effective if using the latter.

Please bear in mind the terms of the license agreement that will be displayed when you install this software - this is not the commercial release, yet...

Thanks for participating in our pre-release program!