This is a bit off-topic, but: what is the state of QNX at the moment? Last 
time I have seen it, it came with a very poor X-Server interface which 
caused strange crashes. And it was not possible to compile and use a 
platform-independent GUI-toolkit like wxWidgets with QNX. Has this changes 
meanwhile or is QNX still a closed universe where all the necessary 
standards do not work?



Am Mittwoch, 9. März 2016 00:27:29 UTC+1 schrieb acheesehead:
>
> I just downloaded and built the latest 'experimental' QNX 6.6 BSP for BBB. 
> Got the same errors. Turns out that the permissions of files in 
> install/sbin and install/bin needed to change. Once I changed their 
> permissions, all goes well. The build script does not mount the SD card or 
> the eMMC, so that must be done manually.
>
> On Tuesday, March 1, 2016 at 3:00:18 PM UTC-7, Steven Hartmann wrote:
>>
>> I hope there is someone here successfully using QNX on the BBB.  I am 
>> currently doing a QNX evaluation and am having trouble with the BBB BSP.  I 
>> am using the BSP_ti-am335x-beaglebone_br-660_be-660_SVN797070_JBN574.zip 
>> BSP.  The package comes with a pre-built image, which boots up fine.  I 
>> have been able to do a few test programs with it, but now I need to modify 
>> the BSP to change which features are used.  The first step in doing this 
>> was to just recompile the BSP to make sure I can recreate the precompiled 
>> version.  The build goes fine and creates an image.  I can boot off the 
>> image, but it gives a lot of errors:
>>
>> U-Boot#  fatload mmc 0 81000000 ifs-ti-am335x-beaglebone.bin
>> reading ifs-ti-am335x-beaglebone.bin
>> 5794620 bytes read in 657 ms (8.4 MiB/s)
>> U-Boot# go 81000000
>> ## Starting application at 0x81000000 ...
>>
>> __________Board ID__________
>> header:  ee3355aa
>> name:    A335BNLT
>> ____________________________
>>     BeagleBone Black detected    
>>
>> VFPv3: fpsid=410330c3
>> coproc_attach(10): attach fe08a3fc (fe08ad24)
>> coproc_attach(11): attach fe08a3fc (fe08ad24)
>> Welcome to QNX Neutrino 6.6.0 on the Texas Instruments AM335x BeagleBone 
>> (ARMv7 Cortex-A8 core) - Board
>> Unable to start "devc-seromap" (2)
>> Unable to access "/dev/ser1" (2)
>> Unable to access "/dev/ser1" (2)
>> Starting MMC/SD driver...
>> Unable to start "devb-sdmmc-j5_generic" (2)
>> Unable to start "devb-sdmmc-j5_generic" (2)
>> starting I2C driver...
>> Unable to start "i2c-omap35xx-j5" (2)
>> Unable to access "/dev/i2c0" (2)
>> starting WDT reset utility...
>> Unable to start "dm814x-wdtkick" (2)
>> starting Board ID driver...
>> Unable to start "am335x-boardid" (2)
>> Unable to access "/dev/bdid" (2)
>> Setting OS Clock from on-board RTC
>> Unable to start "rtc" (2)
>> Sat Jan 01 00:00:15 GMT 2000
>> Starting USB OTG Host driver...
>> Starting SPI driver...
>> Unable to start "spi-master" (2)
>> Starting network driver...
>> starting leds driver...
>> Unable to start "am335x-leds" (2)
>> Unable to access "/dev/leds" (2)
>> Setting environment variables...
>> done.
>> Starting Screen Graphics...
>> done.
>> Starting HDMI Audio driver...
>> Unable to access /dev/snd/pcmC0D1p
>> ksh: No controlling tty (open /dev/tty: No such device or address)
>> ksh: warning: won't have full job control
>>
>>
>> All of the software that reports "unable to start" does not have execute 
>> permissions.  When I tried to add execute permissions by hand, it said the 
>> file did not exist.
>>
>> My build host is linux mint.
>>
>> Thanks!
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to