http://community.qnx.com/sf/discussion/do/listTopics/projects.graphics/discussion.advanced_graphics Posts for Advanced Graphics http://community.qnx.com/sf/go/post101196 I am trying to get Qt and QNX running on the Sabre Lite board. I have a Qt project (just a single button) and the project builds and loads to the target using the Momentics debugger. However, the first line of code that executes: QApplication a(argc, argv, global); Causes this error: QQnxScreen: gf_dev_attach() failed with error code 2 The error in the code says this: #define GF_ERR_IODISPLAY 0x00000002 /* error accessing io-display */ My board does not have an io-display process, and there is no /dev/io-display directory. The QNX demo that is part of the QNX accelerator kit quick start runs correctly and no io-display process is running. How do I get past this error? Do I need an io-display process running? Thanks, Dave Mon, 06 May 2013 23:37:00 GMT http://community.qnx.com/sf/go/post101196 David Lafreniere 2013-05-06T23:37:00Z http://community.qnx.com/sf/go/post101156 Dear Sir. I found my PNG file is a 32bit PNG, and then I change it to 8bit and 24bit, but it still can not be transparented. Thanks and Best Regards! ******************************************* 金狄 天元鼎正电子科技（北京）有限公司 北京市海淀区上地七街1号汇众大厦106 邮编：100085 电话：010-62970815 手机：18601122606 ******************************************* -----邮件原件----- 发件人: Derek Leach [mailto:community-noreply@qnx.com] 发送时间: 2013年5月3日 21:27 收件人: advanced-graphics 主题: RE: How to show a PNG image with transparent background What kind of PNG, 32-bit? -----Original Message----- From: Di Jin [mailto:community-noreply@qnx.com] Sent: May-03-13 4:47 AM To: advanced-graphics Subject: How to show a PNG image with transparent background I have a PNG image. I modify the background of image to transparency in the Photoshop. I write the code like this: if (img.flags & IMG_TRANSPARENCY) { /* we can handle transparency in GF using chroma */ gf_chroma_t chroma; memset(&chroma, 0, sizeof chroma); chroma.mode = GF_CHROMA_OP_SRC_MATCH | GF_CHROMA_OP_NO_DRAW; if (img.format & IMG_FMT_PALETTE) { chroma.color0 = img.palette[img.transparency.index]; } else if (IMG_FMT_BPP(img.format) < 24) { chroma.color0 = img.transparency.rgb16; } else { chroma.color0 = img.transparency.rgb32; } gf_context_set_chroma(*p_context, &chroma); } if (img.format & IMG_FMT_ALPHA) { gf_alpha_t alpha; memset(&alpha, 0, sizeof alpha); alpha.mode = GF_ALPHA_M1_SRC_PIXEL_ALPHA | GF_BLEND_SRC_M1 | GF_BLEND_DST_1mM1; gf_context_set_alpha(*p_context, &alpha); } // blit the image onto a target surface gf_draw_blit2(*p_context, *p_surface, NULL, 0, 0, img.w - 1, img.h - 1, 0, 0); I found (img.flags & IMG_TRANSPARENCY) this branch always nagative. But my Image has transparent background. How shold I do? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post101108 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post101114 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 06 May 2013 02:53:20 GMT http://community.qnx.com/sf/go/post101156 Di Jin 2013-05-06T02:53:20Z http://community.qnx.com/sf/go/post101133 Hi there, If I am trying to display using 2 layers (2 processes), both using gf, but I found my hardware only had one layer. My question will be: how can I get the hardware which supports multiple layer? If I am doing it under vmware, what is the proper driver to use? thanks, Lu Fri, 03 May 2013 16:58:56 GMT http://community.qnx.com/sf/go/post101133 Lu Li 2013-05-03T16:58:56Z http://community.qnx.com/sf/go/post101119 Dear,Sir. Please check the attaching file. I generate it by Fireworks. Thanks and Best Regards! ******************************************* 金狄 天元鼎正电子科技（北京）有限公司 北京市海淀区上地七街1号汇众大厦106 邮编：100085 电话：010-62970815 手机：18601122606 ******************************************* -----邮件原件----- 发件人: Derek Leach [mailto:community-noreply@qnx.com] 发送时间: 2013年5月3日 21:27 收件人: advanced-graphics 主题: RE: How to show a PNG image with transparent background What kind of PNG, 32-bit? -----Original Message----- From: Di Jin [mailto:community-noreply@qnx.com] Sent: May-03-13 4:47 AM To: advanced-graphics Subject: How to show a PNG image with transparent background I have a PNG image. I modify the background of image to transparency in the Photoshop. I write the code like this: if (img.flags & IMG_TRANSPARENCY) { /* we can handle transparency in GF using chroma */ gf_chroma_t chroma; memset(&chroma, 0, sizeof chroma); chroma.mode = GF_CHROMA_OP_SRC_MATCH | GF_CHROMA_OP_NO_DRAW; if (img.format & IMG_FMT_PALETTE) { chroma.color0 = img.palette[img.transparency.index]; } else if (IMG_FMT_BPP(img.format) < 24) { chroma.color0 = img.transparency.rgb16; } else { chroma.color0 = img.transparency.rgb32; } gf_context_set_chroma(*p_context, &chroma); } if (img.format & IMG_FMT_ALPHA) { gf_alpha_t alpha; memset(&alpha, 0, sizeof alpha); alpha.mode = GF_ALPHA_M1_SRC_PIXEL_ALPHA | GF_BLEND_SRC_M1 | GF_BLEND_DST_1mM1; gf_context_set_alpha(*p_context, &alpha); } // blit the image onto a target surface gf_draw_blit2(*p_context, *p_surface, NULL, 0, 0, img.w - 1, img.h - 1, 0, 0); I found (img.flags & IMG_TRANSPARENCY) this branch always nagative. But my Image has transparent background. How shold I do? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post101108 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post101114 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Fri, 03 May 2013 14:17:48 GMT http://community.qnx.com/sf/go/post101119 Di Jin 2013-05-03T14:17:48Z http://community.qnx.com/sf/go/post101114 What kind of PNG, 32-bit? -----Original Message----- From: Di Jin [mailto:community-noreply@qnx.com] Sent: May-03-13 4:47 AM To: advanced-graphics Subject: How to show a PNG image with transparent background I have a PNG image. I modify the background of image to transparency in the Photoshop. I write the code like this: if (img.flags & IMG_TRANSPARENCY) { /* we can handle transparency in GF using chroma */ gf_chroma_t chroma; memset(&chroma, 0, sizeof chroma); chroma.mode = GF_CHROMA_OP_SRC_MATCH | GF_CHROMA_OP_NO_DRAW; if (img.format & IMG_FMT_PALETTE) { chroma.color0 = img.palette[img.transparency.index]; } else if (IMG_FMT_BPP(img.format) < 24) { chroma.color0 = img.transparency.rgb16; } else { chroma.color0 = img.transparency.rgb32; } gf_context_set_chroma(*p_context, &chroma); } if (img.format & IMG_FMT_ALPHA) { gf_alpha_t alpha; memset(&alpha, 0, sizeof alpha); alpha.mode = GF_ALPHA_M1_SRC_PIXEL_ALPHA | GF_BLEND_SRC_M1 | GF_BLEND_DST_1mM1; gf_context_set_alpha(*p_context, &alpha); } // blit the image onto a target surface gf_draw_blit2(*p_context, *p_surface, NULL, 0, 0, img.w - 1, img.h - 1, 0, 0); I found (img.flags & IMG_TRANSPARENCY) this branch always nagative. But my Image has transparent background. How shold I do? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post101108 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Fri, 03 May 2013 13:27:01 GMT http://community.qnx.com/sf/go/post101114 Derek Leach 2013-05-03T13:27:01Z http://community.qnx.com/sf/go/post101108 I have a PNG image. I modify the background of image to transparency in the Photoshop. I write the code like this: if (img.flags & IMG_TRANSPARENCY) { /* we can handle transparency in GF using chroma */ gf_chroma_t chroma; memset(&chroma, 0, sizeof chroma); chroma.mode = GF_CHROMA_OP_SRC_MATCH | GF_CHROMA_OP_NO_DRAW; if (img.format & IMG_FMT_PALETTE) { chroma.color0 = img.palette[img.transparency.index]; } else if (IMG_FMT_BPP(img.format) < 24) { chroma.color0 = img.transparency.rgb16; } else { chroma.color0 = img.transparency.rgb32; } gf_context_set_chroma(*p_context, &chroma); } if (img.format & IMG_FMT_ALPHA) { gf_alpha_t alpha; memset(&alpha, 0, sizeof alpha); alpha.mode = GF_ALPHA_M1_SRC_PIXEL_ALPHA | GF_BLEND_SRC_M1 | GF_BLEND_DST_1mM1; gf_context_set_alpha(*p_context, &alpha); } // blit the image onto a target surface gf_draw_blit2(*p_context, *p_surface, NULL, 0, 0, img.w - 1, img.h - 1, 0, 0); I found (img.flags & IMG_TRANSPARENCY) this branch always nagative. But my Image has transparent background. How shold I do? Fri, 03 May 2013 08:47:29 GMT http://community.qnx.com/sf/go/post101108 Di Jin 2013-05-03T08:47:29Z http://community.qnx.com/sf/go/post100015 I created a 24 BPP surface using gf_surface_create_layer, specifying CPU_LINEARLY_ACCESSIBLE, and verified that the surface does indeed have this flag set in the surface_info_t. However, when I try and write to the surface, the access does not appear to be linear. It seems as though there is a swizzle or address redirection occurring. Drawing to a 32 bit surface and then using gf_draw_blit to blit to the 24 BPP layer_surface has the same issue. Is it possible to write linearly (with the CPU) to a displayable surface on this chipset? Tue, 19 Mar 2013 20:10:28 GMT http://community.qnx.com/sf/go/post100015 Chris Keating 2013-03-19T20:10:28Z http://community.qnx.com/sf/go/post99705 I got the same problem: # gf-calib -D -f /tmp/calib.conf Number of layers: 1 Resolution: 800x480, refresh = 60Hz layer_idx=0 img_load(target1): errno = 3 load_image2surf(): failed switch_lcd_on switch_lcd_off could any guys help me Wed, 06 Mar 2013 14:08:15 GMT http://community.qnx.com/sf/go/post99705 jimmy shao 2013-03-06T14:08:15Z http://community.qnx.com/sf/go/post99336 Hi all, I am not sure where should I post this question. Is there any simliar config file (such as /etc/system/config/display.conf, cursor=hardware) for screen.so or screen process on QNX CAR 2 ROM to show the mouse cursor if I use USB mouse instead of touch panel? Regards, Chinlin Tue, 19 Feb 2013 07:36:59 GMT http://community.qnx.com/sf/go/post99336 chinlin hung 2013-02-19T07:36:59Z http://community.qnx.com/sf/go/post99320 On my hardware (devg-i830.so) dashed line can't be drawn if width of line is set to 1. If width of line is bigger than 1 then everything works ok. Also looks like that my hardware handles line_repeat qual to 32 only. Is this limitation common to all devices supported via the same driver in this case devg-i830.so ? > gf_point_t p[] = { { 50,250},{w-100,250}}; > gf_context_set_fgcolor(context,0x00ffff); > gf_context_set_bgcolor(context,0xffffff); > gf_context_set_linedash(context,0x000ffff, 0, 32, > GF_CONTEXT_LINEDASH_BACKFILL); > gf_context_set_penwidth( context,10); > gf_draw_polyline(context,p,2,0); > > -----Original Message----- > From: Jacek Rudnicki [mailto:community-noreply@qnx.com] > Sent: February-14-13 2:55 PM > To: advanced-graphics > Subject: Re: Line dashing > > I need to draw dotted and dashed line. > > Can anybody explain how to use the gf_context_set_linedash() for such purpose > ? > Is it possible to draw a dashed line on the patchy background ? > > > Hi, > > > > Example from documentation "Setting line attributes" draws a solid > > line, even if I play with function parameters. > > > > What is a proper usage of the gf_context_set_linedash() function ? > > > > Thank's, > > Jacek > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post99297 > To cancel your subscription to this discussion, please e-mail advanced- > graphics-unsubscribe@community.qnx.com Fri, 15 Feb 2013 19:58:20 GMT http://community.qnx.com/sf/go/post99320 Jacek Rudnicki 2013-02-15T19:58:20Z http://community.qnx.com/sf/go/post99298 gf_point_t p[] = { { 50,250},{w-100,250}}; gf_context_set_fgcolor(context,0x00ffff); gf_context_set_bgcolor(context,0xffffff); gf_context_set_linedash(context,0x000ffff, 0, 32, GF_CONTEXT_LINEDASH_BACKFILL); gf_context_set_penwidth( context,10); gf_draw_polyline(context,p,2,0); -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: February-14-13 2:55 PM To: advanced-graphics Subject: Re: Line dashing I need to draw dotted and dashed line. Can anybody explain how to use the gf_context_set_linedash() for such purpose ? Is it possible to draw a dashed line on the patchy background ? > Hi, > > Example from documentation "Setting line attributes" draws a solid > line, even if I play with function parameters. > > What is a proper usage of the gf_context_set_linedash() function ? > > Thank's, > Jacek _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post99297 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Thu, 14 Feb 2013 20:02:01 GMT http://community.qnx.com/sf/go/post99298 Derek Leach 2013-02-14T20:02:01Z http://community.qnx.com/sf/go/post99297 I need to draw dotted and dashed line. Can anybody explain how to use the gf_context_set_linedash() for such purpose ? Is it possible to draw a dashed line on the patchy background ? > Hi, > > Example from documentation "Setting line attributes" draws a solid line, > even if I play with function parameters. > > What is a proper usage of the gf_context_set_linedash() function ? > > Thank's, > Jacek Thu, 14 Feb 2013 19:54:57 GMT http://community.qnx.com/sf/go/post99297 Jacek Rudnicki 2013-02-14T19:54:57Z http://community.qnx.com/sf/go/post99210 Hi, Example from documentation "Setting line attributes" draws a solid line, even if I play with function parameters. What is a proper usage of the gf_context_set_linedash() function ? Thank's, Jacek Mon, 11 Feb 2013 20:16:01 GMT http://community.qnx.com/sf/go/post99210 Jacek Rudnicki 2013-02-11T20:16:01Z http://community.qnx.com/sf/go/post99209 You are correct, there is no 'draw circle' in GF. The original reason was that hardware did not generally implement such a request, and GF only generally mirrors hardware functionality. Photon supports drawing of circles, but at the lowest level, it is all broken down to many span draws. -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: February-11-13 3:12 PM To: advanced-graphics Subject: Re: Drawing a cicle The GF library doesn't include function for drawing a cricle. Looks like that I have to implement such routine itself. > How to draw a circle ? > Is it possible ? > > Jacek _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post99208 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 11 Feb 2013 20:15:44 GMT http://community.qnx.com/sf/go/post99209 Derek Leach 2013-02-11T20:15:44Z http://community.qnx.com/sf/go/post99208 The GF library doesn't include function for drawing a cricle. Looks like that I have to implement such routine itself. > How to draw a circle ? > Is it possible ? > > Jacek Mon, 11 Feb 2013 20:11:45 GMT http://community.qnx.com/sf/go/post99208 Jacek Rudnicki 2013-02-11T20:11:45Z http://community.qnx.com/sf/go/post99206 Ok, so I have to look for the another solution... > > I set chroma as follows: > > chroma.mode = GF_CHROMA_OP_DST_MATCH | GF_CHROMA_OP_NO_DRAW; > > Sorry, but it is unaccelerated. Only SRC_MATCH | NO_DRAW is accelereted. Mon, 11 Feb 2013 20:05:57 GMT http://community.qnx.com/sf/go/post99206 Jacek Rudnicki 2013-02-11T20:05:57Z http://community.qnx.com/sf/go/post99196 > I set chroma as follows: > chroma.mode = GF_CHROMA_OP_DST_MATCH | GF_CHROMA_OP_NO_DRAW; Sorry, but it is unaccelerated. Only SRC_MATCH | NO_DRAW is accelereted. Mon, 11 Feb 2013 07:00:49 GMT http://community.qnx.com/sf/go/post99196 Mike Gorchak 2013-02-11T07:00:49Z http://community.qnx.com/sf/go/post99092 How to draw a circle ? Is it possible ? Jacek Tue, 05 Feb 2013 19:02:18 GMT http://community.qnx.com/sf/go/post99092 Jacek Rudnicki 2013-02-05T19:02:18Z http://community.qnx.com/sf/go/post99049 Are the pixel formats of the source and destination surfaces different? Are planemask or rops enabled during this operation? Are either of the surfaces allocated for CPU fast access? Any of these will force chroma blit into CPU software mode ... -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: February-04-13 4:35 PM To: advanced-graphics Subject: Layers - code example Hi, Is there any example which shows how to properly use layers ? Thank's Jacek _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post99048 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 04 Feb 2013 21:48:10 GMT http://community.qnx.com/sf/go/post99049 Derek Leach 2013-02-04T21:48:10Z http://community.qnx.com/sf/go/post99048 Hi, Is there any example which shows how to properly use layers ? Thank's Jacek Mon, 04 Feb 2013 21:34:51 GMT http://community.qnx.com/sf/go/post99048 Jacek Rudnicki 2013-02-04T21:34:51Z http://community.qnx.com/sf/go/post99043 I set chroma as follows: chroma.mode = GF_CHROMA_OP_DST_MATCH | GF_CHROMA_OP_NO_DRAW; > Ok, there is a hw accel for certain chroma operations, but not all, what > chroma flags are you setting? > > -----Original Message----- > From: Jacek Rudnicki [mailto:community-noreply@qnx.com] > Sent: February-04-13 11:38 AM > To: advanced-graphics > Subject: Re: RE: chroma operation increasing CPU hog > > devg-i830 > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post99041 > To cancel your subscription to this discussion, please e-mail advanced- > graphics-unsubscribe@community.qnx.com Mon, 04 Feb 2013 16:45:28 GMT http://community.qnx.com/sf/go/post99043 Jacek Rudnicki 2013-02-04T16:45:28Z http://community.qnx.com/sf/go/post99042 Ok, there is a hw accel for certain chroma operations, but not all, what chroma flags are you setting? -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: February-04-13 11:38 AM To: advanced-graphics Subject: Re: RE: chroma operation increasing CPU hog devg-i830 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post99041 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 04 Feb 2013 16:40:58 GMT http://community.qnx.com/sf/go/post99042 Derek Leach 2013-02-04T16:40:58Z http://community.qnx.com/sf/go/post99041 devg-i830 Mon, 04 Feb 2013 16:37:56 GMT http://community.qnx.com/sf/go/post99041 Jacek Rudnicki 2013-02-04T16:37:56Z http://community.qnx.com/sf/go/post99032 What devg driver are you using? -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: February-03-13 2:54 PM To: advanced-graphics Subject: chroma operation increasing CPU hog Hi, In application respnsible for displaying video stream the gf_draw_blit2() is called very often. When I set chroma via gf_context_set_chroma() then the following behavior is observed: - increasing CPU hog, - corrupted picture, - picture is not displayed in real time. I need to set chroma keying in order to not display video data on particular color. Am I doing something wrong or my hardware is too slow for such usage ? Application is tested with devg-i830.so driver. Regards, Jacek _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post99026 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 04 Feb 2013 13:50:19 GMT http://community.qnx.com/sf/go/post99032 Derek Leach 2013-02-04T13:50:19Z http://community.qnx.com/sf/go/post99026 Hi, In application respnsible for displaying video stream the gf_draw_blit2() is called very often. When I set chroma via gf_context_set_chroma() then the following behavior is observed: - increasing CPU hog, - corrupted picture, - picture is not displayed in real time. I need to set chroma keying in order to not display video data on particular color. Am I doing something wrong or my hardware is too slow for such usage ? Application is tested with devg-i830.so driver. Regards, Jacek Sun, 03 Feb 2013 19:53:33 GMT http://community.qnx.com/sf/go/post99026 Jacek Rudnicki 2013-02-03T19:53:33Z http://community.qnx.com/sf/go/post99006 Hello, I have application (hybrid of GF and Photon) which is responsible for displaying video stream. Everything works fine and data is displayed in layer 0 which is shared with Photon. I need to draw some lines and text on the top of video stream. Idea is as follows: Layer0: Photon application (lines, text, some other components, widgets, ...), Layer1: GF+Photon (video stream). I don't know if this is a right direction. Regards, Jacek Fri, 01 Feb 2013 19:17:58 GMT http://community.qnx.com/sf/go/post99006 Jacek Rudnicki 2013-02-01T19:17:58Z http://community.qnx.com/sf/go/post98343 Try running your application with "LD_DEBUG=1 {your-app}". You should see which library your are missing. Wed, 02 Jan 2013 16:43:51 GMT http://community.qnx.com/sf/go/post98343 Misha Nefedov 2013-01-02T16:43:51Z http://community.qnx.com/sf/go/post98313 Afetr including img.conf and img_codec so's i am getting error as Number of layers: 3 Resolution: 720x400, refresh = 60Hz layer_idx=0 img_load(target1): errno = 3 load_image2surf(): failed Please help. Mon, 24 Dec 2012 06:29:35 GMT http://community.qnx.com/sf/go/post98313 bhanu shankar d g 2012-12-24T06:29:35Z http://community.qnx.com/sf/go/post97623 Please contact tech support for this level of support. -----Original Message----- From: Ashwini Dubey [mailto:community-noreply@qnx.com] Sent: November-29-12 10:20 AM To: advanced-graphics Subject: Re: RE: RE: RE: gf_layer_attach() failed !!! Can you please provide example of working GF drawing code. Do let me also know how to toggle between GUI and text mode. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post97622 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Thu, 29 Nov 2012 15:20:02 GMT http://community.qnx.com/sf/go/post97623 Derek Leach 2012-11-29T15:20:02Z http://community.qnx.com/sf/go/post97622 Can you please provide example of working GF drawing code. Do let me also know how to toggle between GUI and text mode. Thu, 29 Nov 2012 15:19:43 GMT http://community.qnx.com/sf/go/post97622 Ashwini Dubey 2012-11-29T15:19:43Z http://community.qnx.com/sf/go/post97615 If you want to use Photon, ypu must use Pg photon drawing lines, please see helpviewer in Photon. If you want to use GF application, then you must exit Photon to text mode, then to make it easy, telnet into the QNX box, then run the GF application. -----Original Message----- From: Ashwini Dubey [mailto:community-noreply@qnx.com] Sent: November-29-12 3:16 AM To: advanced-graphics Subject: Re: RE: RE: gf_layer_attach() failed !!! What else is running on the machine? I have a default installation and basic GUI is running. …...... Is Photon running? Yes. 176152 1 /photon/bin/Photon 10r RECEIVE 1 …...... Number of displays: 1 Display 0: 1024X768, refresh = 60Hz Number of layers: 1 …...... I am very new to QNX, but I am experienced in linux application and kernel development. Currently I am using intel HD Graphics, PCI device, Vendor ID:8086, Device ID:0152. …. please suggest what I need to draw a rectangle or circle or line. Below is list of all the process running. Result of pidin command. pid tid name prio STATE Blocked 1 1 boot/procnto-instr 0f READY 1 2 boot/procnto-instr 255r RECEIVE 1 1 3 boot/procnto-instr 10r RECEIVE 1 1 4 boot/procnto-instr 10r RUNNING 1 5 boot/procnto-instr 255r RECEIVE 1 1 7 boot/procnto-instr 10r RECEIVE 1 1 8 boot/procnto-instr 10r RECEIVE 1 1 10 boot/procnto-instr 10r RECEIVE 1 1 11 boot/procnto-instr 10r RECEIVE 1 1 12 boot/procnto-instr 10r RECEIVE 1 1 15 boot/procnto-instr 10r RECEIVE 1 1 16 boot/procnto-instr 10r RECEIVE 1 2 1 sbin/tinit 10o REPLY 1 4099 1 proc/boot/pci-bios 10o RECEIVE 1 4100 1 proc/boot/slogger 10o RECEIVE 1 4101 1 proc/boot/io-usb 10o SIGWAITINFO 4101 2 proc/boot/io-usb 21r RECEIVE 4 4101 3 proc/boot/io-usb 21r RECEIVE 7 4101 4 proc/boot/io-usb 21r RECEIVE 1 4101 5 proc/boot/io-usb 10o RECEIVE 10 4101 6 proc/boot/io-usb 10r NANOSLEEP 4101 7 proc/boot/io-usb 10o RECEIVE 10 4101 8 proc/boot/io-usb 10o RECEIVE 10 4102 1 proc/boot/io-hid 10o SIGWAITINFO 4102 2 proc/boot/io-hid 21r RECEIVE 1 4102 4 proc/boot/io-hid 10o RECEIVE 4 4102 5 proc/boot/io-hid 10r REPLY 4101 4102 6 proc/boot/io-hid 10r REPLY 4101 4102 7 proc/boot/io-hid 9r RECEIVE 12 4102 8 proc/boot/io-hid 9r RECEIVE 16 4102 9 proc/boot/io-hid 10o RECEIVE 4 4103 1 /boot/devc-con-hid 20o RECEIVE 1 4103 2 /boot/devc-con-hid 10o REPLY 4102 8200 1 roc/boot/devb-eide 10o SIGWAITINFO 8200 2 roc/boot/devb-eide 21r RECEIVE 1 8200 3 roc/boot/devb-eide 21o RECEIVE 7 8200 4 roc/boot/devb-eide 10o RECEIVE 4 8200 5 roc/boot/devb-eide 10o RECEIVE 4 8200 6 roc/boot/devb-eide 10o RECEIVE 4 8200 7 roc/boot/devb-eide 10o RECEIVE 4 8200 10 roc/boot/devb-eide 10o RECEIVE 4 8200 13 roc/boot/devb-eide 10o RECEIVE 4 20489 1 sbin/pipe 10o SIGWAITINFO 20489 2 sbin/pipe 10o RECEIVE 1 20489 3 sbin/pipe 10o RECEIVE 1 20489 4 sbin/pipe 10o RECEIVE 1 20489 5 sbin/pipe 10o RECEIVE 1 24586 1 sbin/mqueue 10o RECEIVE 1 53259 1 usr/sbin/mcd 10o RECEIVE 1 53259 2 usr/sbin/mcd 10o NANOSLEEP 53259 3 usr/sbin/mcd 10o SIGWAITINFO 53259 4 usr/sbin/mcd 9o SIGWAITINFO 53259 5 usr/sbin/mcd 10o SIGWAITINFO 53259 6 usr/sbin/mcd 10o SIGWAITINFO 53259 7 usr/sbin/mcd 10o SIGWAITINFO 57356 1 usr/sbin/random 10o SIGWAITINFO 57356 2 usr/sbin/random 10o RECEIVE 1 57356 3 usr/sbin/random 10o NANOSLEEP 61453 1 sbin/enum-devices 10o REPLY 20489 77840 1 sbin/enum-usb 10o SIGWAITINFO 77840 2 sbin/enum-usb 10r REPLY 4101 94222 1 sbin/io-display 10o SIGWAITINFO 94222 2 sbin/io-display 10o RECEIVE 1 94222 3 sbin/io-display 12o RECEIVE 1 94222 4 sbin/io-display 10o RECEIVE 3 94222 5 sbin/io-display 10o RECEIVE 1 118799 1 sbin/io-pkt-v4-hc 21o SIGWAITINFO 118799 2 sbin/io-pkt-v4-hc 21o RECEIVE 1 118801 1 sbin/devc-pty 10o RECEIVE 1 131090 1 usr/sbin/dumper 10o RECEIVE 1 147475 1 bin/login 10o REPLY 4103 147476 1 bin/login 10o REPLY 4103 147477 1 bin/login 10o REPLY 4103 176152 1 /photon/bin/Photon 10r RECEIVE 1 196633 1 on/bin/io-graphics 12r CONDVAR (0x805dc40) 196633 2 on/bin/io-graphics 10r RECEIVE 1 196633 3 on/bin/io-graphics 12r REPLY 176152 213020 1 hoton/bin/devi-hid 10o RECEIVE 1 213020 2 hoton/bin/devi-hid 10o REPLY 4102 213020 3 hoton/bin/devi-hid 12o SIGWAITINFO 213020 4 hoton/bin/devi-hid 10o RECEIVE 1 213020 5 hoton/bin/devi-hid 10o RECEIVE 1 225302 1 bin/login 10o REPLY 4103 786465 1 sbin/io-pkt-v4-hc 21r SIGWAITINFO 786465 2 sbin/io-pkt-v4-hc 10r RECEIVE 1 811044 1 r/sbin/dhcp.client 10r NANOSLEEP 3182629 1 usr/sbin/sshd 10r SIGWAITINFO 4292635 1 usr/photon/bin/pwm 10r RECEIVE 1 4321309 1 r/photon/bin/shelf 10r CONDVAR (0x8076f88) 4321309 2 r/photon/bin/shelf 10r RECEIVE 1 4341790 1 photon/bin/bkgdmgr 10r RECEIVE 1 4341791 1 hoton/bin/wmswitch 10r RECEIVE 2 4341792 1 r/photon/bin/saver 10r RECEIVE 1 4689961 1 usr/sbin/inetd 10r SIGWAITINFO 4771874 1 usr/bin/phrelay 10r REPLY 176152 4771874 2 usr/bin/phrelay 10r REPLY 786465 4771874 3 usr/bin/phrelay 10r CONDVAR (0x805be30) 4792343 1 r/photon/bin/pterm 10r RECEIVE 1 4792346 1 bin/sh 10r SIGSUSPEND 4792355 1 bin/pidin 10r REPLY 1 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post97598 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Thu, 29 Nov 2012 14:01:59 GMT http://community.qnx.com/sf/go/post97615 Derek Leach 2012-11-29T14:01:59Z http://community.qnx.com/sf/go/post97598 What else is running on the machine? I have a default installation and basic GUI is running. …...... Is Photon running? Yes. 176152 1 /photon/bin/Photon 10r RECEIVE 1 …...... Number of displays: 1 Display 0: 1024X768, refresh = 60Hz Number of layers: 1 …...... I am very new to QNX, but I am experienced in linux application and kernel development. Currently I am using intel HD Graphics, PCI device, Vendor ID:8086, Device ID:0152. …. please suggest what I need to draw a rectangle or circle or line. Below is list of all the process running. Result of pidin command. pid tid name prio STATE Blocked 1 1 boot/procnto-instr 0f READY 1 2 boot/procnto-instr 255r RECEIVE 1 1 3 boot/procnto-instr 10r RECEIVE 1 1 4 boot/procnto-instr 10r RUNNING 1 5 boot/procnto-instr 255r RECEIVE 1 1 7 boot/procnto-instr 10r RECEIVE 1 1 8 boot/procnto-instr 10r RECEIVE 1 1 10 boot/procnto-instr 10r RECEIVE 1 1 11 boot/procnto-instr 10r RECEIVE 1 1 12 boot/procnto-instr 10r RECEIVE 1 1 15 boot/procnto-instr 10r RECEIVE 1 1 16 boot/procnto-instr 10r RECEIVE 1 2 1 sbin/tinit 10o REPLY 1 4099 1 proc/boot/pci-bios 10o RECEIVE 1 4100 1 proc/boot/slogger 10o RECEIVE 1 4101 1 proc/boot/io-usb 10o SIGWAITINFO 4101 2 proc/boot/io-usb 21r RECEIVE 4 4101 3 proc/boot/io-usb 21r RECEIVE 7 4101 4 proc/boot/io-usb 21r RECEIVE 1 4101 5 proc/boot/io-usb 10o RECEIVE 10 4101 6 proc/boot/io-usb 10r NANOSLEEP 4101 7 proc/boot/io-usb 10o RECEIVE 10 4101 8 proc/boot/io-usb 10o RECEIVE 10 4102 1 proc/boot/io-hid 10o SIGWAITINFO 4102 2 proc/boot/io-hid 21r RECEIVE 1 4102 4 proc/boot/io-hid 10o RECEIVE 4 4102 5 proc/boot/io-hid 10r REPLY 4101 4102 6 proc/boot/io-hid 10r REPLY 4101 4102 7 proc/boot/io-hid 9r RECEIVE 12 4102 8 proc/boot/io-hid 9r RECEIVE 16 4102 9 proc/boot/io-hid 10o RECEIVE 4 4103 1 /boot/devc-con-hid 20o RECEIVE 1 4103 2 /boot/devc-con-hid 10o REPLY 4102 8200 1 roc/boot/devb-eide 10o SIGWAITINFO 8200 2 roc/boot/devb-eide 21r RECEIVE 1 8200 3 roc/boot/devb-eide 21o RECEIVE 7 8200 4 roc/boot/devb-eide 10o RECEIVE 4 8200 5 roc/boot/devb-eide 10o RECEIVE 4 8200 6 roc/boot/devb-eide 10o RECEIVE 4 8200 7 roc/boot/devb-eide 10o RECEIVE 4 8200 10 roc/boot/devb-eide 10o RECEIVE 4 8200 13 roc/boot/devb-eide 10o RECEIVE 4 20489 1 sbin/pipe 10o SIGWAITINFO 20489 2 sbin/pipe 10o RECEIVE 1 20489 3 sbin/pipe 10o RECEIVE 1 20489 4 sbin/pipe 10o RECEIVE 1 20489 5 sbin/pipe 10o RECEIVE 1 24586 1 sbin/mqueue 10o RECEIVE 1 53259 1 usr/sbin/mcd 10o RECEIVE 1 53259 2 usr/sbin/mcd 10o NANOSLEEP 53259 3 usr/sbin/mcd 10o SIGWAITINFO 53259 4 usr/sbin/mcd 9o SIGWAITINFO 53259 5 usr/sbin/mcd 10o SIGWAITINFO 53259 6 usr/sbin/mcd 10o SIGWAITINFO 53259 7 usr/sbin/mcd 10o SIGWAITINFO 57356 1 usr/sbin/random 10o SIGWAITINFO 57356 2 usr/sbin/random 10o RECEIVE 1 57356 3 usr/sbin/random 10o NANOSLEEP 61453 1 sbin/enum-devices 10o REPLY 20489 77840 1 sbin/enum-usb 10o SIGWAITINFO 77840 2 sbin/enum-usb 10r REPLY 4101 94222 1 sbin/io-display 10o SIGWAITINFO 94222 2 sbin/io-display 10o RECEIVE 1 94222 3 sbin/io-display 12o RECEIVE 1 94222 4 sbin/io-display 10o RECEIVE 3 94222 5 sbin/io-display 10o RECEIVE 1 118799 1 sbin/io-pkt-v4-hc 21o SIGWAITINFO 118799 2 sbin/io-pkt-v4-hc 21o RECEIVE 1 118801 1 sbin/devc-pty 10o RECEIVE 1 131090 1 usr/sbin/dumper 10o RECEIVE 1 147475 1 bin/login 10o REPLY 4103 147476 1 bin/login 10o REPLY 4103 147477 1 bin/login 10o REPLY 4103 176152 1 /photon/bin/Photon 10r RECEIVE 1 196633 1 on/bin/io-graphics 12r CONDVAR (0x805dc40) 196633 2 on/bin/io-graphics 10r RECEIVE 1 196633 3 on/bin/io-graphics 12r REPLY 176152 213020 1 hoton/bin/devi-hid 10o RECEIVE 1 213020 2 hoton/bin/devi-hid 10o REPLY 4102 213020 3 hoton/bin/devi-hid 12o SIGWAITINFO 213020 4 hoton/bin/devi-hid 10o RECEIVE 1 213020 5 hoton/bin/devi-hid 10o RECEIVE 1 225302 1 bin/login 10o REPLY 4103 786465 1 sbin/io-pkt-v4-hc 21r SIGWAITINFO 786465 2 sbin/io-pkt-v4-hc 10r RECEIVE 1 811044 1 r/sbin/dhcp.client 10r NANOSLEEP 3182629 1 usr/sbin/sshd 10r SIGWAITINFO 4292635 1 usr/photon/bin/pwm 10r RECEIVE 1 4321309 1 r/photon/bin/shelf 10r CONDVAR (0x8076f88) 4321309 2 r/photon/bin/shelf 10r RECEIVE 1 4341790 1 photon/bin/bkgdmgr 10r RECEIVE 1 4341791 1 hoton/bin/wmswitch 10r RECEIVE 2 4341792 1 r/photon/bin/saver 10r RECEIVE 1 4689961 1 usr/sbin/inetd 10r SIGWAITINFO 4771874 1 usr/bin/phrelay 10r REPLY 176152 4771874 2 usr/bin/phrelay 10r REPLY 786465 4771874 3 usr/bin/phrelay 10r CONDVAR (0x805be30) 4792343 1 r/photon/bin/pterm 10r RECEIVE 1 4792346 1 bin/sh 10r SIGSUSPEND 4792355 1 bin/pidin 10r REPLY 1 Thu, 29 Nov 2012 08:16:13 GMT http://community.qnx.com/sf/go/post97598 Ashwini Dubey 2012-11-29T08:16:13Z http://community.qnx.com/sf/go/post97562 What else is running on the machine? Is Photon running? You only have one layer on your machine, so no other graphics environment or application can be running. -----Original Message----- From: Ashwini Dubey [mailto:community-noreply@qnx.com] Sent: November-28-12 3:45 AM To: advanced-graphics Subject: Re: RE: gf_layer_attach() failed !!! Return Value = 0x8 which is GF_ERR_INUSE.. I have installed qnx on i5 intel machine....and i can connect to it and run basic hello world... i can use web browser too. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post97541 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Wed, 28 Nov 2012 15:09:05 GMT http://community.qnx.com/sf/go/post97562 Derek Leach 2012-11-28T15:09:05Z http://community.qnx.com/sf/go/post97543 hi all, i am new to QNX graphics and i am facing problem regarding memory allocation failed in gf_surface_create_layer(); return value = 1, GF_ERR_MEM code is given below.. #include <stdlib.h> #include <stdio.h> #include<gf/gf.h> int main(int argc, char *argv[]) { gf_dev_t gdev; gf_dev_info_t gdev_info; gf_display_t display; gf_display_info_t display_info; gf_layer_t layer; gf_surface_t surface; int i=0; if (gf_dev_attach(&gdev, GF_DEVICE_INDEX(0), &gdev_info) != GF_ERR_OK) { printf("gf_dev_attach() failed\n"); return (-1); } printf("Number of displays: %d\n",gdev_info.ndisplays); for (i = 0; i < gdev_info.ndisplays; i++ ) { printf("Display %d: ", i); if (gf_display_attach(&display, gdev, i, &display_info) == GF_ERR_OK) { printf("%dX%d, refresh = %dHz\n", display_info.xres, display_info.yres, display_info.refresh); printf("Number of layers: %d\n", display_info.nlayers); if (gf_layer_attach(&layer, display,0, 1) == GF_ERR_OK ) { printf("\n\tLayer attached Successfully."); //printf("\n\t%d", gf_surface_create_layer(&surface, &layer, 1,0, display_info.xres, display_info.yres, display_info.format , NULL, 0 )); if(gf_surface_create_layer(&surface, &layer, 0,0, display_info.xres, display_info.yres, GF_FORMAT_PACK_RGB565 , NULL, 0 ) == GF_ERR_OK ) { printf("\n\tSurface created successfully."); } else printf("\n\tSurface failed."); } else printf("\n\tLayer Failed."); } else printf("gf_display_attach() failed\n"); } printf("\n\tWelcome to the QNX Momentics IDE\n"); if(gdev) { gf_dev_detach(gdev); } return EXIT_SUCCESS; } Wed, 28 Nov 2012 10:48:05 GMT http://community.qnx.com/sf/go/post97543 Rahul Kaswa 2012-11-28T10:48:05Z http://community.qnx.com/sf/go/post97541 Return Value = 0x8 which is GF_ERR_INUSE.. I have installed qnx on i5 intel machine....and i can connect to it and run basic hello world... i can use web browser too. Wed, 28 Nov 2012 08:45:08 GMT http://community.qnx.com/sf/go/post97541 Ashwini Dubey 2012-11-28T08:45:08Z http://community.qnx.com/sf/go/post97491 What is the return value from gf_layer_attach()? -----Original Message----- From: Ashwini Dubey [mailto:community-noreply@qnx.com] Sent: November-27-12 2:02 AM To: advanced-graphics Subject: gf_layer_attach() failed !!! Dear All, Dear All, I am new to qnx GF, I have read “Advanced Graphics Developers Guide.pdf” and trying to draw a rectangle on GF. I have x86 target machine connected to QNX Momentics IDE 4.7. gf_layer_attach() is failed... can some help... find output and code below. Output: Number of displays: 1 Display 0: 1024X768, refresh = 60Hz Number of layers: 1 code snippet: #include <stdio.h> #include <stdlib.h> #include <gf/gf.h> int main() { //device & display gf_dev_t gdev; gf_dev_info_t gdev_info; gf_display_t display; gf_display_info_t display_info; int i; //layer gf_layer_t layer; //surface gf_surface_t surface; unsigned height; unsigned width; gf_layer_info_t layer_info; //context gf_context_t context; if (gf_dev_attach(&gdev, GF_DEVICE_INDEX(0), &gdev_info) != GF_ERR_OK) { printf("gf_dev_attach() failed\n"); return (-1); } printf("Number of displays: %d\n",gdev_info.ndisplays); for (i = 0; i < gdev_info.ndisplays; i++) { printf("Display %d: ", i); if (gf_display_attach(&display, gdev, i, &display_info) == GF_ERR_OK) { printf("%dX%d, refresh = %dHz\n", display_info.xres, display_info.yres, display_info.refresh); printf("Number of layers: %d\n", display_info.nlayers); } else { printf("gf_display_attach() failed\n"); } } if (display != NULL) { if (gf_layer_attach(&layer,display,display_info.main_layer_index, 0) == GF_ERR_OK) { //if(gf_layer_attach(&layer,display,0, 0) == GF_ERR_OK) { printf("Attaching to Layer : 2\n "); } else { printf("gf_layer_attach() failed\n"); } } if((gf_layer_query(layer,0,&layer_info))==GF_ERR_OK){ printf("Layer is of Format %d\n",layer_info.format); } else{ printf(" gf_layer_query() failed"); } width = display_info.xres; height = display_info.yres; if (gf_surface_create_layer(&surface, &layer, 1, 0, width, height, layer_info.format, NULL, 0) == GF_ERR_OK) { printf("Succesfully created surface on top of layer\n"); gf_layer_set_surfaces(layer, &surface, 1); /* draw stuff here */ } else { printf("gf_surface_create_layer() failed\n"); } if (gf_context_create(&context) != GF_ERR_OK) { fprintf(stderr, "gf_context_create failed\n"); return -1; } else{ printf(" Created the context succefully\n"); } if (gf_context_set_surface(context,surface)!= GF_ERR_OK) { fprintf(stderr, "gf_context_set_surface failed\n"); return -1; } else{ printf("Context Surface is Set Succesfully\n"); } gf_draw_begin(context); gf_context_set_fgcolor(context,0xFFFFFF); gf_draw_rect(context,10,10,50,50); gf_context_set_fgcolor(context,0x000000); gf_draw_rect(context,20,20,40,40); gf_draw_end(context); gf_dev_detach(gdev); return 0; } _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post97473 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Tue, 27 Nov 2012 14:15:55 GMT http://community.qnx.com/sf/go/post97491 Derek Leach 2012-11-27T14:15:55Z http://community.qnx.com/sf/go/post97473 Dear All, Dear All, I am new to qnx GF, I have read “Advanced Graphics Developers Guide.pdf” and trying to draw a rectangle on GF. I have x86 target machine connected to QNX Momentics IDE 4.7. gf_layer_attach() is failed... can some help... find output and code below. Output: Number of displays: 1 Display 0: 1024X768, refresh = 60Hz Number of layers: 1 code snippet: #include <stdio.h> #include <stdlib.h> #include <gf/gf.h> int main() { //device & display gf_dev_t gdev; gf_dev_info_t gdev_info; gf_display_t display; gf_display_info_t display_info; int i; //layer gf_layer_t layer; //surface gf_surface_t surface; unsigned height; unsigned width; gf_layer_info_t layer_info; //context gf_context_t context; if (gf_dev_attach(&gdev, GF_DEVICE_INDEX(0), &gdev_info) != GF_ERR_OK) { printf("gf_dev_attach() failed\n"); return (-1); } printf("Number of displays: %d\n",gdev_info.ndisplays); for (i = 0; i < gdev_info.ndisplays; i++) { printf("Display %d: ", i); if (gf_display_attach(&display, gdev, i, &display_info) == GF_ERR_OK) { printf("%dX%d, refresh = %dHz\n", display_info.xres, display_info.yres, display_info.refresh); printf("Number of layers: %d\n", display_info.nlayers); } else { printf("gf_display_attach() failed\n"); } } if (display != NULL) { if (gf_layer_attach(&layer,display,display_info.main_layer_index, 0) == GF_ERR_OK) { //if(gf_layer_attach(&layer,display,0, 0) == GF_ERR_OK) { printf("Attaching to Layer : 2\n "); } else { printf("gf_layer_attach() failed\n"); } } if((gf_layer_query(layer,0,&layer_info))==GF_ERR_OK){ printf("Layer is of Format %d\n",layer_info.format); } else{ printf(" gf_layer_query() failed"); } width = display_info.xres; height = display_info.yres; if (gf_surface_create_layer(&surface, &layer, 1, 0, width, height, layer_info.format, NULL, 0) == GF_ERR_OK) { printf("Succesfully created surface on top of layer\n"); gf_layer_set_surfaces(layer, &surface, 1); /* draw stuff here */ } else { printf("gf_surface_create_layer() failed\n"); } if (gf_context_create(&context) != GF_ERR_OK) { fprintf(stderr, "gf_context_create failed\n"); return -1; } else{ printf(" Created the context succefully\n"); } if (gf_context_set_surface(context,surface)!= GF_ERR_OK) { fprintf(stderr, "gf_context_set_surface failed\n"); return -1; } else{ printf("Context Surface is Set Succesfully\n"); } gf_draw_begin(context); gf_context_set_fgcolor(context,0xFFFFFF); gf_draw_rect(context,10,10,50,50); gf_context_set_fgcolor(context,0x000000); gf_draw_rect(context,20,20,40,40); gf_draw_end(context); gf_dev_detach(gdev); return 0; } Tue, 27 Nov 2012 07:01:57 GMT http://community.qnx.com/sf/go/post97473 Ashwini Dubey 2012-11-27T07:01:57Z http://community.qnx.com/sf/go/post96507 Good :) -----Original Message----- From: KB [mailto:community-noreply@qnx.com] Sent: October-19-12 2:08 AM To: advanced-graphics Subject: Re: Unable to launch io-graphics Never mind this issue is solved. For further information check on this topic : http://www.openqnx.com/phpbbforum/viewtopic.php?f=8&t=13205 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post96441 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 22 Oct 2012 12:25:21 GMT http://community.qnx.com/sf/go/post96507 Derek Leach 2012-10-22T12:25:21Z http://community.qnx.com/sf/go/post96505 Do you have a /usr/photon/font_repository on your target? -----Original Message----- From: KB [mailto:community-noreply@qnx.com] Sent: October-15-12 9:35 AM To: advanced-graphics Subject: Unable to launch io-graphics Hi, I'm trying to run a small photon application on my embedded system (for instance phcalc). Here's my issue : I am able to run io-display, see my display.conf : # My PCI device { drivername=lx800 vid=0x1022 did=0x2081 deviceindex=0 display { xres=1024 yres=768 refresh=60 pixel_format=argb8888 } } I am able to run vsync. I can't launch demo-alpha > sloginfo : When I run io-graphics I've got the following error : Oct 15 15:07:47 6 8 0 Primary active: 0 9 7 Oct 15 15:07:58 6 8 0 VGA primary : bus 0x0 dev/func 0x9 Oct 15 15:07:58 6 8 0 Found 1 PCI/AGP display devices Oct 15 15:07:58 6 8 0 pci_init: found PCI device 1022:2081 Oct 15 15:07:58 6 8 0 No config file specified Oct 15 15:07:59 6 8 0 Primary active: 0 9 7 Il I launch Photon binary and then phcalc (for example), I have : "unable to attach to font server, pf_attach() : No such file or directory" "Ap: Unable to locate Photon (2)" If I run phfont I have : "PfAttachLocalDllArgv() : Invalid argument " and the following slog : Oct 15 15:07:59 6 8 0 Primary active: 0 9 7 Oct 15 15:12:42 1 8 0 phfont: init... Oct 15 15:12:42 1 8 0 phfont: unable to load font extension rules If I run ph script I have : "Unable to start graphics driver(s)" and the followin slog : Oct 15 15:16:46 1 8 0 phfont.so: init... Oct 15 15:16:46 1 8 0 phfont.so: unable to load font extension rules Oct 15 15:16:46 2 8 0 io-graphics: FAIL PfAttachLocalDll(): Invalid argument, please verify font server configuration. Oct 15 15:16:46 2 8 0 fontserver_setup() My script is attached. My environment variables are defined hereafter : HOME=/ PATH=/proc/boot:/bin:/usr/bin:/usr/sbin:/sbin:/APD:/usr/photon/bin LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll PHOTON_PATH=/usr/photon PHOTON2_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont setconf _CS_LIBPATH :/proc/boot:/lib/dll:/dev/shmem:/lib:/usr/lib:/lib/dll:/lib/dll/font:/usr/photon/lib I'm running QNX 6.5.0. My board is a Rhodeus Geode (AMD 500Mghz) : http://www.diamondsystems.com/products/rhodeus My starting point was this official BSP : http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/AmdGeodeLxdb800 But I had to change things (surcvh as realtek driver)... I use devg-lx800.so graphic library. Any help would be appreciated. Thanks. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post96328 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Mon, 22 Oct 2012 12:08:29 GMT http://community.qnx.com/sf/go/post96505 Derek Leach 2012-10-22T12:08:29Z http://community.qnx.com/sf/go/post96441 Never mind this issue is solved. For further information check on this topic : http://www.openqnx.com/phpbbforum/viewtopic.php?f=8&t=13205 Fri, 19 Oct 2012 06:08:24 GMT http://community.qnx.com/sf/go/post96441 KB 2012-10-19T06:08:24Z http://community.qnx.com/sf/go/post96328 Hi, I'm trying to run a small photon application on my embedded system (for instance phcalc). Here's my issue : I am able to run io-display, see my display.conf : # My PCI device { drivername=lx800 vid=0x1022 did=0x2081 deviceindex=0 display { xres=1024 yres=768 refresh=60 pixel_format=argb8888 } } I am able to run vsync. I can't launch demo-alpha > sloginfo : When I run io-graphics I've got the following error : Oct 15 15:07:47 6 8 0 Primary active: 0 9 7 Oct 15 15:07:58 6 8 0 VGA primary : bus 0x0 dev/func 0x9 Oct 15 15:07:58 6 8 0 Found 1 PCI/AGP display devices Oct 15 15:07:58 6 8 0 pci_init: found PCI device 1022:2081 Oct 15 15:07:58 6 8 0 No config file specified Oct 15 15:07:59 6 8 0 Primary active: 0 9 7 Il I launch Photon binary and then phcalc (for example), I have : "unable to attach to font server, pf_attach() : No such file or directory" "Ap: Unable to locate Photon (2)" If I run phfont I have : "PfAttachLocalDllArgv() : Invalid argument " and the following slog : Oct 15 15:07:59 6 8 0 Primary active: 0 9 7 Oct 15 15:12:42 1 8 0 phfont: init... Oct 15 15:12:42 1 8 0 phfont: unable to load font extension rules If I run ph script I have : "Unable to start graphics driver(s)" and the followin slog : Oct 15 15:16:46 1 8 0 phfont.so: init... Oct 15 15:16:46 1 8 0 phfont.so: unable to load font extension rules Oct 15 15:16:46 2 8 0 io-graphics: FAIL PfAttachLocalDll(): Invalid argument, please verify font server configuration. Oct 15 15:16:46 2 8 0 fontserver_setup() My script is attached. My environment variables are defined hereafter : HOME=/ PATH=/proc/boot:/bin:/usr/bin:/usr/sbin:/sbin:/APD:/usr/photon/bin LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll PHOTON_PATH=/usr/photon PHOTON2_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont setconf _CS_LIBPATH :/proc/boot:/lib/dll:/dev/shmem:/lib:/usr/lib:/lib/dll:/lib/dll/font:/usr/photon/lib I'm running QNX 6.5.0. My board is a Rhodeus Geode (AMD 500Mghz) : http://www.diamondsystems.com/products/rhodeus My starting point was this official BSP : http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/AmdGeodeLxdb800 But I had to change things (surcvh as realtek driver)... I use devg-lx800.so graphic library. Any help would be appreciated. Thanks. Mon, 15 Oct 2012 13:35:13 GMT http://community.qnx.com/sf/go/post96328 KB 2012-10-15T13:35:13Z http://community.qnx.com/sf/go/post95938 devi-hid for armle-v7 is available from QNX 6.5.0 SP1 Mon, 01 Oct 2012 03:24:56 GMT http://community.qnx.com/sf/go/post95938 Philip Endaya 2012-10-01T03:24:56Z http://community.qnx.com/sf/go/post95905 I thought BITMAPV5HEADER has been around for a while since it was supported from Windows 98 onwards. Thanks Derek! Fri, 28 Sep 2012 03:43:48 GMT http://community.qnx.com/sf/go/post95905 Philip Endaya 2012-09-28T03:43:48Z http://community.qnx.com/sf/go/post95876 650 supported v4, which was the latest at the initial 650 time of release. -----Original Message----- From: Philip Endaya [mailto:community-noreply@qnx.com] Sent: September-27-12 2:51 AM To: advanced-graphics Subject: BITMAPV5HEADER support Hi, After some bmp codec soure code digging (bmp.h), it seems that QNX 6.5.0 only supports up to BITMAPV4HEADER but according to QNX documentation it provides full Microsoft BMP support for all known variants (http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.gf_dev_guide/images.html). Can someone confirm this? BR, Philip _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post95870 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Thu, 27 Sep 2012 12:59:06 GMT http://community.qnx.com/sf/go/post95876 Derek Leach 2012-09-27T12:59:06Z http://community.qnx.com/sf/go/post95870 Hi, After some bmp codec soure code digging (bmp.h), it seems that QNX 6.5.0 only supports up to BITMAPV4HEADER but according to QNX documentation it provides full Microsoft BMP support for all known variants (http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.gf_dev_guide/images.html). Can someone confirm this? BR, Philip Thu, 27 Sep 2012 06:50:31 GMT http://community.qnx.com/sf/go/post95870 Philip Endaya 2012-09-27T06:50:31Z http://community.qnx.com/sf/go/post95434 Ok, glad you got it going. -----Original Message----- From: Joe Thompson [mailto:community-noreply@qnx.com] Sent: September-06-12 3:29 PM To: advanced-graphics Subject: Re: libffb.so Issues on Poulsbo Board Must be a driver conflict I stripped everything I didn't need from the OS and finally got graphics started using the poulsbo driver. Unfortunately I didn't do this systematically so I have no idea which driver or file was causing the problem _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post95421 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Fri, 07 Sep 2012 12:39:58 GMT http://community.qnx.com/sf/go/post95434 Derek Leach 2012-09-07T12:39:58Z http://community.qnx.com/sf/go/post95433 True, but is there any way that another code path could have modified the context? -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: September-06-12 5:09 PM To: advanced-graphics Subject: Re: RE: gf_draw_blit2() - problem with bigger surface size I believe that the gf_context_t is inited properly. Here is a part of code responsible for drawing: gf_draw_begin (context); gf_draw_blit2 (context, img_surf, NULL, 0, 0, 639, 479, 0, 0); gf_draw_flush (context); gf_draw_end (context); nothing specific but fails. When I do a blit2() operation more often but on smaller area then everything is ok: gf_draw_begin (context); gf_draw_blit2 (context, img_surf, NULL, 0, 0, BUFLEN*2-1, 0, 0, index*2); gf_draw_blit2 (context, img_surf, NULL, 0, 0, BUFLEN*2-1, 0, 0, index*2+1); gf_draw_flush (context); gf_draw_end (context); BUFLEN is defined as 320. In both examples img_suf is connected with the same 640x480 target area. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post95423 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Fri, 07 Sep 2012 12:37:54 GMT http://community.qnx.com/sf/go/post95433 Derek Leach 2012-09-07T12:37:54Z http://community.qnx.com/sf/go/post95426 > I believe that the gf_context_t is inited properly. > > Here is a part of code responsible for drawing: > gf_draw_begin (context); > gf_draw_blit2 (context, img_surf, NULL, 0, 0, 639, 479, 0, 0); > gf_draw_flush (context); > gf_draw_end (context); > nothing specific but fails.> > When I do a blit2() operation more often but on smaller area then everything > is ok: > gf_draw_begin (context); > gf_draw_blit2 (context, img_surf, NULL, 0, 0, BUFLEN*2-1, 0, 0, index*2); > gf_draw_blit2 (context, img_surf, NULL, 0, 0, BUFLEN*2-1, 0, 0, index*2+1); > > gf_draw_flush (context); > gf_draw_end (context); > BUFLEN is defined as 320. > > In both examples img_suf is connected with the same 640x480 target area. Hi, What will happen in case of using static picture in img_surf, like previous captured frame? Thanks. Fri, 07 Sep 2012 08:15:36 GMT http://community.qnx.com/sf/go/post95426 Mike Gorchak 2012-09-07T08:15:36Z http://community.qnx.com/sf/go/post95423 I believe that the gf_context_t is inited properly. Here is a part of code responsible for drawing: gf_draw_begin (context); gf_draw_blit2 (context, img_surf, NULL, 0, 0, 639, 479, 0, 0); gf_draw_flush (context); gf_draw_end (context); nothing specific but fails. When I do a blit2() operation more often but on smaller area then everything is ok: gf_draw_begin (context); gf_draw_blit2 (context, img_surf, NULL, 0, 0, BUFLEN*2-1, 0, 0, index*2); gf_draw_blit2 (context, img_surf, NULL, 0, 0, BUFLEN*2-1, 0, 0, index*2+1); gf_draw_flush (context); gf_draw_end (context); BUFLEN is defined as 320. In both examples img_suf is connected with the same 640x480 target area. Thu, 06 Sep 2012 21:09:23 GMT http://community.qnx.com/sf/go/post95423 Jacek Rudnicki 2012-09-06T21:09:23Z http://community.qnx.com/sf/go/post95421 Must be a driver conflict I stripped everything I didn't need from the OS and finally got graphics started using the poulsbo driver. Unfortunately I didn't do this systematically so I have no idea which driver or file was causing the problem Thu, 06 Sep 2012 19:28:32 GMT http://community.qnx.com/sf/go/post95421 Joe Thompson 2012-09-06T19:28:32Z http://community.qnx.com/sf/go/post95386 Someone here fixed something similar in another unrelated piece of software, where the gf_context_t was not inited properly, and we were getting similar behaviour. -----Original Message----- From: Mike Gorchak [mailto:community-noreply@qnx.com] Sent: September-05-12 1:48 AM To: advanced-graphics Subject: Re: gf_draw_blit2() - problem with bigger surface size > Does mean that hardware is too slow ? Maybe, do you using plain blit2 or with additional context flags enabled, like chroma, etc? > Or maybe I'm doing something wrong ? I've seen similar behavior when forgot to use flush at the end of picture rendering in case if you have mixed environment, like software+hardware operations on the same surface. Two or more consecutive blit2()s without flush() can be optimized by hardware, you will get the last blit2() result. There are few possible issues: 1) You are not using flush() for blit2() operation. And blit2() is the only function which is called. Hardware will take video memory content for blitting in asynchronous way. For example, 1/1000 of sec is a delay between command to graphics controller has been issued and real blit2() execution in hardware. But in next 1/100000 sec you will get 3-4 optimized blit2() operations, while content of video memory was changed partially. 2) In the same time your application can use some graphics operations which are implemented in software. For example, output of some text and picture to the same surface. This is a race condition between software text rendering and hardware blit2(), so some strange visible artifacts could be observed. It depends on a GPU caching policy. So correct operations sequence will be blit2() -> flush() -> put_text("FPS: %d"). 3) You are updating your video frame content asynchronously comparing to blit2() operation. For example, there is possible such situation: two tasks are not synchronized, one is filling data which it obtains from camera and second one is doing blit2() + flush(). Due to asynchronous nature of GPU, it can execute blit2() in the same time when changing of video frame content is in process. In such case double buffering for managing video stream will be a solution. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post95374 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Wed, 05 Sep 2012 12:40:41 GMT http://community.qnx.com/sf/go/post95386 Derek Leach 2012-09-05T12:40:41Z http://community.qnx.com/sf/go/post95374 > Does mean that hardware is too slow ? Maybe, do you using plain blit2 or with additional context flags enabled, like chroma, etc? > Or maybe I'm doing something wrong ? I've seen similar behavior when forgot to use flush at the end of picture rendering in case if you have mixed environment, like software+hardware operations on the same surface. Two or more consecutive blit2()s without flush() can be optimized by hardware, you will get the last blit2() result. There are few possible issues: 1) You are not using flush() for blit2() operation. And blit2() is the only function which is called. Hardware will take video memory content for blitting in asynchronous way. For example, 1/1000 of sec is a delay between command to graphics controller has been issued and real blit2() execution in hardware. But in next 1/100000 sec you will get 3-4 optimized blit2() operations, while content of video memory was changed partially. 2) In the same time your application can use some graphics operations which are implemented in software. For example, output of some text and picture to the same surface. This is a race condition between software text rendering and hardware blit2(), so some strange visible artifacts could be observed. It depends on a GPU caching policy. So correct operations sequence will be blit2() -> flush() -> put_text("FPS: %d"). 3) You are updating your video frame content asynchronously comparing to blit2() operation. For example, there is possible such situation: two tasks are not synchronized, one is filling data which it obtains from camera and second one is doing blit2() + flush(). Due to asynchronous nature of GPU, it can execute blit2() in the same time when changing of video frame content is in process. In such case double buffering for managing video stream will be a solution. Wed, 05 Sep 2012 05:47:36 GMT http://community.qnx.com/sf/go/post95374 Mike Gorchak 2012-09-05T05:47:36Z http://community.qnx.com/sf/go/post95372 Hardware: Congatec Conga-CA COM Express module (Intel Atom Z510/Intel US15W) Trying to bring graphics up on this board using the generic X86 bsp. Started off with the OEM supplied bsp but now am running into the same issue. As soon as I add the libffb.so driver to the OS, the board will no longer boot and I am left looking at a display of shifting colors. The crash is before anything is running on the system so I can't get any log information or debug information. Have tried using io-display with both the Poulsbo graphics driver and the generic vesabios, the problem appears to be in the common libffb though so I'm stuck at a dead-end... Will be embarrassing to have to resort to a text-based gui! Has anybody managed to get graphics support working on an Atom-based board? Tue, 04 Sep 2012 21:43:34 GMT http://community.qnx.com/sf/go/post95372 Joe Thompson 2012-09-04T21:43:34Z http://community.qnx.com/sf/go/post95236 In the our system a video stream is received from Ethernet device. And then when the all data is already collected picture is displayed. Can a shared interrupt of the ethernet and graphics controller have an impact for application performance: io-pkt-v4-hc --> irq5, io-graphics / io-display --> irq5 ? Or better idea is to separate interrupts for both devices i.e. : io-pkt-v4-hc --> irq5, io-graphics / io-display --> irq10 ? Tue, 28 Aug 2012 20:48:26 GMT http://community.qnx.com/sf/go/post95236 Jacek Rudnicki 2012-08-28T20:48:26Z http://community.qnx.com/sf/go/post94943 I have attached picture that shows a black area. Rest from image lines are displayed properly. Has anybody idea whay these black lines are visible and how can I get rid of them ? Sun, 19 Aug 2012 17:27:15 GMT http://community.qnx.com/sf/go/post94943 Jacek Rudnicki 2012-08-19T17:27:15Z http://community.qnx.com/sf/go/post94942 In my application I had to call the gf_draw_blit2() very often. When size of the image is 320x240: gf_draw_blit2 (context, img_surf, NULL, 0, 0, 319, 239, 0, 0); then everything works fine. When size of the image is 640x480 gf_draw_blit2 (context, img_surf, NULL, 0, 0, 639, 479, 0, 0); several consecutive lines in the window are black (not rendered at all). Does mean that hardware is too slow ? Or maybe I'm doing something wrong ? I'm testing against the devg-i830.so driver (Device Id: 0x2582). Sun, 19 Aug 2012 12:52:09 GMT http://community.qnx.com/sf/go/post94942 Jacek Rudnicki 2012-08-19T12:52:09Z http://community.qnx.com/sf/go/post94734 I'm also having troubles with libimg. After adding libimg the app crash when I execute if (BPS_SUCCESS != screen_request_events(screen_cxt)) Any idea? I added the -limg on linking stage, its ok? Thanks Thu, 09 Aug 2012 19:54:52 GMT http://community.qnx.com/sf/go/post94734 Federico Vidueiro 2012-08-09T19:54:52Z http://community.qnx.com/sf/go/post94680 Yes, in the Foundry27 Graphics project, there is examples showing this. -----Original Message----- From: Jacek Rudnicki [mailto:community-noreply@qnx.com] Sent: August-07-12 12:56 PM To: advanced-graphics Subject: Combining GF and Photon together There is native application written under Photon and similar program that uses Graphics Framework API. How to mix them together ? Is there any documentation which describes such process ? Jacek _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post94679 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Tue, 07 Aug 2012 16:57:38 GMT http://community.qnx.com/sf/go/post94680 Derek Leach 2012-08-07T16:57:38Z http://community.qnx.com/sf/go/post94679 There is native application written under Photon and similar program that uses Graphics Framework API. How to mix them together ? Is there any documentation which describes such process ? Jacek Tue, 07 Aug 2012 16:55:56 GMT http://community.qnx.com/sf/go/post94679 Jacek Rudnicki 2012-08-07T16:55:56Z http://community.qnx.com/sf/go/post94678 I have successfully generated 8-bits gray palette as follows: gf_palette_t palette; gf_color_t g8pal[256]; ... for (i = 0; i < 256; i++) { g8pal[i] = (0xff << 24) | ((i & 0xff) << 16) | ((i & 0xff) << 8) | (i & 0xff); } palette.ncolors = 256; palette.colors = (gf_color_t*)g8pal; It works fine with rgb565 format for io-display. Tue, 07 Aug 2012 16:51:52 GMT http://community.qnx.com/sf/go/post94678 Jacek Rudnicki 2012-08-07T16:51:52Z http://community.qnx.com/sf/go/post94659 I have changed pixel_format in the display.conf file from "rgb565" onto "pal8" value. Now the gf_draw_blit2() works while with "rgb565" screen is dark all the time. Picture is visible but colors are not correct. I wonder how to generate 8-bits gray palette under GF ? Mon, 06 Aug 2012 20:00:03 GMT http://community.qnx.com/sf/go/post94659 Jacek Rudnicki 2012-08-06T20:00:03Z http://community.qnx.com/sf/go/post94656 I am having the same problem, I can't find 'g8pal'. It looks like it should be a pointer to a palette of type 'img_color_t' which is just an integer. So what should the g8pal palette look like. I am new to QNX and GF graphics and am finding it hard to get things working as a lot of info is missing from QNX examples. Mon, 06 Aug 2012 09:40:28 GMT http://community.qnx.com/sf/go/post94656 Richard Soden 2012-08-06T09:40:28Z http://community.qnx.com/sf/go/post94650 Hi, Application is responsible for displaying data (8-bits/pixel graymap). Data is received from Ethernet interface and displayed when image is complete (all frames were already gathered). Under Photon as solution I use PhCreateImage() and PgDrawPhImage() functions. BTW Is there any other way in order to achive a better performane in Photon ? It's time to move to GF. In the "Working with Images" chapter there is a following code: palette.ncolors = 256; palette.colors = (img_color_t*)g8pal; but compiler says that g8pal is undefined. How can I use this ? Should I generate array of colors itself (in similar way that was done under Photon, PgSetPalette()) ? What function should I use under GF as equivalent ? I found the gf_draw_image() but this function doesn't support GF_FORMAT_PAL8... Regards, Jacek Sun, 05 Aug 2012 20:28:59 GMT http://community.qnx.com/sf/go/post94650 Jacek Rudnicki 2012-08-05T20:28:59Z http://community.qnx.com/sf/go/post94376 Ok, thanks Derek. I've given the test code we're using to support, hopefully they can come up with some examples of how to make this work. Thanks again, Don Fri, 20 Jul 2012 21:55:39 GMT http://community.qnx.com/sf/go/post94376 Don Meyer 2012-07-20T21:55:39Z http://community.qnx.com/sf/go/post94366 Ok, it looks like the imx51/53 driver supports this, please send your test case through support. -----Original Message----- From: Don Meyer [mailto:community-noreply@qnx.com] Sent: July-19-12 6:53 PM To: advanced-graphics Subject: Re: RE: RE: Displaying layer 0 gf graphics with Photon in layer 1? This is on an iMX53 eval board, the graphics are those integrated into the Cortex chip. It does support two layers in hardware, and we have Photon running on layer 1 (versus the default layer 0). _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post94353 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Fri, 20 Jul 2012 13:00:31 GMT http://community.qnx.com/sf/go/post94366 Derek Leach 2012-07-20T13:00:31Z http://community.qnx.com/sf/go/post94353 This is on an iMX53 eval board, the graphics are those integrated into the Cortex chip. It does support two layers in hardware, and we have Photon running on layer 1 (versus the default layer 0). Thu, 19 Jul 2012 22:52:59 GMT http://community.qnx.com/sf/go/post94353 Don Meyer 2012-07-19T22:52:59Z http://community.qnx.com/sf/go/post94349 You are attaching to the same layer as Photon? What graphics chipset are you using? -----Original Message----- From: Don Meyer [mailto:community-noreply@qnx.com] Sent: July-19-12 2:53 PM To: advanced-graphics Subject: Re: RE: Displaying layer 0 gf graphics with Photon in layer 1? Thanks for the reply. I did post essentially the same question in the Photon forum, and then posted it here today as I hadn't gotten any responses there yet. Not certian which form is most appropriate for this question - it seems to span both. I've gotten a similar suggestion from tech support (although with less detail, more of a general direction). I've been going this way, so good to know that I'm on the right path. Not having much luck however. I'm attaching to the layer that Photon is using with a passive attach. Then, I set the chroma: gf_chroma_t chroma; chroma.mode = GF_CHROMA_OP_SRC_MATCH | GF_CHROMA_OP_NO_DRAW; chroma.color0 = 0xff0000; chroma.color1 = 0; // unused gf_layer_set_chroma( layer, &chroma ); gf_layer_update( layer, 0 ); After that is done, we create our window and a PtOSContainer, whose background is set to full red. That red background is still drawing however. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post94348 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Thu, 19 Jul 2012 19:35:35 GMT http://community.qnx.com/sf/go/post94349 Derek Leach 2012-07-19T19:35:35Z http://community.qnx.com/sf/go/post94348 Thanks for the reply. I did post essentially the same question in the Photon forum, and then posted it here today as I hadn't gotten any responses there yet. Not certian which form is most appropriate for this question - it seems to span both. I've gotten a similar suggestion from tech support (although with less detail, more of a general direction). I've been going this way, so good to know that I'm on the right path. Not having much luck however. I'm attaching to the layer that Photon is using with a passive attach. Then, I set the chroma: gf_chroma_t chroma; chroma.mode = GF_CHROMA_OP_SRC_MATCH | GF_CHROMA_OP_NO_DRAW; chroma.color0 = 0xff0000; chroma.color1 = 0; // unused gf_layer_set_chroma( layer, &chroma ); gf_layer_update( layer, 0 ); After that is done, we create our window and a PtOSContainer, whose background is set to full red. That red background is still drawing however. Thu, 19 Jul 2012 18:53:07 GMT http://community.qnx.com/sf/go/post94348 Don Meyer 2012-07-19T18:53:07Z http://community.qnx.com/sf/go/post94346 I just answer a similar question in the Photon forum: I have not done this approach lately, but try these suggestions. You could set the fill colour to Pg_TRANSPARENT, unless you are using a PtOSContainer. Now, I think this is the better approach here: If you are using a PtOSContainer, set the fill colour to something not common, then set the chroma on the layer to that value, and no draw. -----Original Message----- From: Don Meyer [mailto:community-noreply@qnx.com] Sent: July-19-12 1:33 PM To: advanced-graphics Subject: Displaying layer 0 gf graphics with Photon in layer 1? Is there any way to have Photon's background either not be drawn, or drawn as "transparent"? I'm trying to render some graphics on layer 0 using the gf library, and have some Photon objects overlay them, with Photon on layer 1. The problem is, Photon draws a background which totally obscures what's rendered on layer 0. Thanks! _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post94343 To cancel your subscription to this discussion, please e-mail advanced-graphics-unsubscribe@community.qnx.com Thu, 19 Jul 2012 17:50:08 GMT http://community.qnx.com/sf/go/post94346 Derek Leach 2012-07-19T17:50:08Z http://community.qnx.com/sf/go/post94343 Is there any way to have Photon's background either not be drawn, or drawn as "transparent"? I'm trying to render some graphics on layer 0 using the gf library, and have some Photon objects overlay them, with Photon on layer 1. The problem is, Photon draws a background which totally obscures what's rendered on layer 0. Thanks! Thu, 19 Jul 2012 17:32:30 GMT http://community.qnx.com/sf/go/post94343 Don Meyer 2012-07-19T17:32:30Z http://community.qnx.com/sf/go/post93716 Hi, I successfully make a sample application of image loading using libimg. Now i want to is it possible to do image editing feature using Limbing. If yes then any documentation or source for this. Mon, 18 Jun 2012 09:05:17 GMT http://community.qnx.com/sf/go/post93716 Megha Sanghvi 2012-06-18T09:05:17Z http://community.qnx.com/sf/go/post93684 Hi, I am new to QNX development. Currently i am developing Native application for BB10 in which i come to work with QNX native. I want to do image editing in native can anyone help me how can i achieve this? I tried to find libimg library but not get that much help. I make a sample application using libimg where i load the image but gives many error. I attached my source code for the same to load the image please help me on this. Fri, 15 Jun 2012 05:37:57 GMT http://community.qnx.com/sf/go/post93684 Megha Sanghvi 2012-06-15T05:37:57Z http://community.qnx.com/sf/go/post93239 > I am using TI beagle-board. When I use gf-calib for calibration of my touch > screen, the following message displays: > # gf-calib > Number of layers: 3 > Resolution: 720x400, refresh = 60Hz > layer_idx=0 > gf_cursor_set(): error = 7 > > I have no idea how to solve it. Any help? Try the -D option. Also, you need to have "img.conf" under /etc/system/config, plus the img_codec so's in your library path. - Malte Tue, 22 May 2012 10:28:00 GMT http://community.qnx.com/sf/go/post93239 Malte Mundt 2012-05-22T10:28:00Z http://community.qnx.com/sf/go/post92952 I am using TI beagle-board. When I use gf-calib for calibration of my touch screen, the following message displays: # gf-calib Number of layers: 3 Resolution: 720x400, refresh = 60Hz layer_idx=0 gf_cursor_set(): error = 7 I have no idea how to solve it. Any help? Fri, 11 May 2012 01:55:53 GMT http://community.qnx.com/sf/go/post92952 David Yang 2012-05-11T01:55:53Z http://community.qnx.com/sf/go/post91489 bump Fri, 10 Feb 2012 19:54:08 GMT http://community.qnx.com/sf/go/post91489 Devan Lippman 2012-02-10T19:54:08Z http://community.qnx.com/sf/go/post91261 Hi John, Did you ever find an answer to this? Looks like I'm following down the same road now. Thanks, Devan Tue, 31 Jan 2012 22:18:58 GMT http://community.qnx.com/sf/go/post91261 Devan Lippman 2012-01-31T22:18:58Z http://community.qnx.com/sf/go/post90739 Hi , When dealing with proportional fonts, sometimes the vectors of one glyph run into the vectors of another. This is especially evident when using a font such as Nuptial BT. We need to take special care when repairing damage to such fonts. PfExtentTextCharPositions() <http://www.qnx.com/developers/docs/6.4.1/photon/lib_ref/pf/pfextenttext charpositions.html> addresses this issue in Photon environment. This position is where you should draw the next character. If you use the PF_CHAR_DRAW_POSITIONS flag, the bearing x of the following character isn't applied to the position, which is useful when you're placing cursors. What is the equivalent on PfExtentTextCharPositions() <http://www.qnx.com/developers/docs/6.4.1/photon/lib_ref/pf/pfextenttext charpositions.html> in Graphics Framework ? Please let me know regarding this. Thanks, Karthik Kannan M General Electric - Transportation Thu, 22 Dec 2011 11:11:49 GMT http://community.qnx.com/sf/go/post90739 Karthik Kannan 2011-12-22T11:11:49Z http://community.qnx.com/sf/go/post90709 Christophe, You were right, the problem was with another library included in devg-flat.so that was not present in the library path. Thanks a lot for your valuable help. Regards, Nicolas Wed, 21 Dec 2011 07:56:15 GMT http://community.qnx.com/sf/go/post90709 Nicolas Pinault 2011-12-21T07:56:15Z http://community.qnx.com/sf/go/post90694 Hello, Probably the problem was not with your library but with another one included with your library. Try this: # DL_DEBUG=1 io-display -c /mnt/sdhc/gf/display.conf -d vid=0x10ee,did=0x6024 And check the missing library. Christophe Hannoyer -----Message d'origine----- De : Nicolas Pinault [mailto:community-noreply@qnx.com] Envoyé : mardi 20 décembre 2011 17:11 À : advanced-graphics Objet : Can't load driver dll Hello, I'm trying to run graphics on my system (Freescale P4080 PowerPC). I'm using a self made driverl derived from devg-flat. To run my driver, I do the folowing : # io-display -c /mnt/sdhc/gf/display.conf -d vid=0x10ee,did=0x6024 Could not initialize device "vid=0x10ee,did=0x6024": No such file or directory Check 'sloginfo' output for more details io-display failed to initialise # sloginfo -c Time Sev Major Minor Args Aug 02 01:41:36 2 8 200 devg-flat.so: gfpr_dlopen: Library cannot be found Here is the display.conf file content : device { drivername=flat vid=0x10ee did=0x6024 deviceindex=0 memopts=/mnt/sdhc/gf/flat.conf display { xres=1920 yres=1080 refresh=30 pixel_format=argb8888 } } The driver devg-flat.so is in /mnt/sdhc/lib which is added to LD_LIBRARY_PATH. It is also added to procnto LD_LIBRARY_PATH in build file. I spent hours to find why the library is not found. Can anybody help me ? Regards, Nicolas _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post90693 Tue, 20 Dec 2011 16:42:37 GMT http://community.qnx.com/sf/go/post90694 Christophe Hannoyer 2011-12-20T16:42:37Z http://community.qnx.com/sf/go/post90693 Hello, I'm trying to run graphics on my system (Freescale P4080 PowerPC). I'm using a self made driverl derived from devg-flat. To run my driver, I do the folowing : # io-display -c /mnt/sdhc/gf/display.conf -d vid=0x10ee,did=0x6024 Could not initialize device "vid=0x10ee,did=0x6024": No such file or directory Check 'sloginfo' output for more details io-display failed to initialise # sloginfo -c Time Sev Major Minor Args Aug 02 01:41:36 2 8 200 devg-flat.so: gfpr_dlopen: Library cannot be found Here is the display.conf file content : device { drivername=flat vid=0x10ee did=0x6024 deviceindex=0 memopts=/mnt/sdhc/gf/flat.conf display { xres=1920 yres=1080 refresh=30 pixel_format=argb8888 } } The driver devg-flat.so is in /mnt/sdhc/lib which is added to LD_LIBRARY_PATH. It is also added to procnto LD_LIBRARY_PATH in build file. I spent hours to find why the library is not found. Can anybody help me ? Regards, Nicolas Tue, 20 Dec 2011 16:11:25 GMT http://community.qnx.com/sf/go/post90693 Nicolas Pinault 2011-12-20T16:11:25Z http://community.qnx.com/sf/go/post90683 Do you solve you problem ? Have you got devi-hid for armle-v7 ? thanks, regards Mon, 19 Dec 2011 15:04:55 GMT http://community.qnx.com/sf/go/post90683 KUBIT Stéphane(deleted) 2011-12-19T15:04:55Z http://community.qnx.com/sf/go/post90352 Hello, I need to copy an entire frame buffer (src) to the screen (dst). Would the function PgContextBlitArea() do the trick? Any help is appreciated. Thanks, -Zahira Tue, 29 Nov 2011 22:23:54 GMT http://community.qnx.com/sf/go/post90352 Zahira Ammarguellat 2011-11-29T22:23:54Z http://community.qnx.com/sf/go/post89931 Hi, I am trying to display a video from a memory buffer into my display. I will be using the Beagle BSP for OMAP3730. Is there any functionality on GF to display video from the memory buffer? Thanks in advance! Tue, 08 Nov 2011 10:39:20 GMT http://community.qnx.com/sf/go/post89931 Felipe Santana 2011-11-08T10:39:20Z http://community.qnx.com/sf/go/post89653 Those functions were written for some custom work and were never included in a general product release. The technote was erroneously included in the documentation, but has since been removed. Steve Reid (stever@qnx.com) Technical Editor QNX Software Systems -----Original Message----- From: Nikshep Patil [mailto:community-noreply@qnx.com] Sent: Wednesday, October 26, 2011 10:29 AM To: advanced-graphics Subject: Re: RE: mmap_peer and mmap64_peer - Undefined reference error Any update on this...? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post89648 Wed, 26 Oct 2011 16:53:13 GMT http://community.qnx.com/sf/go/post89653 Steve Reid 2011-10-26T16:53:13Z http://community.qnx.com/sf/go/post89648 Any update on this...? Wed, 26 Oct 2011 14:29:12 GMT http://community.qnx.com/sf/go/post89648 Nikshep Patil 2011-10-26T14:29:12Z http://community.qnx.com/sf/go/post89527 If I understand you correctly you should try something like this: -- disable all ROP operation -- set fgcolor to your "bgcolor" -- draw a solid rectangle (gf_draw_rect()) where you need it, let's say @ X,Y -- set the pattern -- set the ROP -- set fgcolor to your "fgcolor" -- draw a solid rectangle again @ X,Y Fri, 21 Oct 2011 12:36:47 GMT http://community.qnx.com/sf/go/post89527 Misha Nefedov 2011-10-21T12:36:47Z http://community.qnx.com/sf/go/post89520 Hi Misha, thanks for your help. I have an another question, how can I use this 8x8 value combine with ROPs(gf_context_set_rop()); for example, I want to draw an 8x8 rectangle and set all the needed values like this, mypattern[8] = {0x00, 0x44, 0x00,0x11, 0x00,0x44, 0x00,0x11 }; fgcolor: 0xFFFF0000 bgcolor: 0xFF0000FF rop: GF_ROP_PDSnaon what is the formula to get the result ? Fri, 21 Oct 2011 09:40:02 GMT http://community.qnx.com/sf/go/post89520 shen xifeng 2011-10-21T09:40:02Z http://community.qnx.com/sf/go/post89492 Thanks Thomas. Does that mean I cannot use the mmap_peer()/mmap64_peer() anymore...? Is there an alternative to these functions in 6.5...? I see this documentation on mmap_peer functions - http://www.qnx.com/developers/docs/6.4.1/neutrino/technotes/mmap_and_munmap_peer.html Thu, 20 Oct 2011 14:44:32 GMT http://community.qnx.com/sf/go/post89492 Nikshep Patil 2011-10-20T14:44:32Z http://community.qnx.com/sf/go/post89490 I may be mistaken, but I believe they aren't part of libc any more in 6.5. Regards, Thomas -----Original Message----- From: Nikshep Patil [mailto:community-noreply@qnx.com] Sent: Donnerstag, 20. Oktober 2011 16:27 To: advanced-graphics Subject: mmap_peer and mmap64_peer - Undefined reference error I am trying to use mmap64_peer() in my resource manager. I get "Undefined reference to mmap64_peer()" error. Same with mmap_peer(). Including "sys/mman.h" does not help. What header file/library do I need to include to get mmap64_peer() to work...? Thank you. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post89488 Thu, 20 Oct 2011 14:38:07 GMT http://community.qnx.com/sf/go/post89490 Thomas Haupt 2011-10-20T14:38:07Z http://community.qnx.com/sf/go/post89488 I am trying to use mmap64_peer() in my resource manager. I get "Undefined reference to mmap64_peer()" error. Same with mmap_peer(). Including "sys/mman.h" does not help. What header file/library do I need to include to get mmap64_peer() to work...? Thank you. Thu, 20 Oct 2011 14:27:25 GMT http://community.qnx.com/sf/go/post89488 Nikshep Patil 2011-10-20T14:27:25Z http://community.qnx.com/sf/go/post89451 The pattern is a pointer to an array of characters defining the pattern bitmap. This array should define an 8X8 single bit/pixel bitmap packing 8 pixels/byte, with no padding. Wed, 19 Oct 2011 13:38:51 GMT http://community.qnx.com/sf/go/post89451 Misha Nefedov 2011-10-19T13:38:51Z http://community.qnx.com/sf/go/post89441 Hi , from the help documents, it says the second parameter of this function is pattern which is A pointer to the bitmap containing the pattern. my question is how can I define the bitmap ? Wed, 19 Oct 2011 08:41:37 GMT http://community.qnx.com/sf/go/post89441 shen xifeng 2011-10-19T08:41:37Z http://community.qnx.com/sf/go/post89358 I'm trying to showing some picture by using GF, my application seems to be running OK but there is nothing displayed on the screen. However I run the vsync sample app and it works fine. Is it possible to get the source code of it? Or anybody could tell me about the details of how vsync works. Your help would be appreciated. Thu, 13 Oct 2011 07:23:08 GMT http://community.qnx.com/sf/go/post89358 marvin zhu 2011-10-13T07:23:08Z http://community.qnx.com/sf/go/post88943 Brian, Did you ever get anywhere with this? I'm also looking for devi-hid drivers for armle-v7 Thanks! Mon, 19 Sep 2011 22:11:54 GMT http://community.qnx.com/sf/go/post88943 Yusuf Shirazi 2011-09-19T22:11:54Z http://community.qnx.com/sf/go/post88789 I recommend posting your code -- so others can look at the code and may spot what the problem is. Mon, 12 Sep 2011 19:03:20 GMT http://community.qnx.com/sf/go/post88789 Misha Nefedov 2011-09-12T19:03:20Z http://community.qnx.com/sf/go/post88787 Hi, Can anyone tell me how to change the resolution or display preferences in photon in code? I know “phgrafx” does this. But this is in photon GUI. But I want to implement the same functionality in my code. In short, I like to know about the ways to reconfigure and restart photon with a new config file, after once the display is already been up. Thanks, Arun Johnson Mon, 12 Sep 2011 18:15:34 GMT http://community.qnx.com/sf/go/post88787 Arun Johnson 2011-09-12T18:15:34Z http://community.qnx.com/sf/go/post88774 Hello :) i want to write a .bmp file from raw pixel data. My Programm i have, listen on the ethernet for my Client and accept the Client when he connects. The Client send some data and there are raw pixel data. With a function named "const unsigned int* GetImage()" i get a pointer to the first pixel. My Pictures are 320(W) x 240(H). Now how can i display or save the raw pixel data? i hope for hints :) with best regards Mon, 12 Sep 2011 09:35:38 GMT http://community.qnx.com/sf/go/post88774 Juri Ostrowski 2011-09-12T09:35:38Z http://community.qnx.com/sf/go/post88667 Hi, I need to render a picture to the screen. I am trying to create a surface from my picture buffer using gf_surface_attach(). But the call fails with return value 7. The arguments to gf_surface_attach() seem correct. Could you help me with this...? Thanks Tue, 06 Sep 2011 20:55:55 GMT http://community.qnx.com/sf/go/post88667 Nikshep Patil 2011-09-06T20:55:55Z http://community.qnx.com/sf/go/post88552 Hi, Is there a way to use io-winmgr to bring a window to the front? win_globals.disp_data[0]->win_list = 0x80000003, 0x80000000, 0x80000002 win_globals.disp_data[0]->planes[0].buffered[0].win_list = (null) win_globals.disp_data[0]->planes[0].buffered[1].win_list = (null) win_globals.disp_data[0]->planes[1].buffered[0].win_list = 0x80000002, 0x80000003 win_globals.disp_data[0]->planes[1].buffered[1].win_list = (null) I see from its dump the window IDs. Can I send a msg to io-winmgr to bring window e.g. 0x80000002 or 3 to top? Using io-winmgr –sendev ??? -Hue Wed, 31 Aug 2011 20:10:38 GMT http://community.qnx.com/sf/go/post88552 Hue Vo 2011-08-31T20:10:38Z http://community.qnx.com/sf/go/post88200 To be honest I'm not sure when 6.5.0 was released any platforms with graphics were actually running armle-v7. A couple of customers running armle-v7 needed custom drivers and wrote their own. I checked whether the input DDK posted on the QNX website could be used to build a driver and was told: "The DDK won't work on 6.5.0, better to just get the imx25 BSP: http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/Freescale Imx253dsPdk and grab the source archive from it, it contains the input libs with the gf support and a sample driver." Maybe this is something you can try? Mike -----Original Message----- From: Brian Edmond [mailto:community-noreply@qnx.com] Sent: August 17, 2011 1:52 PM To: advanced-graphics Subject: devi-hid for armle-v7 Probably not the correct place for this but the input drivers were always kinda graphics. There are no devi drivers for armle-v7 targets. How does one get a mouse or keyboard input in 6.5? Brian _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post88172 Thu, 18 Aug 2011 15:24:01 GMT http://community.qnx.com/sf/go/post88200 Michael Van Reenen 2011-08-18T15:24:01Z http://community.qnx.com/sf/go/post88180 No idea how you can change the compression /quality :(, Check if img_load_resize_file() is of any use.... Regards, Lavin -----Original Message----- From: Ronald Burkey [mailto:community-noreply@qnx.com] Sent: Wednesday, August 17, 2011 10:38 PM To: advanced-graphics Subject: Re: Creating a PNG output file. [bcc][auto-ip] True. I don't lack space, so that doesn't actually concern me. But I gather you don't know how it can be done, so the point is moot. Thanks, Ron On 08/17/2011 12:02 PM, Lavin Pottekkat wrote: > Though i have not tried changing the compression techniques, i have seen noticeable difference in the size of the images created with different formats. > > Regards, > Lavin > ________________________________________ > From: Ronald Burkey [community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 9:52 PM > To: advanced-graphics > Subject: RE: Creating a PNG output file. > > One final (I hope) question: If JPGs were being output rather than > PNGs, how can the quality/compression be set? > > -- Ron > > _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post88170 Thu, 18 Aug 2011 07:15:03 GMT http://community.qnx.com/sf/go/post88180 Lavin Pottekkat 2011-08-18T07:15:03Z http://community.qnx.com/sf/go/post88172 Probably not the correct place for this but the input drivers were always kinda graphics. There are no devi drivers for armle-v7 targets. How does one get a mouse or keyboard input in 6.5? Brian Wed, 17 Aug 2011 17:51:32 GMT http://community.qnx.com/sf/go/post88172 Brian Edmond 2011-08-17T17:51:32Z http://community.qnx.com/sf/go/post88170 True. I don't lack space, so that doesn't actually concern me. But I gather you don't know how it can be done, so the point is moot. Thanks, Ron On 08/17/2011 12:02 PM, Lavin Pottekkat wrote: > Though i have not tried changing the compression techniques, i have seen noticeable difference in the size of the images created with different formats. > > Regards, > Lavin > ________________________________________ > From: Ronald Burkey [community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 9:52 PM > To: advanced-graphics > Subject: RE: Creating a PNG output file. > > One final (I hope) question: If JPGs were being output rather than > PNGs, how can the quality/compression be set? > > -- Ron > > Wed, 17 Aug 2011 17:08:18 GMT http://community.qnx.com/sf/go/post88170 Ronald Burkey 2011-08-17T17:08:18Z http://community.qnx.com/sf/go/post88169 Though i have not tried changing the compression techniques, i have seen noticeable difference in the size of the images created with different formats. Regards, Lavin ________________________________________ From: Ronald Burkey [community-noreply@qnx.com] Sent: Wednesday, August 17, 2011 9:52 PM To: advanced-graphics Subject: RE: Creating a PNG output file. One final (I hope) question: If JPGs were being output rather than PNGs, how can the quality/compression be set? -- Ron > -----Original Message----- > From: Lavin Pottekkat [mailto:community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 7:53 AM > To: advanced-graphics > Subject: RE: Creating a PNG output file. [bcc] > > Yes, you can change the mime type for different file formats. > > Regards, > Lavin > > -----Original Message----- > From: Ronald Burkey [mailto:community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 6:10 PM > To: advanced-graphics > Subject: Re: Creating a PNG output file. [bcc] > > I had just made that change about 10 seconds before your message > arrived. :-) I haven't gotten to the point yet where I can run the > code. I'll let you know what happens. > > I assume that if I want jpg or bmp, it's just a matter of changing the > mime type appropriately? > > Thanks! > Ron > > > On 08/17/2011 07:34 AM, Lavin Pottekkat wrote: > > Just now I noticed that you have RGBA8888, in this case I think you > should modify below lines highlighted below using '-->' > > Also pl make sure you configure the img.w/h appropriately. > > > > Cheers, > > Lavin > > > > -----Original Message----- > > From: Pottekkat, Lavin > > Sent: Wednesday, August 17, 2011 5:43 PM > > To: advanced-graphics > > Subject: RE: Creating a PNG output file. > > > > Hi Ronald, > > > > Try this it should work :) .... search for "Lavin" to see my comments > inline.... > > > > uint32_t *img_buf = NULL; > > uint32_t image_size = Max size of the RGB data buffer; > > int32_t result = EOK; > > > > img_lib_t ilib; > > img_codec_t codec_buf; > > int n_codecs; > > img_t img; > > io_stream_t *image_stream_fd; > > char mime[64]; > > uintptr_t temp_encode_data = 0; > > > > /* allocate (image_size/sizeof int-(4bytes)) elements of type int */ > > if (NULL == (img_buf = calloc((image_size / (sizeof(uint32_t))), > sizeof(uint32_t)))) { > > _error("%s: Memory allocation for %d bytes failed", __FUNCTION__, > image_size); > > return ENOMEM; > > } > > > > /* Lavin : copy the image RGB values linearly to the above allocated > img_buf, from your rectangular array in memory */ > > > > /* Lavin : at this point I assume that you have already copied the > image data to img_buf.*/ > > > > /* Lavin : NOTE: you can very well use your rectangular array directly > as image_buf as well :) */ > > > > > > //Attaching to the image library > > memset(&img,0,sizeof(img_t)); > > > > /* get the resolution details */ > > img.w = 1440; // 1440 or 960 , use accordingly > > img.h = 540; // 540, use accordingly > > > > img.format = IMG_FMT_RGBA8888; > > > > img.flags |= IMG_FORMAT | IMG_W | IMG_H | IMG_DIRECT; > > > > img.access.direct.data = img_buf; > > --> img.access.direct.stride = (img.w * 4 ); > > > > if ((result = img_lib_attach(&ilib)) != IMG_ERR_OK) { > > fprintf(stderr, "img_lib_attach() failed: %d\n", result); > > return result; > > } > > > > memset(mime, '\0', 64 ); > > sprintf(mime, "image/%s", "png"); > > > > if(EOK == (n_codecs = img_codec_list_bymime( ilib, > > mime, > > &codec_buf, > > 10 ))) > > { > > _error("%s: img_codec_list() No Codecs found on target !", > __FUNCTION__); > > return -1; > > } > > > > //convert the image_fd to stream_fd required by image libs. > > /* Lavin : here file_fs should be your xxx.png file fd after > open(...O_CREATE) */ > > if(NULL == (image_stream_fd = io_open( IO_FD, IO_WRITE, file_fd > ))) > > { > > _error("%s: io_open() failed: %d", __FUNCTION__); > > return -1; > > } > > > > //set the codec > > > > //Prepare to encode a frame to a stream > > if (img_encode_begin(codec_buf, > image_stream_fd,&temp_encode_data) != IMG_ERR_OK) > > { > > _error("%s: img_encode_begin() failed", __FUNCTION__); > > return -1; > > } > > > > if ( (result = img_encode_frame(codec_buf, image_stream_fd, > NULL,&img,&temp_encode_data)) != IMG_ERR_OK) > > { > > _error("%s: img_encode_frame() failed: %d", __FUNCTION__, > result); > > return -1; > > } > > > > (void)img_encode_finish(codec_buf, > image_stream_fd,&temp_encode_data); > > > > io_close( image_stream_fd ); > > > > /* done with img lib */ > > img_lib_detach(ilib); > > > > /* Lavin : Now your PNG fromat file is ready :) :) */ > > > > > > Regards, > > Lavin, > > > > -----Original Message----- > > From: Ronald Burkey [mailto:community-noreply@qnx.com] > > Sent: Friday, August 12, 2011 9:52 PM > > To: advanced-graphics > > Subject: Creating a PNG output file. > > > > I have a rectangular array in memory of RGB values (i.e., it is > IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. > How would this be done? > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post88079 > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post88149 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88150 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88152 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post88168 Wed, 17 Aug 2011 17:02:02 GMT http://community.qnx.com/sf/go/post88169 Lavin Pottekkat 2011-08-17T17:02:02Z http://community.qnx.com/sf/go/post88168 One final (I hope) question: If JPGs were being output rather than PNGs, how can the quality/compression be set? -- Ron > -----Original Message----- > From: Lavin Pottekkat [mailto:community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 7:53 AM > To: advanced-graphics > Subject: RE: Creating a PNG output file. [bcc] > > Yes, you can change the mime type for different file formats. > > Regards, > Lavin > > -----Original Message----- > From: Ronald Burkey [mailto:community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 6:10 PM > To: advanced-graphics > Subject: Re: Creating a PNG output file. [bcc] > > I had just made that change about 10 seconds before your message > arrived. :-) I haven't gotten to the point yet where I can run the > code. I'll let you know what happens. > > I assume that if I want jpg or bmp, it's just a matter of changing the > mime type appropriately? > > Thanks! > Ron > > > On 08/17/2011 07:34 AM, Lavin Pottekkat wrote: > > Just now I noticed that you have RGBA8888, in this case I think you > should modify below lines highlighted below using '-->' > > Also pl make sure you configure the img.w/h appropriately. > > > > Cheers, > > Lavin > > > > -----Original Message----- > > From: Pottekkat, Lavin > > Sent: Wednesday, August 17, 2011 5:43 PM > > To: advanced-graphics > > Subject: RE: Creating a PNG output file. > > > > Hi Ronald, > > > > Try this it should work :) .... search for "Lavin" to see my comments > inline.... > > > > uint32_t *img_buf = NULL; > > uint32_t image_size = Max size of the RGB data buffer; > > int32_t result = EOK; > > > > img_lib_t ilib; > > img_codec_t codec_buf; > > int n_codecs; > > img_t img; > > io_stream_t *image_stream_fd; > > char mime[64]; > > uintptr_t temp_encode_data = 0; > > > > /* allocate (image_size/sizeof int-(4bytes)) elements of type int */ > > if (NULL == (img_buf = calloc((image_size / (sizeof(uint32_t))), > sizeof(uint32_t)))) { > > _error("%s: Memory allocation for %d bytes failed", __FUNCTION__, > image_size); > > return ENOMEM; > > } > > > > /* Lavin : copy the image RGB values linearly to the above allocated > img_buf, from your rectangular array in memory */ > > > > /* Lavin : at this point I assume that you have already copied the > image data to img_buf.*/ > > > > /* Lavin : NOTE: you can very well use your rectangular array directly > as image_buf as well :) */ > > > > > > //Attaching to the image library > > memset(&img,0,sizeof(img_t)); > > > > /* get the resolution details */ > > img.w = 1440; // 1440 or 960 , use accordingly > > img.h = 540; // 540, use accordingly > > > > img.format = IMG_FMT_RGBA8888; > > > > img.flags |= IMG_FORMAT | IMG_W | IMG_H | IMG_DIRECT; > > > > img.access.direct.data = img_buf; > > --> img.access.direct.stride = (img.w * 4 ); > > > > if ((result = img_lib_attach(&ilib)) != IMG_ERR_OK) { > > fprintf(stderr, "img_lib_attach() failed: %d\n", result); > > return result; > > } > > > > memset(mime, '\0', 64 ); > > sprintf(mime, "image/%s", "png"); > > > > if(EOK == (n_codecs = img_codec_list_bymime( ilib, > > mime, > > &codec_buf, > > 10 ))) > > { > > _error("%s: img_codec_list() No Codecs found on target !", > __FUNCTION__); > > return -1; > > } > > > > //convert the image_fd to stream_fd required by image libs. > > /* Lavin : here file_fs should be your xxx.png file fd after > open(...O_CREATE) */ > > if(NULL == (image_stream_fd = io_open( IO_FD, IO_WRITE, file_fd > ))) > > { > > _error("%s: io_open() failed: %d", __FUNCTION__); > > return -1; > > } > > > > //set the codec > > > > //Prepare to encode a frame to a stream > > if (img_encode_begin(codec_buf, > image_stream_fd,&temp_encode_data) != IMG_ERR_OK) > > { > > _error("%s: img_encode_begin() failed", __FUNCTION__); > > return -1; > > } > > > > if ( (result = img_encode_frame(codec_buf, image_stream_fd, > NULL,&img,&temp_encode_data)) != IMG_ERR_OK) > > { > > _error("%s: img_encode_frame() failed: %d", __FUNCTION__, > result); > > return -1; > > } > > > > (void)img_encode_finish(codec_buf, > image_stream_fd,&temp_encode_data); > > > > io_close( image_stream_fd ); > > > > /* done with img lib */ > > img_lib_detach(ilib); > > > > /* Lavin : Now your PNG fromat file is ready :) :) */ > > > > > > Regards, > > Lavin, > > > > -----Original Message----- > > From: Ronald Burkey [mailto:community-noreply@qnx.com] > > Sent: Friday, August 12, 2011 9:52 PM > > To: advanced-graphics > > Subject: Creating a PNG output file. > > > > I have a rectangular array in memory of RGB values (i.e., it is > IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. > How would this be done? > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post88079 > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post88149 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88150 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88152 Wed, 17 Aug 2011 16:22:11 GMT http://community.qnx.com/sf/go/post88168 Ronald Burkey 2011-08-17T16:22:11Z http://community.qnx.com/sf/go/post88158 Thanks, Lavin. It seems to work fine, after appropriate changes for my environment. On 08/17/2011 07:53 AM, Lavin Pottekkat wrote: > Yes, you can change the mime type for different file formats. > > Regards, > Lavin > > -----Original Message----- > From: Ronald Burkey [mailto:community-noreply@qnx.com] > Sent: Wednesday, August 17, 2011 6:10 PM > To: advanced-graphics > Subject: Re: Creating a PNG output file. [bcc] > > I had just made that change about 10 seconds before your message > arrived. :-) I haven't gotten to the point yet where I can run the > code. I'll let you know what happens. > > I assume that if I want jpg or bmp, it's just a matter of changing the > mime type appropriately? > > Thanks! > Ron > > > Wed, 17 Aug 2011 14:24:37 GMT http://community.qnx.com/sf/go/post88158 Ronald Burkey 2011-08-17T14:24:37Z http://community.qnx.com/sf/go/post88152 Yes, you can change the mime type for different file formats. Regards, Lavin -----Original Message----- From: Ronald Burkey [mailto:community-noreply@qnx.com] Sent: Wednesday, August 17, 2011 6:10 PM To: advanced-graphics Subject: Re: Creating a PNG output file. [bcc] I had just made that change about 10 seconds before your message arrived. :-) I haven't gotten to the point yet where I can run the code. I'll let you know what happens. I assume that if I want jpg or bmp, it's just a matter of changing the mime type appropriately? Thanks! Ron On 08/17/2011 07:34 AM, Lavin Pottekkat wrote: > Just now I noticed that you have RGBA8888, in this case I think you should modify below lines highlighted below using '-->' > Also pl make sure you configure the img.w/h appropriately. > > Cheers, > Lavin > > -----Original Message----- > From: Pottekkat, Lavin > Sent: Wednesday, August 17, 2011 5:43 PM > To: advanced-graphics > Subject: RE: Creating a PNG output file. > > Hi Ronald, > > Try this it should work :) .... search for "Lavin" to see my comments inline.... > > uint32_t *img_buf = NULL; > uint32_t image_size = Max size of the RGB data buffer; > int32_t result = EOK; > > img_lib_t ilib; > img_codec_t codec_buf; > int n_codecs; > img_t img; > io_stream_t *image_stream_fd; > char mime[64]; > uintptr_t temp_encode_data = 0; > > /* allocate (image_size/sizeof int-(4bytes)) elements of type int */ > if (NULL == (img_buf = calloc((image_size / (sizeof(uint32_t))), sizeof(uint32_t)))) { > _error("%s: Memory allocation for %d bytes failed", __FUNCTION__, image_size); > return ENOMEM; > } > > /* Lavin : copy the image RGB values linearly to the above allocated img_buf, from your rectangular array in memory */ > > /* Lavin : at this point I assume that you have already copied the image data to img_buf.*/ > > /* Lavin : NOTE: you can very well use your rectangular array directly as image_buf as well :) */ > > > //Attaching to the image library > memset(&img,0,sizeof(img_t)); > > /* get the resolution details */ > img.w = 1440; // 1440 or 960 , use accordingly > img.h = 540; // 540, use accordingly > > img.format = IMG_FMT_RGBA8888; > > img.flags |= IMG_FORMAT | IMG_W | IMG_H | IMG_DIRECT; > > img.access.direct.data = img_buf; > --> img.access.direct.stride = (img.w * 4 ); > > if ((result = img_lib_attach(&ilib)) != IMG_ERR_OK) { > fprintf(stderr, "img_lib_attach() failed: %d\n", result); > return result; > } > > memset(mime, '\0', 64 ); > sprintf(mime, "image/%s", "png"); > > if(EOK == (n_codecs = img_codec_list_bymime( ilib, > mime, > &codec_buf, > 10 ))) > { > _error("%s: img_codec_list() No Codecs found on target !", __FUNCTION__); > return -1; > } > > //convert the image_fd to stream_fd required by image libs. > /* Lavin : here file_fs should be your xxx.png file fd after open(...O_CREATE) */ > if(NULL == (image_stream_fd = io_open( IO_FD, IO_WRITE, file_fd ))) > { > _error("%s: io_open() failed: %d", __FUNCTION__); > return -1; > } > > //set the codec > > //Prepare to encode a frame to a stream > if (img_encode_begin(codec_buf, image_stream_fd,&temp_encode_data) != IMG_ERR_OK) > { > _error("%s: img_encode_begin() failed", __FUNCTION__); > return -1; > } > > if ( (result = img_encode_frame(codec_buf, image_stream_fd, NULL,&img,&temp_encode_data)) != IMG_ERR_OK) > { > _error("%s: img_encode_frame() failed: %d", __FUNCTION__, result); > return -1; > } > > (void)img_encode_finish(codec_buf, image_stream_fd,&temp_encode_data); > > io_close( image_stream_fd ); > > /* done with img lib */ > img_lib_detach(ilib); > > /* Lavin : Now your PNG fromat file is ready :) :) */ > > > Regards, > Lavin, > > -----Original Message----- > From: Ronald Burkey [mailto:community-noreply@qnx.com] > Sent: Friday, August 12, 2011 9:52 PM > To: advanced-graphics > Subject: Creating a PNG output file. > > I have a rectangular array in memory of RGB values (i.e., it is IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. How would this be done? > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88079 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88149 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post88150 Wed, 17 Aug 2011 12:53:15 GMT http://community.qnx.com/sf/go/post88152 Lavin Pottekkat 2011-08-17T12:53:15Z http://community.qnx.com/sf/go/post88150 I had just made that change about 10 seconds before your message arrived. :-) I haven't gotten to the point yet where I can run the code. I'll let you know what happens. I assume that if I want jpg or bmp, it's just a matter of changing the mime type appropriately? Thanks! Ron On 08/17/2011 07:34 AM, Lavin Pottekkat wrote: > Just now I noticed that you have RGBA8888, in this case I think you should modify below lines highlighted below using '-->' > Also pl make sure you configure the img.w/h appropriately. > > Cheers, > Lavin > > -----Original Message----- > From: Pottekkat, Lavin > Sent: Wednesday, August 17, 2011 5:43 PM > To: advanced-graphics > Subject: RE: Creating a PNG output file. > > Hi Ronald, > > Try this it should work :) .... search for "Lavin" to see my comments inline.... > > uint32_t *img_buf = NULL; > uint32_t image_size = Max size of the RGB data buffer; > int32_t result = EOK; > > img_lib_t ilib; > img_codec_t codec_buf; > int n_codecs; > img_t img; > io_stream_t *image_stream_fd; > char mime[64]; > uintptr_t temp_encode_data = 0; > > /* allocate (image_size/sizeof int-(4bytes)) elements of type int */ > if (NULL == (img_buf = calloc((image_size / (sizeof(uint32_t))), sizeof(uint32_t)))) { > _error("%s: Memory allocation for %d bytes failed", __FUNCTION__, image_size); > return ENOMEM; > } > > /* Lavin : copy the image RGB values linearly to the above allocated img_buf, from your rectangular array in memory */ > > /* Lavin : at this point I assume that you have already copied the image data to img_buf.*/ > > /* Lavin : NOTE: you can very well use your rectangular array directly as image_buf as well :) */ > > > //Attaching to the image library > memset(&img,0,sizeof(img_t)); > > /* get the resolution details */ > img.w = 1440; // 1440 or 960 , use accordingly > img.h = 540; // 540, use accordingly > > img.format = IMG_FMT_RGBA8888; > > img.flags |= IMG_FORMAT | IMG_W | IMG_H | IMG_DIRECT; > > img.access.direct.data = img_buf; > --> img.access.direct.stride = (img.w * 4 ); > > if ((result = img_lib_attach(&ilib)) != IMG_ERR_OK) { > fprintf(stderr, "img_lib_attach() failed: %d\n", result); > return result; > } > > memset(mime, '\0', 64 ); > sprintf(mime, "image/%s", "png"); > > if(EOK == (n_codecs = img_codec_list_bymime( ilib, > mime, > &codec_buf, > 10 ))) > { > _error("%s: img_codec_list() No Codecs found on target !", __FUNCTION__); > return -1; > } > > //convert the image_fd to stream_fd required by image libs. > /* Lavin : here file_fs should be your xxx.png file fd after open(...O_CREATE) */ > if(NULL == (image_stream_fd = io_open( IO_FD, IO_WRITE, file_fd ))) > { > _error("%s: io_open() failed: %d", __FUNCTION__); > return -1; > } > > //set the codec > > //Prepare to encode a frame to a stream > if (img_encode_begin(codec_buf, image_stream_fd,&temp_encode_data) != IMG_ERR_OK) > { > _error("%s: img_encode_begin() failed", __FUNCTION__); > return -1; > } > > if ( (result = img_encode_frame(codec_buf, image_stream_fd, NULL,&img,&temp_encode_data)) != IMG_ERR_OK) > { > _error("%s: img_encode_frame() failed: %d", __FUNCTION__, result); > return -1; > } > > (void)img_encode_finish(codec_buf, image_stream_fd,&temp_encode_data); > > io_close( image_stream_fd ); > > /* done with img lib */ > img_lib_detach(ilib); > > /* Lavin : Now your PNG fromat file is ready :) :) */ > > > Regards, > Lavin, > > -----Original Message----- > From: Ronald Burkey [mailto:community-noreply@qnx.com] > Sent: Friday, August 12, 2011 9:52 PM > To: advanced-graphics > Subject: Creating a PNG output file. > > I have a rectangular array in memory of RGB values (i.e., it is IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. How would this be done? > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88079 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post88149 Wed, 17 Aug 2011 12:40:07 GMT http://community.qnx.com/sf/go/post88150 Ronald Burkey 2011-08-17T12:40:07Z http://community.qnx.com/sf/go/post88149 Just now I noticed that you have RGBA8888, in this case I think you should modify below lines highlighted below using '-->' Also pl make sure you configure the img.w/h appropriately. Cheers, Lavin -----Original Message----- From: Pottekkat, Lavin Sent: Wednesday, August 17, 2011 5:43 PM To: advanced-graphics Subject: RE: Creating a PNG output file. Hi Ronald, Try this it should work :) .... search for "Lavin" to see my comments inline.... uint32_t *img_buf = NULL; uint32_t image_size = Max size of the RGB data buffer; int32_t result = EOK; img_lib_t ilib; img_codec_t codec_buf; int n_codecs; img_t img; io_stream_t *image_stream_fd; char mime[64]; uintptr_t temp_encode_data = 0; /* allocate (image_size/sizeof int-(4bytes)) elements of type int */ if (NULL == (img_buf = calloc((image_size / (sizeof(uint32_t))), sizeof(uint32_t)))) { _error("%s: Memory allocation for %d bytes failed", __FUNCTION__, image_size); return ENOMEM; } /* Lavin : copy the image RGB values linearly to the above allocated img_buf, from your rectangular array in memory */ /* Lavin : at this point I assume that you have already copied the image data to img_buf.*/ /* Lavin : NOTE: you can very well use your rectangular array directly as image_buf as well :) */ //Attaching to the image library memset(&img,0,sizeof(img_t)); /* get the resolution details */ img.w = 1440; // 1440 or 960 , use accordingly img.h = 540; // 540, use accordingly img.format = IMG_FMT_RGBA8888; img.flags |= IMG_FORMAT | IMG_W | IMG_H | IMG_DIRECT; img.access.direct.data = img_buf; --> img.access.direct.stride = (img.w * 4 ); if ((result = img_lib_attach(&ilib)) != IMG_ERR_OK) { fprintf(stderr, "img_lib_attach() failed: %d\n", result); return result; } memset(mime, '\0', 64 ); sprintf(mime, "image/%s", "png"); if(EOK == (n_codecs = img_codec_list_bymime( ilib, mime, &codec_buf, 10 ))) { _error("%s: img_codec_list() No Codecs found on target !", __FUNCTION__); return -1; } //convert the image_fd to stream_fd required by image libs. /* Lavin : here file_fs should be your xxx.png file fd after open(...O_CREATE) */ if(NULL == (image_stream_fd = io_open( IO_FD, IO_WRITE, file_fd ))) { _error("%s: io_open() failed: %d", __FUNCTION__); return -1; } //set the codec //Prepare to encode a frame to a stream if (img_encode_begin(codec_buf, image_stream_fd, &temp_encode_data) != IMG_ERR_OK) { _error("%s: img_encode_begin() failed", __FUNCTION__); return -1; } if ( (result = img_encode_frame(codec_buf, image_stream_fd, NULL, &img, &temp_encode_data)) != IMG_ERR_OK) { _error("%s: img_encode_frame() failed: %d", __FUNCTION__, result); return -1; } (void)img_encode_finish(codec_buf, image_stream_fd, &temp_encode_data); io_close( image_stream_fd ); /* done with img lib */ img_lib_detach(ilib); /* Lavin : Now your PNG fromat file is ready :) :) */ Regards, Lavin, -----Original Message----- From: Ronald Burkey [mailto:community-noreply@qnx.com] Sent: Friday, August 12, 2011 9:52 PM To: advanced-graphics Subject: Creating a PNG output file. I have a rectangular array in memory of RGB values (i.e., it is IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. How would this be done? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post88079 Wed, 17 Aug 2011 12:34:51 GMT http://community.qnx.com/sf/go/post88149 Lavin Pottekkat 2011-08-17T12:34:51Z http://community.qnx.com/sf/go/post88148 Hi Ronald, Try this it should work :) .... search for "Lavin" to see my comments inline.... uint32_t *img_buf = NULL; uint32_t image_size = Max size of the RGB data buffer; int32_t result = EOK; img_lib_t ilib; img_codec_t codec_buf; int n_codecs; img_t img; io_stream_t *image_stream_fd; char mime[64]; uintptr_t temp_encode_data = 0; /* allocate (image_size/sizeof int-(4bytes)) elements of type int */ if (NULL == (img_buf = calloc((image_size / (sizeof(uint32_t))), sizeof(uint32_t)))) { _error("%s: Memory allocation for %d bytes failed", __FUNCTION__, image_size); return ENOMEM; } /* Lavin : copy the image RGB values linearly to the above allocated img_buf, from your rectangular array in memory */ /* Lavin : at this point I assume that you have already copied the image data to img_buf.*/ /* Lavin : NOTE: you can very well use your rectangular array directly as image_buf as well :) */ //Attaching to the image library memset(&img,0,sizeof(img_t)); /* get the resolution details */ img.w = 1440; // 1440 or 960 , use accordingly img.h = 540; // 540, use accordingly img.format = IMG_FMT_RGBA8888; img.flags |= IMG_FORMAT | IMG_W | IMG_H | IMG_DIRECT; img.access.direct.data = img_buf; img.access.direct.stride = (img.w * 3 ); if ((result = img_lib_attach(&ilib)) != IMG_ERR_OK) { fprintf(stderr, "img_lib_attach() failed: %d\n", result); return result; } memset(mime, '\0', 64 ); sprintf(mime, "image/%s", "png"); if(EOK == (n_codecs = img_codec_list_bymime( ilib, mime, &codec_buf, 10 ))) { _error("%s: img_codec_list() No Codecs found on target !", __FUNCTION__); return -1; } //convert the image_fd to stream_fd required by image libs. /* Lavin : here file_fs should be your xxx.png file fd after open(...O_CREATE) */ if(NULL == (image_stream_fd = io_open( IO_FD, IO_WRITE, file_fd ))) { _error("%s: io_open() failed: %d", __FUNCTION__); return -1; } //set the codec //Prepare to encode a frame to a stream if (img_encode_begin(codec_buf, image_stream_fd, &temp_encode_data) != IMG_ERR_OK) { _error("%s: img_encode_begin() failed", __FUNCTION__); return -1; } if ( (result = img_encode_frame(codec_buf, image_stream_fd, NULL, &img, &temp_encode_data)) != IMG_ERR_OK) { _error("%s: img_encode_frame() failed: %d", __FUNCTION__, result); return -1; } (void)img_encode_finish(codec_buf, image_stream_fd, &temp_encode_data); io_close( image_stream_fd ); /* done with img lib */ img_lib_detach(ilib); /* Lavin : Now your PNG fromat file is ready :) :) */ Regards, Lavin, -----Original Message----- From: Ronald Burkey [mailto:community-noreply@qnx.com] Sent: Friday, August 12, 2011 9:52 PM To: advanced-graphics Subject: Creating a PNG output file. I have a rectangular array in memory of RGB values (i.e., it is IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. How would this be done? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post88079 Wed, 17 Aug 2011 12:14:51 GMT http://community.qnx.com/sf/go/post88148 Lavin Pottekkat 2011-08-17T12:14:51Z http://community.qnx.com/sf/go/post88107 Photon (and io-graphics) is running and there's only 1 layer on the system so your app fails to attach to the layer. -----Original Message----- From: Hieronim Fet [mailto:community-noreply@qnx.com] Sent: August-09-11 6:49 PM To: advanced-graphics Subject: gf_layer_attach() fails. Hello everyone, I`m having a problem with example program that draws rectangle. The code is from topic http://community.qnx.com/sf/discussion/do/listPosts/projects.graphics/di scussion.advanced_graphics.topc8189?_pagenum=1, but I enclose copy of source without long comments so it is easier to look through. As mentioned in topic of this message there is problem with gf_layer_attach() function that fails. The output of the running program is: Number of displays: 1 Display 0: 1280X1024, refresh = 60Hz Number of layers: 1 gf_layer_attach() failed I`m sending sloginfo and pidin outputs and my display.conf. I have no idea why gf_layer_attach fails, hope you will help me. Generally I`m working in Momentics IDE, so if I run this program as QNX C/C++ App will I see any "drawn rectangles" or should I run the program directly under QNX? Maybe this question is silly but I`m just a beginner. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post87952 Mon, 15 Aug 2011 20:56:48 GMT http://community.qnx.com/sf/go/post88107 Michael Van Reenen 2011-08-15T20:56:48Z http://community.qnx.com/sf/go/post88079 I have a rectangular array in memory of RGB values (i.e., it is IMG_FMT_RGBA8888 data) and would like to output a PNG file from that data. How would this be done? Fri, 12 Aug 2011 16:22:11 GMT http://community.qnx.com/sf/go/post88079 Ronald Burkey 2011-08-12T16:22:11Z http://community.qnx.com/sf/go/post87957 Hi, I don't immediately see a reason for failure, either. You should examine the return value of gf_layer_attach() more closely to see what the error was. Perhaps another instance of your application was already running? In that case, you'd get an GF_ERR_INUSE. You will not see any rectangles drawn on your Windows/Linux development host; QNX executables simple will not run there. They can only execute on systems running the QNX Neutrino OS. To run your program from the Momentics IDE, you'll want to use a "C/C++ QNX QConn (IP)" launch configuration; this will automatically transfer your program to the defined target and run it there. As well, you could transfer the binary to your target and run it there directly. Hope this helps, Thomas -----Original Message----- From: Hieronim Fet [mailto:community-noreply@qnx.com] Sent: Mittwoch, 10. August 2011 00:49 To: advanced-graphics Subject: gf_layer_attach() fails. Hello everyone, I`m having a problem with example program that draws rectangle. The code is from topic http://community.qnx.com/sf/discussion/do/listPosts/projects.graphics/di scussion.advanced_graphics.topc8189?_pagenum=1, but I enclose copy of source without long comments so it is easier to look through. As mentioned in topic of this message there is problem with gf_layer_attach() function that fails. The output of the running program is: Number of displays: 1 Display 0: 1280X1024, refresh = 60Hz Number of layers: 1 gf_layer_attach() failed I`m sending sloginfo and pidin outputs and my display.conf. I have no idea why gf_layer_attach fails, hope you will help me. Generally I`m working in Momentics IDE, so if I run this program as QNX C/C++ App will I see any "drawn rectangles" or should I run the program directly under QNX? Maybe this question is silly but I`m just a beginner. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post87952 Wed, 10 Aug 2011 07:05:29 GMT http://community.qnx.com/sf/go/post87957 Thomas Haupt 2011-08-10T07:05:29Z http://community.qnx.com/sf/go/post87954 Sorry for posting twice, my mistake. Tue, 09 Aug 2011 22:54:28 GMT http://community.qnx.com/sf/go/post87954 Hieronim Fet 2011-08-09T22:54:28Z http://community.qnx.com/sf/go/post87953 Hello everyone, I`m having a problem with example program that draws rectangle. The code is from topic http://community.qnx.com/sf/discussion/do/listPosts/projects.graphics/discussion.advanced_graphics.topc8189?_pagenum=1, but I enclose copy of source without long comments so it is easier to look through. As mentioned in topic of this message there is problem with gf_layer_attach() function that fails. The output of the running program is: Number of displays: 1 Display 0: 1280X1024, refresh = 60Hz Number of layers: 1 gf_layer_attach() failed I`m sending sloginfo and pidin outputs and my display.conf. I have no idea why gf_layer_attach fails, hope you will help me. Generally I`m working in Momentics IDE, so if I run this program as QNX C/C++ App will I see any "drawn rectangles" or should I run the program directly under QNX? Maybe this question is silly but I`m just a beginner. Tue, 09 Aug 2011 22:53:00 GMT http://community.qnx.com/sf/go/post87953 Hieronim Fet 2011-08-09T22:53:00Z http://community.qnx.com/sf/go/post87952 Hello everyone, I`m having a problem with example program that draws rectangle. The code is from topic http://community.qnx.com/sf/discussion/do/listPosts/projects.graphics/discussion.advanced_graphics.topc8189?_pagenum=1, but I enclose copy of source without long comments so it is easier to look through. As mentioned in topic of this message there is problem with gf_layer_attach() function that fails. The output of the running program is: Number of displays: 1 Display 0: 1280X1024, refresh = 60Hz Number of layers: 1 gf_layer_attach() failed I`m sending sloginfo and pidin outputs and my display.conf. I have no idea why gf_layer_attach fails, hope you will help me. Generally I`m working in Momentics IDE, so if I run this program as QNX C/C++ App will I see any "drawn rectangles" or should I run the program directly under QNX? Maybe this question is silly but I`m just a beginner. Tue, 09 Aug 2011 22:49:26 GMT http://community.qnx.com/sf/go/post87952 Hieronim Fet 2011-08-09T22:49:26Z http://community.qnx.com/sf/go/post87581 Am using LCD, i had a reference driver for LCD. I was able to integrate and it is working fine. Now am able to run few example applications. Thank you. Has anyone done a Photon GUI environment on the iMx51 or iMx53 platform. Kishore.S > > What kind of display (DVI, VGA, LCD) are you using? > > Thanks > > > -----Original Message----- > From: kishore s [mailto:community-noreply@qnx.com] > Sent: July 22, 2011 2:43 AM > To: advanced-graphics > Subject: Display problem for iMx51 - vsync and eglgears not working > > Hi, > > I am working on iMx51 reference board from Freescale. > > When i run the vsync or egl-gears application nothing is comming up on > the > display. > > When i run the egl application i get the below prints. > egl-gears > 185 frames in 5.027 seconds = 36.801 FPS > 184 frames in 5.027 seconds = 36.602 FPS > 218 frames in 5.946 seconds = 36.663 FPS > > I am not getting any errors also when i run sloginfo. > > Jan 01 00:00:00 2 5 0 libcam.so (Jul 9 2010 13:52:59) bver > 6040207 > Jan 01 00:00:00 5 6 0 Watchdog Timer is disable now. > Jan 01 00:00:00 2 5 100 cam-disk.so (Jul 9 2010 13:53:13) > Jan 01 00:00:14 6 8 0 get_config_data(): xres=800 yres=480 > refresh=60 output_fmt=24 di_sel=1 display_type=1 yuv_layer=1 > Jan 01 00:00:14 6 8 0 imx51_layer_update_end(): type=1, > gpio3=0x0600102a DVI_RST LVDS_RST LCD_DET > Jan 01 00:00:14 6 8 0 imx51_layer_update_end(): set > gpio3=0x0600103a DVI_RST LVDS_RST LCD_DET LCD_BKLIGHT > > For the display.conf you can refer the attached buildfile. > for modopts in display.conf am using the imx51-1.conf. > xres=800,yres=480,refresh=60,pixclk=32264000,hsw=124,hss=60,hew=32,vsw=2 > ,vss=33,vew=10,vpol=1,epol=1,dpol=0,cpol=0,hpol=1,ofmt=16,di=1,type=1,yu > v=1 > > In the release notes they have mentioned about display-detect but i dint > find any binary for the same, so i have directly given the imx51-1.conf > file. > > > Can anyone help me on this issue. > > > Kishore.S > > > > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post87517 > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post87560 > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Tue, 26 Jul 2011 04:42:08 GMT http://community.qnx.com/sf/go/post87581 kishore s 2011-07-26T04:42:08Z http://community.qnx.com/sf/go/post87560 What kind of display (DVI, VGA, LCD) are you using? Thanks -----Original Message----- From: kishore s [mailto:community-noreply@qnx.com] Sent: July 22, 2011 2:43 AM To: advanced-graphics Subject: Display problem for iMx51 - vsync and eglgears not working Hi, I am working on iMx51 reference board from Freescale. When i run the vsync or egl-gears application nothing is comming up on the display. When i run the egl application i get the below prints. egl-gears 185 frames in 5.027 seconds = 36.801 FPS 184 frames in 5.027 seconds = 36.602 FPS 218 frames in 5.946 seconds = 36.663 FPS I am not getting any errors also when i run sloginfo. Jan 01 00:00:00 2 5 0 libcam.so (Jul 9 2010 13:52:59) bver 6040207 Jan 01 00:00:00 5 6 0 Watchdog Timer is disable now. Jan 01 00:00:00 2 5 100 cam-disk.so (Jul 9 2010 13:53:13) Jan 01 00:00:14 6 8 0 get_config_data(): xres=800 yres=480 refresh=60 output_fmt=24 di_sel=1 display_type=1 yuv_layer=1 Jan 01 00:00:14 6 8 0 imx51_layer_update_end(): type=1, gpio3=0x0600102a DVI_RST LVDS_RST LCD_DET Jan 01 00:00:14 6 8 0 imx51_layer_update_end(): set gpio3=0x0600103a DVI_RST LVDS_RST LCD_DET LCD_BKLIGHT For the display.conf you can refer the attached buildfile. for modopts in display.conf am using the imx51-1.conf. xres=800,yres=480,refresh=60,pixclk=32264000,hsw=124,hss=60,hew=32,vsw=2 ,vss=33,vew=10,vpol=1,epol=1,dpol=0,cpol=0,hpol=1,ofmt=16,di=1,type=1,yu v=1 In the release notes they have mentioned about display-detect but i dint find any binary for the same, so i have directly given the imx51-1.conf file. Can anyone help me on this issue. Kishore.S -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post87517 Mon, 25 Jul 2011 12:51:51 GMT http://community.qnx.com/sf/go/post87560 Michael Van Reenen 2011-07-25T12:51:51Z http://community.qnx.com/sf/go/post87517 Hi, I am working on iMx51 reference board from Freescale. When i run the vsync or egl-gears application nothing is comming up on the display. When i run the egl application i get the below prints. egl-gears 185 frames in 5.027 seconds = 36.801 FPS 184 frames in 5.027 seconds = 36.602 FPS 218 frames in 5.946 seconds = 36.663 FPS I am not getting any errors also when i run sloginfo. Jan 01 00:00:00 2 5 0 libcam.so (Jul 9 2010 13:52:59) bver 6040207 Jan 01 00:00:00 5 6 0 Watchdog Timer is disable now. Jan 01 00:00:00 2 5 100 cam-disk.so (Jul 9 2010 13:53:13) Jan 01 00:00:14 6 8 0 get_config_data(): xres=800 yres=480 refresh=60 output_fmt=24 di_sel=1 display_type=1 yuv_layer=1 Jan 01 00:00:14 6 8 0 imx51_layer_update_end(): type=1, gpio3=0x0600102a DVI_RST LVDS_RST LCD_DET Jan 01 00:00:14 6 8 0 imx51_layer_update_end(): set gpio3=0x0600103a DVI_RST LVDS_RST LCD_DET LCD_BKLIGHT For the display.conf you can refer the attached buildfile. for modopts in display.conf am using the imx51-1.conf. xres=800,yres=480,refresh=60,pixclk=32264000,hsw=124,hss=60,hew=32,vsw=2,vss=33,vew=10,vpol=1,epol=1,dpol=0,cpol=0,hpol=1,ofmt=16,di=1,type=1,yuv=1 In the release notes they have mentioned about display-detect but i dint find any binary for the same, so i have directly given the imx51-1.conf file. Can anyone help me on this issue. Kishore.S -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Fri, 22 Jul 2011 06:42:37 GMT http://community.qnx.com/sf/go/post87517 kishore s 2011-07-22T06:42:37Z http://community.qnx.com/sf/go/post86633 Check your video memory setting in BIOS! Had the same problem with the poulsbo driver on a iEi UIBX-200 machine. Changing the video memory from 4MB to 8MB it works fine with 1280x1024 16M colors. Wed, 15 Jun 2011 11:59:15 GMT http://community.qnx.com/sf/go/post86633 Oscar Andreassen 2011-06-15T11:59:15Z http://community.qnx.com/sf/go/post86430 I am loading a 640X480 rgb png as follow: img_t image1; rc = img_load_file(ilib, "/tmp/black.png", NULL, &image1); I am trying to walk through every pixel in this image and do per pixel calculation. However, the loop below causes my system to crash! for (i = 0; i <( image1.h * image1.w); i++) // walk through the image using a pointer After debugging this, it seems if I use image size to be 640*361 everything works fine. So, why is it that imag1.access.direct.data is pointing to a memory size that is (640*361) where the image size is 640X480? My image is a ARGB, so it I should have 4 bytes/pixel. According to the documentation in img_t, the img_w and ima_h fields are the number of pixels. Can someone help me understand the discrepancy that I am seeing? Thanks, R.S. Fri, 03 Jun 2011 17:33:23 GMT http://community.qnx.com/sf/go/post86430 Reza Salehi 2011-06-03T17:33:23Z http://community.qnx.com/sf/go/post86372 Hi, I have a question in regards to the following img_t flags: IMG_TRANSPARENCY; IMG_FMT_ALPHA; I have a file that is ARGB8888. When I load this file as below rc = img_load_file(ilib, "/tmp/Day_24hr.png", NULL, &image1); the IMG_TRANSPARENCY, IMG_FMT_ALPHA are not set! Aren't these flags suppose to be set by the img_load_file, if the file is ARGB8888 png file? I am trying to blit (blend) two ARGB files, but for some reason, I keep overwriting the destination instead of the blending. I also tried the following without luck alpha.mode = GF_ALPHA_M1_SRC_PIXEL_ALPHA; gf_context_set_dst_alpha(context, &alpha); I would appreciate if someone can show me me some code on how to blend to two ARGB png files together. I am trying to evaluate the QNX for our next company project but the documentation is not always very easy to follow (at least for a non graphic expert like me) Thanks, R.S. Thu, 02 Jun 2011 03:40:24 GMT http://community.qnx.com/sf/go/post86372 Reza Salehi 2011-06-02T03:40:24Z http://community.qnx.com/sf/go/post86359 For some reason, when I do: image2.flags |= IMG_FORMAT; image2.format = GF_FORMAT_ARGB8888; rc = img_load_file(ilib, "/tmp/Day_24hr.png", NULL, &image1); rc = gf_surface_attach(&img_surf1, gdev, image1.w, image1.h, image1.access.direct.stride, img_fmt_to_gf(image1.format), &palette, image1.access.direct.data, 0); gf_context_create(&context); Then my call to rc = gf_context_set_surface(context, img_surf1); hangs and never returns!!! I am running out of ideas to try!!! Thanks, Reza. Wed, 01 Jun 2011 21:36:34 GMT http://community.qnx.com/sf/go/post86359 Reza Salehi 2011-06-01T21:36:34Z http://community.qnx.com/sf/go/post86358 Correct, you'll need an alpha channel for source alpha blending. ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Wednesday, June 01, 2011 05:17 PM To: advanced-graphics <post86357@community.qnx.com> Subject: Re: How to blit insttead of overwite using gf_draw_blit2? Thanks for the quick reply Joel. However, I guess my problem is that I can not figure out how to enable blending! I have looked at the document and I found the gf_context_set_alpha. However, my images are RGB888 and not ARGB888. Should I read the original image as ARGB8888 (by setting the img_t format field). I would appreciate it if you can point me to small code snipet or site, as I have been trying to figure this out for past two days. Regards, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post86357 Wed, 01 Jun 2011 21:27:37 GMT http://community.qnx.com/sf/go/post86358 Joel Pilon 2011-06-01T21:27:37Z http://community.qnx.com/sf/go/post86357 Thanks for the quick reply Joel. However, I guess my problem is that I can not figure out how to enable blending! I have looked at the document and I found the gf_context_set_alpha. However, my images are RGB888 and not ARGB888. Should I read the original image as ARGB8888 (by setting the img_t format field). I would appreciate it if you can point me to small code snipet or site, as I have been trying to figure this out for past two days. Regards, Reza. Wed, 01 Jun 2011 21:17:32 GMT http://community.qnx.com/sf/go/post86357 Reza Salehi 2011-06-01T21:17:32Z http://community.qnx.com/sf/go/post86356 You'll probably want to enable blending and use a source over blending mode. -Joel ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Wednesday, June 01, 2011 04:51 PM To: advanced-graphics <post86355@community.qnx.com> Subject: How to blit insttead of overwite using gf_draw_blit2? Hi All, I am trying to blit two .png files. I have attached the .png files to two seperate surfaces and am using the following code(only the important calls): rc = gf_surface_attach(&img_surf1, gdev, image1.w, image1.h, image1.access.direct.stride, img_fmt_to_gf(image1.format), &palette, image1.access.direct.data, 0); rc = gf_surface_attach(&img_surf2, gdev, image2.w, image2.h, image2.access.direct.stride, img_fmt_to_gf(image2.format), &palette2, image2.access.direct.data, 0); gf_context_create(&context); gf_context_set_surface(context, img_surf1); gf_draw_begin(context); gf_draw_blit2( context, img_surf2, NULL, 107, 4, 334, 222, 0, 0); gf_draw_end(context); rc = img_write_file(ilib, "/tmp/reza.png", NULL, &image1); The two images are getting combined. However, the target image is overwriting (covering) the target image. Can someone please tell me what I need to do (probably to the context) to have the source image blited into the target image, instead of overwriting it? Thanks in advance, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post86355 Wed, 01 Jun 2011 20:56:56 GMT http://community.qnx.com/sf/go/post86356 Joel Pilon 2011-06-01T20:56:56Z http://community.qnx.com/sf/go/post86355 Hi All, I am trying to blit two .png files. I have attached the .png files to two seperate surfaces and am using the following code(only the important calls): rc = gf_surface_attach(&img_surf1, gdev, image1.w, image1.h, image1.access.direct.stride, img_fmt_to_gf(image1.format), &palette, image1.access.direct.data, 0); rc = gf_surface_attach(&img_surf2, gdev, image2.w, image2.h, image2.access.direct.stride, img_fmt_to_gf(image2.format), &palette2, image2.access.direct.data, 0); gf_context_create(&context); gf_context_set_surface(context, img_surf1); gf_draw_begin(context); gf_draw_blit2( context, img_surf2, NULL, 107, 4, 334, 222, 0, 0); gf_draw_end(context); rc = img_write_file(ilib, "/tmp/reza.png", NULL, &image1); The two images are getting combined. However, the target image is overwriting (covering) the target image. Can someone please tell me what I need to do (probably to the context) to have the source image blited into the target image, instead of overwriting it? Thanks in advance, Reza. Wed, 01 Jun 2011 20:51:18 GMT http://community.qnx.com/sf/go/post86355 Reza Salehi 2011-06-01T20:51:18Z http://community.qnx.com/sf/go/post86287 1. What graphics driver are you using? 2. What version of the OS? 3. What is the output of 'pci -v' (relevant part only -- search for VGA) 4. What is the output of show_vesa ? (just the header -- not need for modes' descriptions). Tue, 31 May 2011 12:51:49 GMT http://community.qnx.com/sf/go/post86287 Misha Nefedov 2011-05-31T12:51:49Z http://community.qnx.com/sf/go/post86285 This is the link which contains datasheet of ARK-6622H-18ZE: - http://www.alldatasheet.net/datasheet-pdf/pdf/327854/ADVANTECH/ARK-6622H-18ZE.html and this is the link for the board: - http://buy.advantech.com/AIMB270G200A1E/AIMB270G200A1E/model-AIMB-270G2-00A1E.htm 2011/5/31 Misha Nefedov <community-noreply@qnx.com> > The code is for a chassis. Please post a link to the board/graphics adapter > details. > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post86276 > > Tue, 31 May 2011 10:59:57 GMT http://community.qnx.com/sf/go/post86285 Thang Bui Quy 2011-05-31T10:59:57Z http://community.qnx.com/sf/go/post86276 The code is for a chassis. Please post a link to the board/graphics adapter details. Mon, 30 May 2011 18:38:46 GMT http://community.qnx.com/sf/go/post86276 Misha Nefedov 2011-05-30T18:38:46Z http://community.qnx.com/sf/go/post86275 I bought a computer from Advantech, its name is ARK-6622H-18ZE. You can see details about graphic adapter on website of Advantech. Thank you. 2011/5/31 Thắng Bùi Quý <bqthangcndt@gmail.com> > Dear you! > I am using the graphics adapter Intel GFX. I used window OS to build > programs with the context memory and they always run normal, there were not > any problem. Do you have solutions for my problem? Can you help me. Please! > > > 2011/5/31 Misha Nefedov <community-noreply@qnx.com> > >> This is most likely expected -- when you get a pointer to a video >> (dedicated) memory. The memory access is facilitated by the graphics >> controller and is usually slow for reading (comparing to a RAM memory >> controller) and fast for writing. >> What graphics adapter are you using? >> >> >> >> _______________________________________________ >> >> Advanced Graphics >> http://community.qnx.com/sf/go/post86272 >> >> > Mon, 30 May 2011 17:38:35 GMT http://community.qnx.com/sf/go/post86275 Thang Bui Quy 2011-05-30T17:38:35Z http://community.qnx.com/sf/go/post86274 Dear you! I am using the graphics adapter Intel GFX. I used window OS to build programs with the context memory and they always run normal, there were not any problem. Do you have solutions for my problem? Can you help me. Please! 2011/5/31 Misha Nefedov <community-noreply@qnx.com> > This is most likely expected -- when you get a pointer to a video > (dedicated) memory. The memory access is facilitated by the graphics > controller and is usually slow for reading (comparing to a RAM memory > controller) and fast for writing. > What graphics adapter are you using? > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post86272 > > Mon, 30 May 2011 17:32:36 GMT http://community.qnx.com/sf/go/post86274 Thang Bui Quy 2011-05-30T17:32:36Z http://community.qnx.com/sf/go/post86272 This is most likely expected -- when you get a pointer to a video (dedicated) memory. The memory access is facilitated by the graphics controller and is usually slow for reading (comparing to a RAM memory controller) and fast for writing. What graphics adapter are you using? Mon, 30 May 2011 17:10:33 GMT http://community.qnx.com/sf/go/post86272 Misha Nefedov 2011-05-30T17:10:33Z http://community.qnx.com/sf/go/post86234 I write a program using draw context memory by the function PdCreateOffscreenContext(). This function returns a pointer to a PdOffscreenContext_t. After that i use the function PdGetOffscreenContextPtr() to get a pointer to the shared memory object. When i have that pointer i can change data in the context to blit them on the screen by the function PgContextBlit(). However i had a problem with writing data back into the context, it was very slow. For example: ptr is the pointer to context, d is a variable. for(int i=0; i < CONTEXT_HEIGHT; ++i) for(int j=0; j < CONTEXT_WITH; ++j) { d = *(ptr + i * CONTEXT_WIDTH * 4 + j);(1) *(ptr + i * CONTEXT_WIDTH * 4 + j) = 2 * d; (2) } if i set CONTEXT_HEIGHT and CONTEXT_WIDTH small (about smaller than 256) the program run normal. if i set CONTEXT_HEIGHT and CONTEXT_WIDTH biggerl (about 1024) the program run very slow. I tried to test with bypassing either the line (1) or the line (2) and i realized that the line (2) made the program very slow. Can you help me to solve it? Sat, 28 May 2011 17:55:44 GMT http://community.qnx.com/sf/go/post86234 Thang Bui Quy 2011-05-28T17:55:44Z http://community.qnx.com/sf/go/post86181 I'd have to take a closer look. Perhaps someone else knows off hand. ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Thursday, May 26, 2011 05:59 PM To: advanced-graphics <post86180@community.qnx.com> Subject: Re: Who is responsible for alloc mem for access.direct.data? Hi Joel, Thanks for answering. I though the same. However, I wrote a small code and it seems like data is NULL before and after img_load_file() call! The function returns OK so the image does get loaded (somewhere), but the point is still data pointer is still NULL. So, when I try to use this pointer to attach it to a gf surface, the system hangs. img.flags = 0; img.flags |= IMG_DIRECT; printf("data before load %p \n",img.access.direct.data); if ((rc = img_load_file(ilib, "/tmp/n_day_r.png", NULL, &img)) != IMG_ERR_OK) { fprintf(stderr, "img_load_file(%s) failed: %d\n", "/tmp/n_day_r.png", rc); return -1; } else { fprintf(stderr, "img_load_file(%s) sucess : %d\n", "/tmp/n_day_r.png", rc); fprintf(stdout, "img is %dx%dx%d\n", img.w, img.h, IMG_FMT_BPP(img.format)); } printf("data after load %d \n",img.access.direct.data); _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post86180 Thu, 26 May 2011 22:02:30 GMT http://community.qnx.com/sf/go/post86181 Joel Pilon 2011-05-26T22:02:30Z http://community.qnx.com/sf/go/post86180 Hi Joel, Thanks for answering. I though the same. However, I wrote a small code and it seems like data is NULL before and after img_load_file() call! The function returns OK so the image does get loaded (somewhere), but the point is still data pointer is still NULL. So, when I try to use this pointer to attach it to a gf surface, the system hangs. img.flags = 0; img.flags |= IMG_DIRECT; printf("data before load %p \n",img.access.direct.data); if ((rc = img_load_file(ilib, "/tmp/n_day_r.png", NULL, &img)) != IMG_ERR_OK) { fprintf(stderr, "img_load_file(%s) failed: %d\n", "/tmp/n_day_r.png", rc); return -1; } else { fprintf(stderr, "img_load_file(%s) sucess : %d\n", "/tmp/n_day_r.png", rc); fprintf(stdout, "img is %dx%dx%d\n", img.w, img.h, IMG_FMT_BPP(img.format)); } printf("data after load %d \n",img.access.direct.data); Thu, 26 May 2011 21:59:31 GMT http://community.qnx.com/sf/go/post86180 Reza Salehi 2011-05-26T21:59:31Z http://community.qnx.com/sf/go/post86178 It been a long time, but i'm pretty sure the lib will allocate the memory, however I think you're responsible for freeing it. ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Thursday, May 26, 2011 05:21 PM To: advanced-graphics <post86177@community.qnx.com> Subject: Who is responsible for alloc mem for access.direct.data? Hi All, I am having a problem with setting img.flags |= IMG_DIRECT. Who is responsible for alloc memory for acess.direct.data? Is it the user or does the img_load_file() allocates memeory when the user sets the IMG_DIRECT flag. I have been spinning why wheels on this. I am trying to grab the acess.direct.data pointer after loading a png file, but my system hangs everytime I set the IMG_DIRECT flag. Thanks, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post86177 Thu, 26 May 2011 21:23:40 GMT http://community.qnx.com/sf/go/post86178 Joel Pilon 2011-05-26T21:23:40Z http://community.qnx.com/sf/go/post86177 Hi All, I am having a problem with setting img.flags |= IMG_DIRECT. Who is responsible for alloc memory for acess.direct.data? Is it the user or does the img_load_file() allocates memeory when the user sets the IMG_DIRECT flag. I have been spinning why wheels on this. I am trying to grab the acess.direct.data pointer after loading a png file, but my system hangs everytime I set the IMG_DIRECT flag. Thanks, Reza. Thu, 26 May 2011 21:21:19 GMT http://community.qnx.com/sf/go/post86177 Reza Salehi 2011-05-26T21:21:19Z http://community.qnx.com/sf/go/post86166 Hello, For one of our embedded system we have a custom video driver working with QNX 6.3. Now I want to update it for QNX 6.4/6.5. I'm currently reading this doc : http://www.qnx.com/download/feature.html?programid=20957 Now I need to get the updated sources of the includes and sample drivers. But since the last changes in F27 I have not access to these sources. How is it possible to get these access? Thanks, Christophe Thu, 26 May 2011 14:50:05 GMT http://community.qnx.com/sf/go/post86166 Christophe Hannoyer 2011-05-26T14:50:05Z http://community.qnx.com/sf/go/post86102 Hi Derek, I have a question with regard to img_t but in regard to who is allocating memory for access.direct.data pointer when using setting the IMG_DIRECT flag? Will the img_load_file() allocate memory for it? I am trying to read a .png file, make some modification to the file and then save it as new .png file. However, when I set the IMG_DIRECT flag, my system hangs. If I don't set the IMG_DIRECT flag, the file is loaded correctly. I am using QNX 6.4.1 on the host and the same version running on a VM target. I appreciate it if you can give me pointer on where the problem could be. Thanks, RS. Wed, 25 May 2011 00:13:23 GMT http://community.qnx.com/sf/go/post86102 Reza Salehi 2011-05-25T00:13:23Z http://community.qnx.com/sf/go/post86101 Hi Joel, I tried to use the direct pointer approach, but my system hangs. Below is a code snipet where it hangs: img_t img_day; if ((rc = img_lib_attach(&ilib)) != IMG_ERR_OK) { fprintf(stderr, "img_lib_attach() failed: %d\n", rc); return rc; } img_day.flags = 0; img_day.flags |= IMG_DIRECT; // /tmp/stop.png is the location of the file on the target VM system img_template_file_Day = "/tmp/stop.png"; // The code hangs after making the call below. If I don't set the IMG_DIRECT flag, it works. if ((rc = img_load_file(ilib, img_template_file_Day, NULL, &img_day)) != IMG_ERR_OK) { fprintf(stderr, "img_load_file(%s) failed on Day Template: %d\n", img_template_file_Day, rc); // return rc; } Tue, 24 May 2011 23:06:36 GMT http://community.qnx.com/sf/go/post86101 Reza Salehi 2011-05-24T23:06:36Z http://community.qnx.com/sf/go/post86097 Well, I think my problem is that I am not familiar enough with the graphic sub-systems of QNX to know what I want to do :). Basically, I have some graphic artists that are providing me base .png files. I need to draw an ellipse based on some dynamic data and save the result as another .png file. So, whatever is the fastest to accomplish this would work for me. I appreciate it if you have any suggestion or code snippet to help me get started. Thanks, Reza Tue, 24 May 2011 20:14:43 GMT http://community.qnx.com/sf/go/post86097 Reza Salehi 2011-05-24T20:14:43Z http://community.qnx.com/sf/go/post86096 Do you want to modify the img data using gf rendering or just via a pointer in software? If you don't plan on using gf rendering, then there's no need for a gf surface. -Joel -----Original Message----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: May 24, 2011 3:02 PM To: advanced-graphics Subject: Re: How to use devg-flat in gf_dev_attach? Thanks Joel. But, my understanding was that in order to modify the image data, I will have to first attach it to a gf surface, modify it, and then save it. Just so I understand, if I only need need to modify a .png file (not display it), I don't need to use gf at all? In other words, I don't need to attach and great a gf surface at all? Basically, below is what I am trying to do: 1. Read a .png file from the file system (i.e. /tmp/test.png) 2. Modify this file with some algorithm to draw an ellipse 3. Same the result from #2 as /tmp/new_image.png Thanks, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post86093 Tue, 24 May 2011 19:38:35 GMT http://community.qnx.com/sf/go/post86096 Joel Pilon 2011-05-24T19:38:35Z http://community.qnx.com/sf/go/post86093 Thanks Joel. But, my understanding was that in order to modify the image data, I will have to first attach it to a gf surface, modify it, and then save it. Just so I understand, if I only need need to modify a .png file (not display it), I don't need to use gf at all? In other words, I don't need to attach and great a gf surface at all? Basically, below is what I am trying to do: 1. Read a .png file from the file system (i.e. /tmp/test.png) 2. Modify this file with some algorithm to draw an ellipse 3. Same the result from #2 as /tmp/new_image.png Thanks, Reza. Tue, 24 May 2011 19:02:28 GMT http://community.qnx.com/sf/go/post86093 Reza Salehi 2011-05-24T19:02:28Z http://community.qnx.com/sf/go/post86090 If you just want to encode/decode image data you don't need GF. You can either pass or get a pointer to the img data by just using libimg. Tue, 24 May 2011 18:30:37 GMT http://community.qnx.com/sf/go/post86090 Joel Pilon 2011-05-24T18:30:37Z http://community.qnx.com/sf/go/post86089 I am trying to read a .png file, modify it and write a back to the file system. In order to do that, my understanding is, that I need to use both gf and img libraries. I don't want to use any specific HW to attach to as I don't need to display my .png file. All I want to do is to be able to create surface so that I can modify my .png file. In order to create a surface, I need to first attach to a device. My understanding is that I can use devg-flat as a device. However I am not sure, how to install devg-flat driver and related files into my IDE and target. I also don't know how to use devg-flat in the call gf_dev_attach() call? I have already added libffb.so to extra libraries section of IDE. I appreciate it if anyone can give me some pointers on this. Regards, Reza. Tue, 24 May 2011 18:27:12 GMT http://community.qnx.com/sf/go/post86089 Reza Salehi 2011-05-24T18:27:12Z http://community.qnx.com/sf/go/post86031 Reza Salehi wrote: > Hi Armin, > > Thanks for your comment. Do you know if there is a site that tells you how to install sdl_gfx library/ies and write a hello world program to draw an ellipse on VM x86 target running Nuternia 6.5? SDL 1.3: http://community.qnx.com/sf/projects/qnx_community_sdl_project/ --> have a look to the OpenGL ES support SDL_Gfx: http://www.ferzkopp.net/joomla/content/view/19/14/ ... it compiles out of the box. --Armin > Thanks in advance, > > Reza. > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post86028 > > Sat, 21 May 2011 11:43:26 GMT http://community.qnx.com/sf/go/post86031 Armin Steinhoff 2011-05-21T11:43:26Z http://community.qnx.com/sf/go/post86028 Hi Armin, Thanks for your comment. Do you know if there is a site that tells you how to install sdl_gfx library/ies and write a hello world program to draw an ellipse on VM x86 target running Nuternia 6.5? Thanks in advance, Reza. Fri, 20 May 2011 23:13:14 GMT http://community.qnx.com/sf/go/post86028 Reza Salehi 2011-05-20T23:13:14Z http://community.qnx.com/sf/go/post86000 Joel Pilon wrote: > My mistake, my memory is a little rusty. You'll have to generate and tessellate your own ellipses in gf. Or you might be able to use photon and the pgdrawellise function. ... with SDL_Gfx you will get antialized ellipses :) --Armin http://www.steinhoff-automation.com > ----- Original Message ----- > From: Reza Salehi [mailto:community-noreply@qnx.com] > Sent: Thursday, May 19, 2011 08:42 PM > To: advanced-graphics<post85987@community.qnx.com> > Subject: Re: Newbie Question - Help with GF > > Thanks Joel. However, after checking the libgf, it seems like it doesn't support drawing of ellipses! I only see polyline and rectangular drawing functions. > > Cheers, > > Reza. > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85987 > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85995 > > Fri, 20 May 2011 08:53:18 GMT http://community.qnx.com/sf/go/post86000 Armin Steinhoff 2011-05-20T08:53:18Z http://community.qnx.com/sf/go/post85995 My mistake, my memory is a little rusty. You'll have to generate and tessellate your own ellipses in gf. Or you might be able to use photon and the pgdrawellise function. ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Thursday, May 19, 2011 08:42 PM To: advanced-graphics <post85987@community.qnx.com> Subject: Re: Newbie Question - Help with GF Thanks Joel. However, after checking the libgf, it seems like it doesn't support drawing of ellipses! I only see polyline and rectangular drawing functions. Cheers, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post85987 Fri, 20 May 2011 02:52:36 GMT http://community.qnx.com/sf/go/post85995 Joel Pilon 2011-05-20T02:52:36Z http://community.qnx.com/sf/go/post85987 Thanks Joel. However, after checking the libgf, it seems like it doesn't support drawing of ellipses! I only see polyline and rectangular drawing functions. Cheers, Reza. Fri, 20 May 2011 00:42:55 GMT http://community.qnx.com/sf/go/post85987 Reza Salehi 2011-05-20T00:42:55Z http://community.qnx.com/sf/go/post85984 Oops accidently hit send to soon. You can get a pointer from a gf surface using gf to either read or write image data. Libimg accepts a pointer for the src or dst for image encode/decode operations. ----- Original Message ----- From: Joel Pilon Sent: Thursday, May 19, 2011 07:46 PM To: 'post85982@community.qnx.com' <post85982@community.qnx.com> Subject: Re: Newbie Question - Help with GF I don't have a link handy, but you can get a pointer from a CPU accessible surface. You can pass the pointrr ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Thursday, May 19, 2011 07:44 PM To: advanced-graphics <post85982@community.qnx.com> Subject: Re: Newbie Question - Help with GF Thank you very much Joel. At least I know where to start looking. After looking into libimg, I found the img_load and img_load_file APIs. However, one of these APIs deal with streaming data and another with a filesystem file! I could not find and API that would directly read and load an image from GF surface. Can you please tell which libimg API does that? Also, QNX usually has some very good code examples or tutorials on these types of things. Do you know a link or a location where I can find an example of how to do something like this instead of me asking stupid questions and wasting peoples time on the this Forum? Thanks again, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post85982 Thu, 19 May 2011 23:49:01 GMT http://community.qnx.com/sf/go/post85984 Joel Pilon 2011-05-19T23:49:01Z http://community.qnx.com/sf/go/post85983 I don't have a link handy, but you can get a pointer from a CPU accessible surface. You can pass the pointrr ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Thursday, May 19, 2011 07:44 PM To: advanced-graphics <post85982@community.qnx.com> Subject: Re: Newbie Question - Help with GF Thank you very much Joel. At least I know where to start looking. After looking into libimg, I found the img_load and img_load_file APIs. However, one of these APIs deal with streaming data and another with a filesystem file! I could not find and API that would directly read and load an image from GF surface. Can you please tell which libimg API does that? Also, QNX usually has some very good code examples or tutorials on these types of things. Do you know a link or a location where I can find an example of how to do something like this instead of me asking stupid questions and wasting peoples time on the this Forum? Thanks again, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post85982 Thu, 19 May 2011 23:46:10 GMT http://community.qnx.com/sf/go/post85983 Joel Pilon 2011-05-19T23:46:10Z http://community.qnx.com/sf/go/post85982 Thank you very much Joel. At least I know where to start looking. After looking into libimg, I found the img_load and img_load_file APIs. However, one of these APIs deal with streaming data and another with a filesystem file! I could not find and API that would directly read and load an image from GF surface. Can you please tell which libimg API does that? Also, QNX usually has some very good code examples or tutorials on these types of things. Do you know a link or a location where I can find an example of how to do something like this instead of me asking stupid questions and wasting peoples time on the this Forum? Thanks again, Reza. Thu, 19 May 2011 23:44:14 GMT http://community.qnx.com/sf/go/post85982 Reza Salehi 2011-05-19T23:44:14Z http://community.qnx.com/sf/go/post85979 I'd suggest taking a look at libimg. There also doc for the api as well. The gf api allows you to render things like ellipses and libimg would allow you to write data from gf surfaces as pngs. You could then load png files into gf surfaces or to render them as gf images. ----- Original Message ----- From: Reza Salehi [mailto:community-noreply@qnx.com] Sent: Thursday, May 19, 2011 06:30 PM To: advanced-graphics <post85978@community.qnx.com> Subject: Re: Newbie Question - Help with GF Sorry, I had a typo in the previous e-mail: I was trying to say that I am trying to draw ellipses and save them as a png file. Thanks, Reza. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post85978 Thu, 19 May 2011 22:38:51 GMT http://community.qnx.com/sf/go/post85979 Joel Pilon 2011-05-19T22:38:51Z http://community.qnx.com/sf/go/post85978 Sorry, I had a typo in the previous e-mail: I was trying to say that I am trying to draw ellipses and save them as a png file. Thanks, Reza. Thu, 19 May 2011 22:30:37 GMT http://community.qnx.com/sf/go/post85978 Reza Salehi 2011-05-19T22:30:37Z http://community.qnx.com/sf/go/post85977 Hi All, I am Newbie with QNX GF and QNX in general. I am trying to use Momentics IDE to connect to a x86 VM target using qconn. What I want to do is to be able to draw an based on some parameters and then save it in a PNG format on the target file system (VM running neutrino). I would like to then be able to load the png file in a browser and display the image. Can anyone someone tell me what is the best way to start? Is GF the correct place to start. With GF, I could not find anyway to render to a file rather that a graphic device! I apologize if some my graphic terminology is not correct. I am trying to evaluate the QNX platform for a future project and this would help me get started. Thanks in advance. Reza. Thu, 19 May 2011 21:35:09 GMT http://community.qnx.com/sf/go/post85977 Reza Salehi 2011-05-19T21:35:09Z http://community.qnx.com/sf/go/post85798 Thanks, Misha. It does seem to do something now. On 05/17/2011 09:19 AM, Misha Nefedov wrote: > Yes, I got this. The problem is that we asked to NO rendering buffer when doing th PfAttachCx(). Give it a number, for example: > > PfAttachCx( NULL, 32*1024 ); > > The size of the buffer should depend on how large the strings and the font size are. > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85785 Tue, 17 May 2011 16:15:31 GMT http://community.qnx.com/sf/go/post85798 Ronald Burkey 2011-05-17T16:15:31Z http://community.qnx.com/sf/go/post85785 Yes, I got this. The problem is that we asked to NO rendering buffer when doing th PfAttachCx(). Give it a number, for example: PfAttachCx( NULL, 32*1024 ); The size of the buffer should depend on how large the strings and the font size are. Tue, 17 May 2011 14:19:24 GMT http://community.qnx.com/sf/go/post85785 Misha Nefedov 2011-05-17T14:19:24Z http://community.qnx.com/sf/go/post85745 On 05/16/2011 02:55 PM, Misha Nefedov wrote: > Hard to tell. Can you please post the entire source file -- for me to try? Here's code that fails for me as described. I compiled it with "ntox86-gcc -o FontTest FontTest.c -lph" and ran the font server with "phfont -d /usr/photon/font_repository -D /usr/photon/font_repository". #include <stdio.h> #include <errno.h> #include <photon/Pf.h> void Callback (void *ctx, const pf_point_t *pos, const FontRender *fr) { fprintf (stderr, "Callback: %d,%d\n", pos->x, pos->y); fprintf (stderr, "Callback: %d,%d %d,%d %d, %d, %d, %p\n", fr->size.x, fr->size.y, fr->offset.x, fr->offset.y, fr->width, fr->bpl, fr->bpp, fr->bmptr); } int main (void) { char *MyFontName = "Courier10 BT"; int FontSize = 10; int i; struct _Pf_ctrl *FontServer = NULL; FontID *ID; FontName Description; pf_point_t pp = { 50, 50 }; FontServer = PfAttachCx (NULL, 0); if (FontServer == NULL) { fprintf (stderr, "Cannot attach to font server.\n"); return (1); } if (NULL == PfGenerateFontNameCx (FontServer, MyFontName, 0, FontSize, Description)) { fprintf (stderr, "Cannot get font name %s size %d style 0x%X\n", MyFontName, FontSize, 0); return (1); } i = PfRenderCx (FontServer, FontServer, Description, 0L, 0L, "Hello, world!", 0, 0, &pp, NULL, Callback); fprintf (stderr, "PfRenderCx() returned %d\n", i); if (i) fprintf (stderr, "%s\n", strerror (errno)); return (0); } > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85742 Mon, 16 May 2011 20:15:32 GMT http://community.qnx.com/sf/go/post85745 Ronald Burkey 2011-05-16T20:15:32Z http://community.qnx.com/sf/go/post85743 GF does not support blitting to/from YUV surfaces so you will not be able to set a context to this surface. The other formats are all RGB so they work. If you need to transfer YUV data between surfaces you'll have to manually copy this. Alternately depending on your application/use-case you could have multiple YUV surfaces and just re-target the layer to point at the different surfaces. (gf_layer_set_surfaces()) -----Original Message----- From: Nikshep Patil [mailto:community-noreply@qnx.com] Sent: May 16, 2011 3:35 PM To: advanced-graphics Subject: Re: RE: gf_context_set_surface(): Problem with color format GF_FORMAT_PACK_YUV_UYVY Hi Michael, I am working with an internal driver. Regards _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post85736 Mon, 16 May 2011 19:55:11 GMT http://community.qnx.com/sf/go/post85743 Michael Van Reenen 2011-05-16T19:55:11Z http://community.qnx.com/sf/go/post85742 Hard to tell. Can you please post the entire source file -- for me to try? Mon, 16 May 2011 19:54:59 GMT http://community.qnx.com/sf/go/post85742 Misha Nefedov 2011-05-16T19:54:59Z http://community.qnx.com/sf/go/post85739 I am having problems with gf_context_set_surface() of step 3 with the color format GF_FORMAT_PACK_YUV_UYVY. Mon, 16 May 2011 19:39:34 GMT http://community.qnx.com/sf/go/post85739 Nikshep Patil 2011-05-16T19:39:34Z http://community.qnx.com/sf/go/post85737 On 05/16/2011 01:17 PM, Misha Nefedov wrote: > The 'Description' should be replaced with 'FontName' when calling the PfFindFont(). The PfFindFont() is similar to PfGenerateFontName(), it only returns FontID. I am not sure why you need it. Well, I was simply following the sample code in the PfRenderCx() API doc, as you suggested. The sample code calls PfFindFontCx(). Personally, I'm willing to do without it, even though I don't see why it should be failing. > The 'Description' you got from the Generate function is good to be used with the subsequent PfRenderCx(). Okay, I think you're suggesting something like this: FontName Description; char *FontName = "Courier10 BT"; pf_point_t pp = { 50, 50 }; int FontSize = 10; FontServer = PfAttachCx (NULL, 0); ... check for error ... if (NULL == PfGenerateFontNameCx (FontServer, FontName, 0, FontSize, Description)) { ... error ... } i = PfRenderCx (FontServer, FontServer, Description, 0L, 0L, "Hello, world!", 0, 0, &pp, NULL, Callback); ... check for error ... This code fails when it reaches PfRenderCx(). The error message displayed by "perror(strerror(errno))" is "Invalid argument". > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85727 Mon, 16 May 2011 19:35:18 GMT http://community.qnx.com/sf/go/post85737 Ronald Burkey 2011-05-16T19:35:18Z http://community.qnx.com/sf/go/post85736 Hi Michael, I am working with an internal driver. Regards Mon, 16 May 2011 19:35:02 GMT http://community.qnx.com/sf/go/post85736 Nikshep Patil 2011-05-16T19:35:02Z http://community.qnx.com/sf/go/post85733 Hi Misha, A correction. I am using the gf_surface_create_layer(&surface, &layer, 1, 0, width, height, GF_FORMAT_PACK_YUV_UYVY, NULL, flag) call; NOT gf_surface_create() as I earlier mentioned. I am trying to implement the following steps - 1. Create surface_scratch using gf_surface_create() - 2. Create surface_main on the main layer using gf_surface_create_layer() 3. Create a context and set it to surface_main using gf_context_set_surface() 4. Blit from the surface_scratch to the surface_main I am having problems with gf_surface_create_layer() of step 3 with the color format GF_FORMAT_PACK_YUV_UYVY. With the other color formats (already listed in earlier post) my application works fine, blitting is successful. Regards Mon, 16 May 2011 19:11:03 GMT http://community.qnx.com/sf/go/post85733 Nikshep Patil 2011-05-16T19:11:03Z http://community.qnx.com/sf/go/post85732 What platform/driver are you working with? Thanks -----Original Message----- From: Nikshep Patil [mailto:community-noreply@qnx.com] Sent: May-16-11 1:37 PM To: advanced-graphics Subject: gf_context_set_surface(): Problem with color format GF_FORMAT_PACK_YUV_UYVY Hi All, I am having problems with the gf_context_set_surface() call. I create a surface on the main layer of my display with color format GF_FORMAT_PACK_YUV_UYVY - _uint32 flag = GF_SURFACE_CREATE_CPU_LINEAR_ACCESSIBLE | GF_SURFACE_CREATE_CPU_FAST_ACCESS; gf_surface_create(&surface_exp, gf_dev, width, height, GF_FORMAT_PACK_YUV_UYVY, NULL, flag) The surface is created successfully. But the subsequent call to gf_context_set_surface() fails with return value 7. Also, if I create the surface with other color formats (GF_FORMAT_PACK_RGB565, GF_FORMAT_PACK_ARGB1555, GF_FORMAT_BGR888, GF_FORMAT_BGRA8888), the call to gf_context_set_surface() works without any problem. Could you please help me with this...? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post85722 Mon, 16 May 2011 18:49:25 GMT http://community.qnx.com/sf/go/post85732 Michael Van Reenen 2011-05-16T18:49:25Z http://community.qnx.com/sf/go/post85727 The 'Description' should be replaced with 'FontName' when calling the PfFindFont(). The PfFindFont() is similar to PfGenerateFontName(), it only returns FontID. I am not sure why you need it. The 'Description' you got from the Generate function is good to be used with the subsequent PfRenderCx(). Mon, 16 May 2011 18:17:10 GMT http://community.qnx.com/sf/go/post85727 Misha Nefedov 2011-05-16T18:17:10Z http://community.qnx.com/sf/go/post85726 Error #7 -- GF_ERR_PARM -- The 2D engine can't render to the surface. Why do you need a context with this surface? Mon, 16 May 2011 18:11:50 GMT http://community.qnx.com/sf/go/post85726 Misha Nefedov 2011-05-16T18:11:50Z http://community.qnx.com/sf/go/post85725 So Misha, as I said before, you were right and PfGenerateFontNameCx() does not segfault. But I must still be failing to understand some basic point. Right now I'm trying the following code: FontServer = PfAttachCx (NULL, 0); if (FontServer == NULL) { fprintf (stderr, "Cannot attach to font server.\n"); goto Error; } #if 1 { char *FontName = "Courier10 BT"; FontSize = 10; if (NULL == PfGenerateFontNameCx (FontServer, FontName, 0, FontSize, Description)) { fprintf (stderr, "Cannot get font name %s size %d style 0x%X\n", FontName, FontSize, 0); return (1); } ID = PfFindFontCx (FontServer, Description, 0, FontSize); if (NULL == ID) { fprintf (stderr, "Cannot find font %s size %d style 0x%X\n", FontName, FontSize, 0); perror (strerror (errno)); return (1); } } #endif The call to PfAttachCx() succeeds. The call to PfGenerateFontNameCx() succeeds ... with the code shown, it provides a Description[] of "courier10bts10". However, PfFindFontCx() fails with a return value of NULL. errno is set to ESRCH, indicating no font found. I've tried various other fonts as well, with no luck. What am I missing here? On 05/16/2011 10:16 AM, Misha Nefedov wrote: > This is likely that you are trying to use photon wrapper functions, and since you are not connected to photon they fail. > Change the code to use Pf*Cx() API. For example PfGenerateFontNameCx(). It takes an extra parameter which is a struct _Pf_ctrl * -- the one returned by the PfAttachCx(). > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85711 Mon, 16 May 2011 17:51:00 GMT http://community.qnx.com/sf/go/post85725 Ronald Burkey 2011-05-16T17:51:00Z http://community.qnx.com/sf/go/post85722 Hi All, I am having problems with the gf_context_set_surface() call. I create a surface on the main layer of my display with color format GF_FORMAT_PACK_YUV_UYVY - _uint32 flag = GF_SURFACE_CREATE_CPU_LINEAR_ACCESSIBLE | GF_SURFACE_CREATE_CPU_FAST_ACCESS; gf_surface_create(&surface_exp, gf_dev, width, height, GF_FORMAT_PACK_YUV_UYVY, NULL, flag) The surface is created successfully. But the subsequent call to gf_context_set_surface() fails with return value 7. Also, if I create the surface with other color formats (GF_FORMAT_PACK_RGB565, GF_FORMAT_PACK_ARGB1555, GF_FORMAT_BGR888, GF_FORMAT_BGRA8888), the call to gf_context_set_surface() works without any problem. Could you please help me with this...? Mon, 16 May 2011 17:37:06 GMT http://community.qnx.com/sf/go/post85722 Nikshep Patil 2011-05-16T17:37:06Z http://community.qnx.com/sf/go/post85720 Forget my last message. I was just being dumb, and didn't pass PfGenerateFontNameCx() the right struct. On 05/16/2011 10:16 AM, Misha Nefedov wrote: > This is likely that you are trying to use photon wrapper functions, and since you are not connected to photon they fail. > Change the code to use Pf*Cx() API. For example PfGenerateFontNameCx(). It takes an extra parameter which is a struct _Pf_ctrl * -- the one returned by the PfAttachCx(). > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85711 Mon, 16 May 2011 16:55:14 GMT http://community.qnx.com/sf/go/post85720 Ronald Burkey 2011-05-16T16:55:14Z http://community.qnx.com/sf/go/post85719 Well, you're right that it doesn't segfault with PfGenerateFontNameCx(). The next problem is that no matter what pkgDescription argument I plug into PfGenerateFontNameCx(), the function always returns NULL. I guess the names from the fontdir file are not what is supposed to be in pkgDescription. Certainly, the string "Helvetica" as given in the sample code doesn't work. How can I find a valid pkgDescription to plug in? On 05/16/2011 10:16 AM, Misha Nefedov wrote: > This is likely that you are trying to use photon wrapper functions, and since you are not connected to photon they fail. > Change the code to use Pf*Cx() API. For example PfGenerateFontNameCx(). It takes an extra parameter which is a struct _Pf_ctrl * -- the one returned by the PfAttachCx(). > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85711 Mon, 16 May 2011 16:27:21 GMT http://community.qnx.com/sf/go/post85719 Ronald Burkey 2011-05-16T16:27:21Z http://community.qnx.com/sf/go/post85711 This is likely that you are trying to use photon wrapper functions, and since you are not connected to photon they fail. Change the code to use Pf*Cx() API. For example PfGenerateFontNameCx(). It takes an extra parameter which is a struct _Pf_ctrl * -- the one returned by the PfAttachCx(). Mon, 16 May 2011 15:15:53 GMT http://community.qnx.com/sf/go/post85711 Misha Nefedov 2011-05-16T15:15:53Z http://community.qnx.com/sf/go/post85709 Oops! I was a bit to hasty in the code snippet I sent in my last message. Here's a better one: FontServer = PfAttach (NULL, 0); if (FontServer == NULL) { fprintf (stderr, "Cannot attach to font server.\n"); goto Error; } for (i = 0; i < 3; i++) for (j = 0; j < NUM_FONT_SIZES; j++) { int FontSize; FontID *ID; FontName Description; FontSize = MIN_FONT_SIZE + INC_FONT_SIZE * j; if (NULL == PfGenerateFontName ( FontDescriptions[i], FontStyles[i], FontSize, Description)) { fprintf (stderr, "Cannot get font name %s size %d style 0x%X\n", FontDescriptions[i], FontSize, FontStyles[i]); return (1); } ID = PfFindFont (Description, FontStyles[i], FontSize); if (NULL == ID) { fprintf (stderr, "Cannot find font %s size %d style 0x%X\n", FontDescriptions[i], FontSize, FontStyles[i]); return (1); } FontStructures[i]->ID = ID; } Here the segfault occurs as soon as PfGenerateFontName() is hit. The arguments to PfGenerateFontName() correspond to the description I gave for the arguments of PfFindFont() in my last message. In point of fact, the segfault occurs if I simply run the sample code in the PfGenerateFontName() doc: FontServer = PfAttach (NULL, 0); if (FontServer == NULL) { fprintf (stderr, "Cannot attach to font server.\n"); goto Error; } { char szHelvetica12[MAX_FONT_TAG]; if (PfGenerateFontName ("Helvetica", PF_STYLE_BOLD, 12, szHelvetica12) == NULL) { perror ("Unable to find font"); } } Mon, 16 May 2011 14:17:47 GMT http://community.qnx.com/sf/go/post85709 Ronald Burkey 2011-05-16T14:17:47Z http://community.qnx.com/sf/go/post85705 On 05/13/2011 02:20 PM, Misha Nefedov wrote: > I am not aware of a Pf*() tutorial. I recommend starting with the sample code that is in PfRender() API docs. Thanks, Misha, I hadn't gotten as far as trying to render the text, so I hadn't yet become aware of that sample code. More on that below. > Also check that: > -- you are running pfont, Here's what "ps -Af | grep phfont" says: 0 1163315 1 - May16 ? 00:00:00 phfont -d /usr/photon/font_repository 0 1163315 1 - May16 ? 00:00:00 phfont -d /usr/photon/font_repository > -- check sloginfo, As far as sloginfo is concerned, the following lines seem to be the only relevant ones: ... May 16 07:53:10 1 8 0 phfont: init... May 16 07:53:10 1 8 0 phfont: initialized. May 16 07:53:10 1 8 0 phfont: '/dev/phfont[<32|64>]' server installed. ... > -- see where the app is crashing. As I understand it, what the sample code in the PfRender() docs say to do is: 1. Run PfAttach(). 2. Run PfFindFont(). 3. Run PfRender(). I segfault the very first time I hit PfFindFont(). Here's the relevant code-snippet from my program: ... FontServer = PfAttach (NULL, 0); if (FontServer == NULL) { fprintf (stderr, "Cannot attach to font server.\n"); goto Error; } for (i = 0; i < 3; i++) for (j = 0; j < NUM_FONT_SIZES; j++) { int FontSize; FontID *ID; FontSize = MIN_FONT_SIZE + INC_FONT_SIZE * j; ID = PfFindFont (FontDescriptions[i], FontStyles[i], FontSize); if (NULL == ID) { fprintf (stderr, "Cannot find font %s size %d style 0x%X\n", FontDescriptions[i], FontSize, FontStyles[i]); } FontStructures[i]->ID = ID; } .... At the point where the segfault occurs in PfFindFont(): * FontDescriptions[i] is a pointer to the string "ronsanss", which is a TrueType font that I've installed and is known-good (at least in Linux). When I say I've "installed" it, I mean that I hope I installed it correctly and that one of the lines in /usr/photon/font_repository/fontdir is "ronsanss,0@RonSans.ttf,Ron Sans,0,,000D-FFFD,p,228x151,4508K". Please recall that I'm not running Photon, so I'm not aware of any good way to know that the installation was correct until my app actually works. * FontStyles[i] is 16 (PF_STYLE_ANTIALIAS). * FontSize is 10. > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85678 Mon, 16 May 2011 13:29:10 GMT http://community.qnx.com/sf/go/post85705 Ronald Burkey 2011-05-16T13:29:10Z http://community.qnx.com/sf/go/post85680 phfont ;-) Fri, 13 May 2011 19:58:24 GMT http://community.qnx.com/sf/go/post85680 Misha Nefedov 2011-05-13T19:58:24Z http://community.qnx.com/sf/go/post85679 What is pfont? If you meant phfont, yes ps shows that it's running. On 05/13/2011 02:20 PM, Misha Nefedov wrote: > I am not aware of a Pf*() tutorial. I recommend starting with the sample code that is in PfRender() API docs. > Also check that: > -- you are running pfont, > -- check sloginfo, > -- see where the app is crashing. > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85678 Fri, 13 May 2011 19:47:52 GMT http://community.qnx.com/sf/go/post85679 Ronald Burkey 2011-05-13T19:47:52Z http://community.qnx.com/sf/go/post85678 I am not aware of a Pf*() tutorial. I recommend starting with the sample code that is in PfRender() API docs. Also check that: -- you are running pfont, -- check sloginfo, -- see where the app is crashing. Fri, 13 May 2011 19:20:04 GMT http://community.qnx.com/sf/go/post85678 Misha Nefedov 2011-05-13T19:20:04Z http://community.qnx.com/sf/go/post85673 Thanks, Misha, that's very useful. The platform I'm working on is actually a CAR system that doesn't seem to have phfont on it, but if I copy a copy of phfont over from QNX 6.5.0, it seems to run and not complain. However ... as soon as my app tries to use any of the API's font-related functions there's a segfault. Recall that I'm not running Photon. I wonder if there's some kind of initialization I'm supposed to be doing that would normally have been done by starting Photon? Or, could a versioning discrepancy in phfont be the problem? Or perhaps I simply don't know what I'm doing in regard to text rendering. Is there a suitable coding tutorial somewhere? (Remember ... I don't have any user interface here, so any tutorial that involves displaying stuff in windows in Photon is of limited use to me.) Thanks again! On 05/13/2011 08:45 AM, Misha Nefedov wrote: > -- start 'phfont -d /usr/photon/font_repository' -- this will run the server -- you do not need photon > -- use PfAttach(), PfRender(), etc API to render the fonts -- http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.photon_lib_ref/pf-base.html > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post85666 Fri, 13 May 2011 15:59:11 GMT http://community.qnx.com/sf/go/post85673 Ronald Burkey 2011-05-13T15:59:11Z http://community.qnx.com/sf/go/post85666 -- start 'phfont -d /usr/photon/font_repository' -- this will run the server -- you do not need photon -- use PfAttach(), PfRender(), etc API to render the fonts -- http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.photon_lib_ref/pf-base.html Fri, 13 May 2011 13:45:17 GMT http://community.qnx.com/sf/go/post85666 Misha Nefedov 2011-05-13T13:45:17Z http://community.qnx.com/sf/go/post85658 I'm sure this is my own failure to understand the obvious, but if somebody could give me some pointers it would be very helpful. The application program I am working on continually reads jpg and/or png files, manipulates them in various ways, then writes out a bmp file, using the graphics framework. There is no user interface. Photon is not running. The application works fine, except that I now find I need to render text onto the images, and can't figure out even the basic steps to do so. That's my general problem, but far as specifics are concerned, I have two questions to start with: 1. Given that Photon isn't being used, what software can I use as a font server, and what are the specifics of obtaining and starting up that software outside of a Photon-related context? 2. How does one interact with the font server within the context of the graphics framework to get the text rendered into memory-buffered imagery? The names of specific API functions would be very helpful. Thanks! Fri, 13 May 2011 10:21:46 GMT http://community.qnx.com/sf/go/post85658 Ronald Burkey 2011-05-13T10:21:46Z http://community.qnx.com/sf/go/post84497 Known problem, contact support. -----Original Message----- From: Ronald Burkey [mailto:community-noreply@qnx.com] Sent: March 31, 2011 3:58 PM To: advanced-graphics Subject: Memory leak in gf_draw_polyline()? I notice that when I use gf_draw_polyline(), every call to the function seems to perform 6 more calls to malloc() than to free(). Or at least, that's what the "Malloc Information" view in Momentics says. This is measurable both in single-stepping over the gf_draw_polyline() function and by running my app for an extended period of time and maintaining a count of the number of times gf_draw_polyline() is called. Is this a known problem gf_draw_polyline(), or can it be caused by something I'm doing? The lines being drawn look perfectly fine on the output images, and I never would have noticed the problem if my program's memory usage hadn't been building up unexpectedly. In other words, I have no reason from the program's behavior to suspect that I'm using the function incorrectly. I'm using development platform 6.5.0 for an x86 target system. Also, I'm drawing to memory, and not to a physical display. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post84496 Thu, 31 Mar 2011 19:59:03 GMT http://community.qnx.com/sf/go/post84497 Derek Leach 2011-03-31T19:59:03Z http://community.qnx.com/sf/go/post84496 I notice that when I use gf_draw_polyline(), every call to the function seems to perform 6 more calls to malloc() than to free(). Or at least, that's what the "Malloc Information" view in Momentics says. This is measurable both in single-stepping over the gf_draw_polyline() function and by running my app for an extended period of time and maintaining a count of the number of times gf_draw_polyline() is called. Is this a known problem gf_draw_polyline(), or can it be caused by something I'm doing? The lines being drawn look perfectly fine on the output images, and I never would have noticed the problem if my program's memory usage hadn't been building up unexpectedly. In other words, I have no reason from the program's behavior to suspect that I'm using the function incorrectly. I'm using development platform 6.5.0 for an x86 target system. Also, I'm drawing to memory, and not to a physical display. Thu, 31 Mar 2011 19:58:01 GMT http://community.qnx.com/sf/go/post84496 Ronald Burkey 2011-03-31T19:58:01Z http://community.qnx.com/sf/go/post84486 I had suspected that is what is happening. I have submitted a request to get access to the source code. Thanks for your response. Thu, 31 Mar 2011 15:21:31 GMT http://community.qnx.com/sf/go/post84486 Robert Murrell 2011-03-31T15:21:31Z http://community.qnx.com/sf/go/post84440 The slog message you provided indicates that the driver likely doesn't believe it supports 480x272 - (regardless of whether the timing provided matches what the LCD requires) I took a closer look at the driver and realized for X86 the modes supported will depend on what the BIOS provides. There is no way around this right now unless you get the driver source and make a change to disable the driver's BIOS support - thus allowing you to override LCD settings. (this is what happens for non-X86 systems) Thu, 31 Mar 2011 01:05:49 GMT http://community.qnx.com/sf/go/post84440 Michael Van Reenen 2011-03-31T01:05:49Z http://community.qnx.com/sf/go/post84432 Thanks for responding. I took a lot of guesses setting smi7xx.conf based on the display timing diagrams. Its unclear what the units are in the configuration file. Its even less clear on how the numbers relate to the color depth. The display uses pixel clock counts for all horizontal timing and horizontal clocks for all vertical timings. I guess I will have to play with the settings some more. Wed, 30 Mar 2011 19:30:11 GMT http://community.qnx.com/sf/go/post84432 Robert Murrell 2011-03-30T19:30:11Z http://community.qnx.com/sf/go/post84426 Are you specifying a driver configuration file? I believe the sm712 driver will only report 640x480 unless you specifically give the settings in smi7xx.conf. This is passed to the driver via the /etc/system/config/display.conf file -----Original Message----- From: Robert Murrell [mailto:community-noreply@qnx.com] Sent: March 28, 2011 11:37 AM To: advanced-graphics Subject: Re: io-display and BIOS interactions Some additional information from slogger: Mar 27 22:58:20 2 8 200 io-display: driver doesn't support, or not configured for "rgb888" at 480x272, 60Hz I've tried all the published pixel formats and none of them work. Does this mean that io-display or devg-sm7xx.so does not support this format? Also, am I stuck writing my own driver for this format? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post84337 Wed, 30 Mar 2011 18:26:22 GMT http://community.qnx.com/sf/go/post84426 Michael Van Reenen 2011-03-30T18:26:22Z http://community.qnx.com/sf/go/post84337 Some additional information from slogger: Mar 27 22:58:20 2 8 200 io-display: driver doesn't support, or not configured for "rgb888" at 480x272, 60Hz I've tried all the published pixel formats and none of them work. Does this mean that io-display or devg-sm7xx.so does not support this format? Also, am I stuck writing my own driver for this format? Mon, 28 Mar 2011 15:37:15 GMT http://community.qnx.com/sf/go/post84337 Robert Murrell 2011-03-28T15:37:15Z http://community.qnx.com/sf/go/post84329 I am trying to interface an odd-resolution LCD screen to an x86 single-board PC. My goal is to avoid having a custom BIOS created for our application. My plan was to set the board for blank booting (which I have working) and let io-display set the proper settings for the LCD screen, but this isn't working as expected. We are experimenting with two different manufacturer's boards. One uses an SMI SM712 LynxEM4+ graphics chip. The other uses an XGI Technology Volari Z9 chip. The LCD screen is a 480x272 TFT color display (I didn't pick it). For the SM712 I configure io-display to use the smi7xx driver and for the Z9 I use the svga driver. Since the Z9 chip doesn't seem to have an existing QNX driver that targets this hardware, I've been concentrating on the SM712 board. Both board power up OK in CRT 640x480 mode. For the Sm712 board, I have a simple program that opens io-display and can display a simple bitmap. I edited display.conf to set the resolution to 480x272, but the screen always comes up in 648x480, the BIOS default. Next, I tried to customize smi7xx.conf to match the LCD display's timing characteristics. I set the BIOS display settings to 640x480 TFT LCD. When I run my test program, gf_dev_attach returns 2, GF_ERR_IODISPLAY. I will get this error even if I set display.conf to 640x480 resolution to match the BIOS resolution. This error is too generic for me to determine what is wrong. Is there something else I need to set to get io-display to at least attach to the LCD screen? Mon, 28 Mar 2011 14:31:54 GMT http://community.qnx.com/sf/go/post84329 Robert Murrell 2011-03-28T14:31:54Z http://community.qnx.com/sf/go/post84228 Hi All, I have been trying to port the Touch screen driver on the QNX platform. The processor I am working on is OMAP2430. I took the reference code from the IMX Freescale imx35-3ds bsp trunk. It had the code for TSC2007 controller code which was interfaced with I2C to read the touch data. The TSC2046 uses SPI controller to read the touch data. I customized the touch driver code and spi driver to get the touch screen working. I get the touch screen driver loaded. It goes and look for the calibration file but I don't see it any where in my SDP. Just got this from some forum guy. I created my own calib.localhost file. The display resolution is 240x320. I put this entry in the calibration file.. 0x0:319x239:0 2047 0 2047 0 I am not sure if it is right or wrong. Attaching the log files for ur reference. There are couple of log files. 1) touch.log has the log which shows that I am getting continuous interrupt when I configure the GPIO24 (PENIRQ) as LOWLEVELDETECT. 2) touch_1.log file has the log which does not respond to the touchces at all . Configure the GPIO24 (PENIRQ) as FALLINGDETECT. Also ran the "calib" utility to calibrate the touch screen but it doesn't respond to touches at all. One more concern I have is whenever I launch any app say "calculator" the app goes beyond the screen resolution. I could not see the calculator app completely. same goes with the "calib" utility as well. I would appreciate the help in advance. Thu, 24 Mar 2011 12:09:47 GMT http://community.qnx.com/sf/go/post84228 Raj Pandey 2011-03-24T12:09:47Z http://community.qnx.com/sf/go/post83813 Hi All, Has anyone in this forum used libpng.so library? Where can i get the compiled versions of libpng.so & the associated libpng header files for QNX? Bascically i need to create .png images by reading BRGB, GBRG, RGBR ...BRGB,GBRG,RGBR pattern from FPGA. It will be really helpful if someone can give some pointers in this regard.. Thanks in Adv, Lavin Tue, 08 Mar 2011 07:14:57 GMT http://community.qnx.com/sf/go/post83813 Lavin Pottekkat 2011-03-08T07:14:57Z http://community.qnx.com/sf/go/post83495 I've been working with the IMG library for a few months and have a functional image scaler. It can scale most pictures (can't do palatized pictures, GIF & palatized PNG). The rough sequence of operations it uses is: img_load_file img_resize_fs img_write_file I did this in three parts because I need to load in the file to make some determinations about what to do (image smaller than target, unhandleable codec, etc). My testing has determined that for the average picture, 90% of the total run time is spent in img_load_file. Timings determined by calling gettimeofday before and after the operation, plus at the start and end of entire code block. So, my question is, does anybody know of a faster way to load pictures into an img_t object? Our expected file system source is a USB stick and we can't pre-copy the file to our RAM drive. Fri, 25 Feb 2011 13:15:56 GMT http://community.qnx.com/sf/go/post83495 Michael Briggs 2011-02-25T13:15:56Z http://community.qnx.com/sf/go/post83493 Mario - While, yes, it is syntactically legal to do a delete on a NULL, in QNX on ARM-LE v7 it generates a core dump of the file due to being an illegal function. So that's why I was protecting against NULLs. However, Derek's solution was much more elegant and does the job just fine. - Mike -----Original Message----- From: Mario Charest [mailto:community-noreply@qnx.com] Sent: Wednesday, February 23, 2011 2:17 PM To: advanced-graphics Subject: RE: cleaning up an img_t* in C++ You cannot mix delete and malloc. Also in C++ it`s legal to do a delete on a NULL, hence you can get rid of the ifs. > -----Message d'origine----- > De : Michael Briggs [mailto:community-noreply@qnx.com] > Envoyé : 23 février 2011 13:09 > À : advanced-graphics > Objet : cleaning up an img_t* in C++ > > So, i've been working with the IMG library in C++ and I'm working on closing > down memory leaks. > > The way i've been creating my img_t objects is: > > img_t* OrigImage = new img_t(); > > This works well enough until I start doing my house cleaning: > > if (OrigImage->access.direct.data != NULL) { > delete OrigImage->access.direct.data; > } > if (OrigImage->palette != NULL) { > delete OrigImage->palette; > } > delete OrigImage; > > This code works pretty good, except when there's palette information...and > then it crashes. > > So, anybody know a better way to fully clean up an img_t* ? > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83429 > _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83439 Fri, 25 Feb 2011 13:06:56 GMT http://community.qnx.com/sf/go/post83493 Michael Briggs 2011-02-25T13:06:56Z http://community.qnx.com/sf/go/post83491 Derek - Thanks for the sample. It worked perfectly...and helped demonstrate my lack of deep understanding of the img_t structure. :-) I made a cleanup function that passes in an img_t* item, runs your code, then deletes the img_t* item. - Mike -----Original Message----- From: Derek Leach [mailto:community-noreply@qnx.com] Sent: Wednesday, February 23, 2011 1:20 PM To: advanced-graphics Subject: RE: cleaning up an img_t* in C++ try this: if (img->flags & IMG_DIRECT) { free(img->access.direct.data); img->flags &= ~IMG_DIRECT; if (img->flags & IMG_PALETTE) { img->flags &= ~IMG_PALETTE; } } else if (img->flags & IMG_PALETTE) { free(img->palette); img->flags &= ~IMG_PALETTE; } -----Original Message----- From: Michael Briggs [mailto:community-noreply@qnx.com] Sent: February 23, 2011 1:09 PM To: advanced-graphics Subject: cleaning up an img_t* in C++ So, i've been working with the IMG library in C++ and I'm working on closing down memory leaks. The way i've been creating my img_t objects is: img_t* OrigImage = new img_t(); This works well enough until I start doing my house cleaning: if (OrigImage->access.direct.data != NULL) { delete OrigImage->access.direct.data; } if (OrigImage->palette != NULL) { delete OrigImage->palette; } delete OrigImage; This code works pretty good, except when there's palette information...and then it crashes. So, anybody know a better way to fully clean up an img_t* ? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83429 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83432 Fri, 25 Feb 2011 13:05:27 GMT http://community.qnx.com/sf/go/post83491 Michael Briggs 2011-02-25T13:05:27Z http://community.qnx.com/sf/go/post83439 You cannot mix delete and malloc. Also in C++ it`s legal to do a delete on a NULL, hence you can get rid of the ifs. > -----Message d'origine----- > De : Michael Briggs [mailto:community-noreply@qnx.com] > Envoyé : 23 février 2011 13:09 > À : advanced-graphics > Objet : cleaning up an img_t* in C++ > > So, i've been working with the IMG library in C++ and I'm working on closing > down memory leaks. > > The way i've been creating my img_t objects is: > > img_t* OrigImage = new img_t(); > > This works well enough until I start doing my house cleaning: > > if (OrigImage->access.direct.data != NULL) { > delete OrigImage->access.direct.data; > } > if (OrigImage->palette != NULL) { > delete OrigImage->palette; > } > delete OrigImage; > > This code works pretty good, except when there's palette information...and > then it crashes. > > So, anybody know a better way to fully clean up an img_t* ? > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83429 > Wed, 23 Feb 2011 19:17:23 GMT http://community.qnx.com/sf/go/post83439 Mario Charest 2011-02-23T19:17:23Z http://community.qnx.com/sf/go/post83432 try this: if (img->flags & IMG_DIRECT) { free(img->access.direct.data); img->flags &= ~IMG_DIRECT; if (img->flags & IMG_PALETTE) { img->flags &= ~IMG_PALETTE; } } else if (img->flags & IMG_PALETTE) { free(img->palette); img->flags &= ~IMG_PALETTE; } -----Original Message----- From: Michael Briggs [mailto:community-noreply@qnx.com] Sent: February 23, 2011 1:09 PM To: advanced-graphics Subject: cleaning up an img_t* in C++ So, i've been working with the IMG library in C++ and I'm working on closing down memory leaks. The way i've been creating my img_t objects is: img_t* OrigImage = new img_t(); This works well enough until I start doing my house cleaning: if (OrigImage->access.direct.data != NULL) { delete OrigImage->access.direct.data; } if (OrigImage->palette != NULL) { delete OrigImage->palette; } delete OrigImage; This code works pretty good, except when there's palette information...and then it crashes. So, anybody know a better way to fully clean up an img_t* ? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83429 Wed, 23 Feb 2011 18:19:38 GMT http://community.qnx.com/sf/go/post83432 Derek Leach 2011-02-23T18:19:38Z http://community.qnx.com/sf/go/post83429 So, i've been working with the IMG library in C++ and I'm working on closing down memory leaks. The way i've been creating my img_t objects is: img_t* OrigImage = new img_t(); This works well enough until I start doing my house cleaning: if (OrigImage->access.direct.data != NULL) { delete OrigImage->access.direct.data; } if (OrigImage->palette != NULL) { delete OrigImage->palette; } delete OrigImage; This code works pretty good, except when there's palette information...and then it crashes. So, anybody know a better way to fully clean up an img_t* ? Wed, 23 Feb 2011 18:09:01 GMT http://community.qnx.com/sf/go/post83429 Michael Briggs 2011-02-23T18:09:01Z http://community.qnx.com/sf/go/post83283 Dear All, I want to get the home screen on my LCD panel with all the widgets and icon. I read in the forum that in QNX Photon Desktop Manager takes care of it. How do I get this Photon Desktop Manager? I am working on QNX6.5 OS version. I would appreciate the help very much. Regards Thu, 17 Feb 2011 18:05:17 GMT http://community.qnx.com/sf/go/post83283 Raj Pandey 2011-02-17T18:05:17Z http://community.qnx.com/sf/go/post83173 Hi Takshi, I am just hijacking this thread for a minute ... :) >> Takshi Pandey wrote: >>> I could run the 2D demo app VSYNC and it is running fine. Although, I need >> to slay the Photon app for this VSYNC to run coz it goes and attach to the >> same layer that Photon runs on otherwise fails saying layer attach failed. >>> I could not see (~/src/video/photon/SDL_ph_video.c ) in my entire project >> and thats what is surprising me how the display is working. You can run vsync on another layer if your devg supports multi-layers: vsync 0 <- layer 0 vsync 1 <- layer 1 vsync 2 <- layer 2 OR like I mentioned to Raj, you can create a hybrid GF/Photon application as well, which means you can run all those GF applications on the same layer as Photon, in a Photon window. Takshi and Raj, I still do not have a clear understanding about what you want with "video". Do you just want to play a video file, like a .mpg ... or do you want to stream it from a video capture device on your hardware, or do you want to stream a MPEG stream from a network connection? Armin's SDL is great ... I am just trying what to understand what you are asking for. -Derek >> >> OK ... Photon is available. So download the sources of SDL 1.3 and >> recompile it and you will get a "frame buffer" >> >> --Armin >> >>> I am working with OS QNX6.5. >>> >>> Regards, >>> >>>> Takshi Pandey wrote: >>>>> Thanks Armin for the reply. The link that you shared seems that SDL takes >>>> care of everything as far as playing Audio/Video is concern. But I somehow >>>> could not relate this to the devg-xxx.so display driver. I could not see >> any >>>> references to SDL libraries in the display driver. >>>>> The surprising this is that I could see something on the OMAP2430 LCD >> panel >>>> (running a simple demo app) despite not seeing any references to SDL in my >>>> display driver. >>>>> My question are : >>>>> 1) From where the display driver is rendering the image? >>>> SDL is using low level calls of the Photon API in order to create >>>> something like a frame buffer interface. >>>> (~/src/video/photon/SDL_ph_video.c ) >>>> >>>> Doesn't the BSP of the OMAP2430 support Photon ? >>>> >>>> --Armin >>>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Advanced Graphics >>> http://community.qnx.com/sf/go/post83135 >>> >>> > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83153 > > _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83157 Tue, 15 Feb 2011 13:53:37 GMT http://community.qnx.com/sf/go/post83173 Derek Leach 2011-02-15T13:53:37Z http://community.qnx.com/sf/go/post83163 Let me just re-phrase my question again, Derek. I know that the frame buffer is a physical memory which we use as a display memory to render the display images. My question is ..."which part of the devg-driver code does this? any particular api?" I hope I have made myself clear. Regards, > I still do not understand what you are trying to accomplish ... > > You talk of a "frame buffer" ... do you mean the actual display memory > for the layer, or something else? If you are already displaying > application, GF and Photon, then you are using the "frame buffer". > > If not, what will you use this "frame buffer" for? > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 14, 2011 12:43 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging > after Pterm Utility > > Thanks for the reply Derek. I did the porting of display driver in > WindowsCE 6.0 as well. As per the TRM we could allocate a region of > physical memory from SRAM/SDRAM and I just mapped the SDRAM area for the > frame buffer. I am not aware of any video decoder in omap2430. > From all the discussions/forum I know that Frame buffer is a memory > region which must be continuous. But just couldn't relate this with my > devg code or build file. > > As per Armin he says we need to include SDL libraries which takes care > of the frame buffer in QNX but I have not seen any reference of it in my > bsp. > > Regards, > > > Derek, no need for you to spend your time on img_decode_simple issue. > > Just got that stuff working today. I slayed the Photon app and then > run > > "img_decode_simple my.jpg" and I was able to draw the image on the LCD > > panel. > > I just saw another thread inquiring about the FRAME BUFFER concept in > > QNX display driver. > > This one thing is baffling me as well. Although I can do almost > > everything with my display driver ,i.e, draw images, run 2D/3D demo > > apps. The only thing pending is playing a video. > > > > DL: Yes, you cannot run img_decode_simple (GF application) on the > same > > layer that Photon is working, glad you figured it out OK. > > > > Just wanted to know where are we defining the memory for the frame > > buffer. Is it the one in build file, the parameters we pass to the > start > > up script like omap3530 -L 0x87E00000 0x00020000 ? > > I haven't see any reference of frame buffer in the devg code. > > > > The other thing is do we have any test code to test our driver > > thoroughly? > > > > DL: Do you have a video decoder on your board? Does it present to a > > physical address? frame buffer is just a region of memory. > > > > I would appreciate the reply. > > > > Regards > > > > > not yet, I just got to work. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 13, 2011 9:29 PM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging > after > > > Pterm Utility > > > > > > Hi Derek, > > > > > > did u get a chance to look into this issue that I am running in? > > > > > > Regards, > > > > I will check next week, I do not have time today. > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 11, 2011 6:49 AM > > > > To: advanced-graphics > > > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > > > Pterm > > > > Utility > > > > > > > > Derek, I found the img_decode_simple app. I followed the > procedures > > > > mentioned on the QNX website link "working with images". I edited > > the > > > > img.conf file to have the entries for JPEG and BMP only. Added the > > > > img_decode_simple binary into the target as well as added the > > jpg/bmp > > > > files for the drawing. I added this line : > > > > > > > > img_decode_simple my.jpg > > > > > > > > into the build script so that it starts the drawing as soon as > > > > photon/io-display/io-graphics starts up and running. However, I am > > > > getting this error > > > > > > > > gf_setup() failed with error 8 which means there is something > wrong > > > with > > > > the format. > > > > > > > > My display resolution is 240x320 and I am trying with images > > > > (125x94/300x282 as I couldn't find the image with exact 240x320 > > > > resolution). > > > > > > > > Do you know what is wrong? > > > > > > > > regarding the hybrid apps that you shared, I am not able see > > anything > > > on > > > > the LCD panel after running gf-ph-2d & gf-ph-3d app. > > > > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such > > > process" > > > > and > > > > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > > > > > > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > > > > moving with some text on the top as well. > > > > > > > > Please tell what is wrong I am doing. > > > > > > > > Regards, > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post83110 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83129 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83149 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83152 Tue, 15 Feb 2011 02:38:54 GMT http://community.qnx.com/sf/go/post83163 Raj Pandey 2011-02-15T02:38:54Z http://community.qnx.com/sf/go/post83157 Takshi Pandey wrote: > Thanks Armin and sorry for the late response. > Can you point me to any bsp which has the reference of SDL? > How do I add this SDL into my bsp? How am I going to link my bsp with this SDL? The SDL project (http://www.libsdl.org ) isn't part of any BSP ... but it is applicable with a QNX BSP if Photon is available. Since version 0.8 exists support for Linux and ARM ... so it's not rocket science to bring it down to QNX 6.x. and ARM. > And the last question. If I don't have SDL how am I seeing the images or able to play the demo apps presently? There are a lot of demos at http://www.libsdl.org ... --Armin > Regards, > >> Takshi Pandey wrote: >>> I could run the 2D demo app VSYNC and it is running fine. Although, I need >> to slay the Photon app for this VSYNC to run coz it goes and attach to the >> same layer that Photon runs on otherwise fails saying layer attach failed. >>> I could not see (~/src/video/photon/SDL_ph_video.c ) in my entire project >> and thats what is surprising me how the display is working. >> >> OK ... Photon is available. So download the sources of SDL 1.3 and >> recompile it and you will get a "frame buffer" >> >> --Armin >> >>> I am working with OS QNX6.5. >>> >>> Regards, >>> >>>> Takshi Pandey wrote: >>>>> Thanks Armin for the reply. The link that you shared seems that SDL takes >>>> care of everything as far as playing Audio/Video is concern. But I somehow >>>> could not relate this to the devg-xxx.so display driver. I could not see >> any >>>> references to SDL libraries in the display driver. >>>>> The surprising this is that I could see something on the OMAP2430 LCD >> panel >>>> (running a simple demo app) despite not seeing any references to SDL in my >>>> display driver. >>>>> My question are : >>>>> 1) From where the display driver is rendering the image? >>>> SDL is using low level calls of the Photon API in order to create >>>> something like a frame buffer interface. >>>> (~/src/video/photon/SDL_ph_video.c ) >>>> >>>> Doesn't the BSP of the OMAP2430 support Photon ? >>>> >>>> --Armin >>>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Advanced Graphics >>> http://community.qnx.com/sf/go/post83135 >>> >>> > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83153 > > Mon, 14 Feb 2011 21:50:41 GMT http://community.qnx.com/sf/go/post83157 Armin Steinhoff 2011-02-14T21:50:41Z http://community.qnx.com/sf/go/post83155 I still do not understand what you are trying to accomplish ... You talk of a "frame buffer" ... do you mean the actual display memory for the layer, or something else? If you are already displaying application, GF and Photon, then you are using the "frame buffer". If not, what will you use this "frame buffer" for? -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 14, 2011 12:43 PM To: advanced-graphics Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility Thanks for the reply Derek. I did the porting of display driver in WindowsCE 6.0 as well. As per the TRM we could allocate a region of physical memory from SRAM/SDRAM and I just mapped the SDRAM area for the frame buffer. I am not aware of any video decoder in omap2430. From all the discussions/forum I know that Frame buffer is a memory region which must be continuous. But just couldn't relate this with my devg code or build file. As per Armin he says we need to include SDL libraries which takes care of the frame buffer in QNX but I have not seen any reference of it in my bsp. Regards, > Derek, no need for you to spend your time on img_decode_simple issue. > Just got that stuff working today. I slayed the Photon app and then run > "img_decode_simple my.jpg" and I was able to draw the image on the LCD > panel. > I just saw another thread inquiring about the FRAME BUFFER concept in > QNX display driver. > This one thing is baffling me as well. Although I can do almost > everything with my display driver ,i.e, draw images, run 2D/3D demo > apps. The only thing pending is playing a video. > > DL: Yes, you cannot run img_decode_simple (GF application) on the same > layer that Photon is working, glad you figured it out OK. > > Just wanted to know where are we defining the memory for the frame > buffer. Is it the one in build file, the parameters we pass to the start > up script like omap3530 -L 0x87E00000 0x00020000 ? > I haven't see any reference of frame buffer in the devg code. > > The other thing is do we have any test code to test our driver > thoroughly? > > DL: Do you have a video decoder on your board? Does it present to a > physical address? frame buffer is just a region of memory. > > I would appreciate the reply. > > Regards > > > not yet, I just got to work. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 13, 2011 9:29 PM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > > Pterm Utility > > > > Hi Derek, > > > > did u get a chance to look into this issue that I am running in? > > > > Regards, > > > I will check next week, I do not have time today. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 11, 2011 6:49 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > > Pterm > > > Utility > > > > > > Derek, I found the img_decode_simple app. I followed the procedures > > > mentioned on the QNX website link "working with images". I edited > the > > > img.conf file to have the entries for JPEG and BMP only. Added the > > > img_decode_simple binary into the target as well as added the > jpg/bmp > > > files for the drawing. I added this line : > > > > > > img_decode_simple my.jpg > > > > > > into the build script so that it starts the drawing as soon as > > > photon/io-display/io-graphics starts up and running. However, I am > > > getting this error > > > > > > gf_setup() failed with error 8 which means there is something wrong > > with > > > the format. > > > > > > My display resolution is 240x320 and I am trying with images > > > (125x94/300x282 as I couldn't find the image with exact 240x320 > > > resolution). > > > > > > Do you know what is wrong? > > > > > > regarding the hybrid apps that you shared, I am not able see > anything > > on > > > the LCD panel after running gf-ph-2d & gf-ph-3d app. > > > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such > > process" > > > and > > > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > > > > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > > > moving with some text on the top as well. > > > > > > Please tell what is wrong I am doing. > > > > > > Regards, > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83110 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83129 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83149 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83152 Mon, 14 Feb 2011 18:36:06 GMT http://community.qnx.com/sf/go/post83155 Derek Leach 2011-02-14T18:36:06Z http://community.qnx.com/sf/go/post83153 Thanks Armin and sorry for the late response. Can you point me to any bsp which has the reference of SDL? How do I add this SDL into my bsp? How am I going to link my bsp with this SDL? And the last question. If I don't have SDL how am I seeing the images or able to play the demo apps presently? Regards, > Takshi Pandey wrote: > > I could run the 2D demo app VSYNC and it is running fine. Although, I need > to slay the Photon app for this VSYNC to run coz it goes and attach to the > same layer that Photon runs on otherwise fails saying layer attach failed. > > I could not see (~/src/video/photon/SDL_ph_video.c ) in my entire project > and thats what is surprising me how the display is working. > > OK ... Photon is available. So download the sources of SDL 1.3 and > recompile it and you will get a "frame buffer" > > --Armin > > > I am working with OS QNX6.5. > > > > Regards, > > > >> Takshi Pandey wrote: > >>> Thanks Armin for the reply. The link that you shared seems that SDL takes > >> care of everything as far as playing Audio/Video is concern. But I somehow > >> could not relate this to the devg-xxx.so display driver. I could not see > any > >> references to SDL libraries in the display driver. > >>> The surprising this is that I could see something on the OMAP2430 LCD > panel > >> (running a simple demo app) despite not seeing any references to SDL in my > >> display driver. > >>> My question are : > >>> 1) From where the display driver is rendering the image? > >> SDL is using low level calls of the Photon API in order to create > >> something like a frame buffer interface. > >> (~/src/video/photon/SDL_ph_video.c ) > >> > >> Doesn't the BSP of the OMAP2430 support Photon ? > >> > >> --Armin > >> > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83135 > > > > Mon, 14 Feb 2011 17:47:04 GMT http://community.qnx.com/sf/go/post83153 Takshi Pandey 2011-02-14T17:47:04Z http://community.qnx.com/sf/go/post83152 Thanks for the reply Derek. I did the porting of display driver in WindowsCE 6.0 as well. As per the TRM we could allocate a region of physical memory from SRAM/SDRAM and I just mapped the SDRAM area for the frame buffer. I am not aware of any video decoder in omap2430. From all the discussions/forum I know that Frame buffer is a memory region which must be continuous. But just couldn't relate this with my devg code or build file. As per Armin he says we need to include SDL libraries which takes care of the frame buffer in QNX but I have not seen any reference of it in my bsp. Regards, > Derek, no need for you to spend your time on img_decode_simple issue. > Just got that stuff working today. I slayed the Photon app and then run > "img_decode_simple my.jpg" and I was able to draw the image on the LCD > panel. > I just saw another thread inquiring about the FRAME BUFFER concept in > QNX display driver. > This one thing is baffling me as well. Although I can do almost > everything with my display driver ,i.e, draw images, run 2D/3D demo > apps. The only thing pending is playing a video. > > DL: Yes, you cannot run img_decode_simple (GF application) on the same > layer that Photon is working, glad you figured it out OK. > > Just wanted to know where are we defining the memory for the frame > buffer. Is it the one in build file, the parameters we pass to the start > up script like omap3530 -L 0x87E00000 0x00020000 ? > I haven't see any reference of frame buffer in the devg code. > > The other thing is do we have any test code to test our driver > thoroughly? > > DL: Do you have a video decoder on your board? Does it present to a > physical address? frame buffer is just a region of memory. > > I would appreciate the reply. > > Regards > > > not yet, I just got to work. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 13, 2011 9:29 PM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > > Pterm Utility > > > > Hi Derek, > > > > did u get a chance to look into this issue that I am running in? > > > > Regards, > > > I will check next week, I do not have time today. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 11, 2011 6:49 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > > Pterm > > > Utility > > > > > > Derek, I found the img_decode_simple app. I followed the procedures > > > mentioned on the QNX website link "working with images". I edited > the > > > img.conf file to have the entries for JPEG and BMP only. Added the > > > img_decode_simple binary into the target as well as added the > jpg/bmp > > > files for the drawing. I added this line : > > > > > > img_decode_simple my.jpg > > > > > > into the build script so that it starts the drawing as soon as > > > photon/io-display/io-graphics starts up and running. However, I am > > > getting this error > > > > > > gf_setup() failed with error 8 which means there is something wrong > > with > > > the format. > > > > > > My display resolution is 240x320 and I am trying with images > > > (125x94/300x282 as I couldn't find the image with exact 240x320 > > > resolution). > > > > > > Do you know what is wrong? > > > > > > regarding the hybrid apps that you shared, I am not able see > anything > > on > > > the LCD panel after running gf-ph-2d & gf-ph-3d app. > > > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such > > process" > > > and > > > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > > > > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > > > moving with some text on the top as well. > > > > > > Please tell what is wrong I am doing. > > > > > > Regards, > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83110 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83129 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83149 Mon, 14 Feb 2011 17:42:30 GMT http://community.qnx.com/sf/go/post83152 Raj Pandey 2011-02-14T17:42:30Z http://community.qnx.com/sf/go/post83151 Derek, no need for you to spend your time on img_decode_simple issue. Just got that stuff working today. I slayed the Photon app and then run "img_decode_simple my.jpg" and I was able to draw the image on the LCD panel. I just saw another thread inquiring about the FRAME BUFFER concept in QNX display driver. This one thing is baffling me as well. Although I can do almost everything with my display driver ,i.e, draw images, run 2D/3D demo apps. The only thing pending is playing a video. DL: Yes, you cannot run img_decode_simple (GF application) on the same layer that Photon is working, glad you figured it out OK. Just wanted to know where are we defining the memory for the frame buffer. Is it the one in build file, the parameters we pass to the start up script like omap3530 -L 0x87E00000 0x00020000 ? I haven't see any reference of frame buffer in the devg code. The other thing is do we have any test code to test our driver thoroughly? DL: Do you have a video decoder on your board? Does it present to a physical address? frame buffer is just a region of memory. I would appreciate the reply. Regards > not yet, I just got to work. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 13, 2011 9:29 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > Pterm Utility > > Hi Derek, > > did u get a chance to look into this issue that I am running in? > > Regards, > > I will check next week, I do not have time today. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 11, 2011 6:49 AM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > Pterm > > Utility > > > > Derek, I found the img_decode_simple app. I followed the procedures > > mentioned on the QNX website link "working with images". I edited the > > img.conf file to have the entries for JPEG and BMP only. Added the > > img_decode_simple binary into the target as well as added the jpg/bmp > > files for the drawing. I added this line : > > > > img_decode_simple my.jpg > > > > into the build script so that it starts the drawing as soon as > > photon/io-display/io-graphics starts up and running. However, I am > > getting this error > > > > gf_setup() failed with error 8 which means there is something wrong > with > > the format. > > > > My display resolution is 240x320 and I am trying with images > > (125x94/300x282 as I couldn't find the image with exact 240x320 > > resolution). > > > > Do you know what is wrong? > > > > regarding the hybrid apps that you shared, I am not able see anything > on > > the LCD panel after running gf-ph-2d & gf-ph-3d app. > > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such > process" > > and > > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > > moving with some text on the top as well. > > > > Please tell what is wrong I am doing. > > > > Regards, > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83110 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83129 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83149 Mon, 14 Feb 2011 16:57:23 GMT http://community.qnx.com/sf/go/post83151 Derek Leach 2011-02-14T16:57:23Z http://community.qnx.com/sf/go/post83149 Derek, no need for you to spend your time on img_decode_simple issue. Just got that stuff working today. I slayed the Photon app and then run "img_decode_simple my.jpg" and I was able to draw the image on the LCD panel. I just saw another thread inquiring about the FRAME BUFFER concept in QNX display driver. This one thing is baffling me as well. Although I can do almost everything with my display driver ,i.e, draw images, run 2D/3D demo apps. The only thing pending is playing a video. Just wanted to know where are we defining the memory for the frame buffer. Is it the one in build file, the parameters we pass to the start up script like omap3530 -L 0x87E00000 0x00020000 ? I haven't see any reference of frame buffer in the devg code. The other thing is do we have any test code to test our driver thoroughly? I would appreciate the reply. Regards > not yet, I just got to work. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 13, 2011 9:29 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > Pterm Utility > > Hi Derek, > > did u get a chance to look into this issue that I am running in? > > Regards, > > I will check next week, I do not have time today. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 11, 2011 6:49 AM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after > Pterm > > Utility > > > > Derek, I found the img_decode_simple app. I followed the procedures > > mentioned on the QNX website link "working with images". I edited the > > img.conf file to have the entries for JPEG and BMP only. Added the > > img_decode_simple binary into the target as well as added the jpg/bmp > > files for the drawing. I added this line : > > > > img_decode_simple my.jpg > > > > into the build script so that it starts the drawing as soon as > > photon/io-display/io-graphics starts up and running. However, I am > > getting this error > > > > gf_setup() failed with error 8 which means there is something wrong > with > > the format. > > > > My display resolution is 240x320 and I am trying with images > > (125x94/300x282 as I couldn't find the image with exact 240x320 > > resolution). > > > > Do you know what is wrong? > > > > regarding the hybrid apps that you shared, I am not able see anything > on > > the LCD panel after running gf-ph-2d & gf-ph-3d app. > > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such > process" > > and > > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > > moving with some text on the top as well. > > > > Please tell what is wrong I am doing. > > > > Regards, > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83110 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83129 Mon, 14 Feb 2011 16:12:53 GMT http://community.qnx.com/sf/go/post83149 Raj Pandey 2011-02-14T16:12:53Z http://community.qnx.com/sf/go/post83140 not yet, I just got to work. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 13, 2011 9:29 PM To: advanced-graphics Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility Hi Derek, did u get a chance to look into this issue that I am running in? Regards, > I will check next week, I do not have time today. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 11, 2011 6:49 AM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm > Utility > > Derek, I found the img_decode_simple app. I followed the procedures > mentioned on the QNX website link "working with images". I edited the > img.conf file to have the entries for JPEG and BMP only. Added the > img_decode_simple binary into the target as well as added the jpg/bmp > files for the drawing. I added this line : > > img_decode_simple my.jpg > > into the build script so that it starts the drawing as soon as > photon/io-display/io-graphics starts up and running. However, I am > getting this error > > gf_setup() failed with error 8 which means there is something wrong with > the format. > > My display resolution is 240x320 and I am trying with images > (125x94/300x282 as I couldn't find the image with exact 240x320 > resolution). > > Do you know what is wrong? > > regarding the hybrid apps that you shared, I am not able see anything on > the LCD panel after running gf-ph-2d & gf-ph-3d app. > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such process" > and > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > moving with some text on the top as well. > > Please tell what is wrong I am doing. > > Regards, > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83110 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83129 Mon, 14 Feb 2011 13:23:37 GMT http://community.qnx.com/sf/go/post83140 Derek Leach 2011-02-14T13:23:37Z http://community.qnx.com/sf/go/post83136 Takshi Pandey wrote: > I could run the 2D demo app VSYNC and it is running fine. Although, I need to slay the Photon app for this VSYNC to run coz it goes and attach to the same layer that Photon runs on otherwise fails saying layer attach failed. > I could not see (~/src/video/photon/SDL_ph_video.c ) in my entire project and thats what is surprising me how the display is working. OK ... Photon is available. So download the sources of SDL 1.3 and recompile it and you will get a "frame buffer" --Armin > I am working with OS QNX6.5. > > Regards, > >> Takshi Pandey wrote: >>> Thanks Armin for the reply. The link that you shared seems that SDL takes >> care of everything as far as playing Audio/Video is concern. But I somehow >> could not relate this to the devg-xxx.so display driver. I could not see any >> references to SDL libraries in the display driver. >>> The surprising this is that I could see something on the OMAP2430 LCD panel >> (running a simple demo app) despite not seeing any references to SDL in my >> display driver. >>> My question are : >>> 1) From where the display driver is rendering the image? >> SDL is using low level calls of the Photon API in order to create >> something like a frame buffer interface. >> (~/src/video/photon/SDL_ph_video.c ) >> >> Doesn't the BSP of the OMAP2430 support Photon ? >> >> --Armin >> > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83135 > > Mon, 14 Feb 2011 11:49:05 GMT http://community.qnx.com/sf/go/post83136 Armin Steinhoff 2011-02-14T11:49:05Z http://community.qnx.com/sf/go/post83135 I could run the 2D demo app VSYNC and it is running fine. Although, I need to slay the Photon app for this VSYNC to run coz it goes and attach to the same layer that Photon runs on otherwise fails saying layer attach failed. I could not see (~/src/video/photon/SDL_ph_video.c ) in my entire project and thats what is surprising me how the display is working. I am working with OS QNX6.5. Regards, > Takshi Pandey wrote: > > Thanks Armin for the reply. The link that you shared seems that SDL takes > care of everything as far as playing Audio/Video is concern. But I somehow > could not relate this to the devg-xxx.so display driver. I could not see any > references to SDL libraries in the display driver. > > The surprising this is that I could see something on the OMAP2430 LCD panel > (running a simple demo app) despite not seeing any references to SDL in my > display driver. > > My question are : > > 1) From where the display driver is rendering the image? > > SDL is using low level calls of the Photon API in order to create > something like a frame buffer interface. > (~/src/video/photon/SDL_ph_video.c ) > > Doesn't the BSP of the OMAP2430 support Photon ? > > --Armin > Mon, 14 Feb 2011 08:49:50 GMT http://community.qnx.com/sf/go/post83135 Takshi Pandey 2011-02-14T08:49:50Z http://community.qnx.com/sf/go/post83134 Takshi Pandey wrote: > Thanks Armin for the reply. The link that you shared seems that SDL takes care of everything as far as playing Audio/Video is concern. But I somehow could not relate this to the devg-xxx.so display driver. I could not see any references to SDL libraries in the display driver. > The surprising this is that I could see something on the OMAP2430 LCD panel (running a simple demo app) despite not seeing any references to SDL in my display driver. > My question are : > 1) From where the display driver is rendering the image? SDL is using low level calls of the Photon API in order to create something like a frame buffer interface. (~/src/video/photon/SDL_ph_video.c ) Doesn't the BSP of the OMAP2430 support Photon ? --Armin Mon, 14 Feb 2011 08:07:20 GMT http://community.qnx.com/sf/go/post83134 Armin Steinhoff 2011-02-14T08:07:20Z http://community.qnx.com/sf/go/post83131 Thanks Armin for the reply. The link that you shared seems that SDL takes care of everything as far as playing Audio/Video is concern. But I somehow could not relate this to the devg-xxx.so display driver. I could not see any references to SDL libraries in the display driver. The surprising this is that I could see something on the OMAP2430 LCD panel (running a simple demo app) despite not seeing any references to SDL in my display driver. My question are : 1) From where the display driver is rendering the image? 2) What part of the display driver code is responsible for this? 3) How should we link to SDL library in order to get the Framebuffer for the image rendering? 4) Where is the code which is mapping the physical memory for the frame buffer in devg-driver? regards, > Takshi Pandey wrote: > > Hi Experts, > > > > Is there any frame buffer concept in QNX for display driver. I am working on > porting display driver on omap2430. I couldn't find any omap2430 bsp on the > website. I looked at the IMX21 bsp. It has the display driver reference in > devg folder. I kind of got the idea how display driver is populating function > pointer in DISP_ADD_FUNCTION and some of them are implemented in them, but I > couldn't see any code where it is mapping a memory from SRAM/SDRAM as part of > frame buffer. I saw the config file imx21.conf as well but could not the see > the reference of memory as frame buffer. > > > > Do we have framebuffer concept in QNX? > > http://community.qnx.com/sf/projects/qnx_community_sdl_project/ > > --Armin > > http://www.steinhoff-automation.com > > > How is the display driver rendering the image on the LCD panel? > > > > I would appreciate the reply. I am using QNX6.5. > > > > Regards > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83127 > > > > Mon, 14 Feb 2011 04:12:16 GMT http://community.qnx.com/sf/go/post83131 Takshi Pandey 2011-02-14T04:12:16Z http://community.qnx.com/sf/go/post83129 Hi Derek, did u get a chance to look into this issue that I am running in? Regards, > I will check next week, I do not have time today. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 11, 2011 6:49 AM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm > Utility > > Derek, I found the img_decode_simple app. I followed the procedures > mentioned on the QNX website link "working with images". I edited the > img.conf file to have the entries for JPEG and BMP only. Added the > img_decode_simple binary into the target as well as added the jpg/bmp > files for the drawing. I added this line : > > img_decode_simple my.jpg > > into the build script so that it starts the drawing as soon as > photon/io-display/io-graphics starts up and running. However, I am > getting this error > > gf_setup() failed with error 8 which means there is something wrong with > the format. > > My display resolution is 240x320 and I am trying with images > (125x94/300x282 as I couldn't find the image with exact 240x320 > resolution). > > Do you know what is wrong? > > regarding the hybrid apps that you shared, I am not able see anything on > the LCD panel after running gf-ph-2d & gf-ph-3d app. > gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such process" > and > gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". > > But the gf-gl_pg_demo app runs perfectly and I could see the gears > moving with some text on the top as well. > > Please tell what is wrong I am doing. > > Regards, > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83110 Mon, 14 Feb 2011 02:28:58 GMT http://community.qnx.com/sf/go/post83129 Raj Pandey 2011-02-14T02:28:58Z http://community.qnx.com/sf/go/post83128 Takshi Pandey wrote: > Hi Experts, > > Is there any frame buffer concept in QNX for display driver. I am working on porting display driver on omap2430. I couldn't find any omap2430 bsp on the website. I looked at the IMX21 bsp. It has the display driver reference in devg folder. I kind of got the idea how display driver is populating function pointer in DISP_ADD_FUNCTION and some of them are implemented in them, but I couldn't see any code where it is mapping a memory from SRAM/SDRAM as part of frame buffer. I saw the config file imx21.conf as well but could not the see the reference of memory as frame buffer. > > Do we have framebuffer concept in QNX? http://community.qnx.com/sf/projects/qnx_community_sdl_project/ --Armin http://www.steinhoff-automation.com > How is the display driver rendering the image on the LCD panel? > > I would appreciate the reply. I am using QNX6.5. > > Regards > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83127 > > Sun, 13 Feb 2011 19:26:35 GMT http://community.qnx.com/sf/go/post83128 Armin Steinhoff 2011-02-13T19:26:35Z http://community.qnx.com/sf/go/post83127 Hi Experts, Is there any frame buffer concept in QNX for display driver. I am working on porting display driver on omap2430. I couldn't find any omap2430 bsp on the website. I looked at the IMX21 bsp. It has the display driver reference in devg folder. I kind of got the idea how display driver is populating function pointer in DISP_ADD_FUNCTION and some of them are implemented in them, but I couldn't see any code where it is mapping a memory from SRAM/SDRAM as part of frame buffer. I saw the config file imx21.conf as well but could not the see the reference of memory as frame buffer. Do we have framebuffer concept in QNX? How is the display driver rendering the image on the LCD panel? I would appreciate the reply. I am using QNX6.5. Regards Sun, 13 Feb 2011 17:34:42 GMT http://community.qnx.com/sf/go/post83127 Takshi Pandey 2011-02-13T17:34:42Z http://community.qnx.com/sf/go/post83111 I will check next week, I do not have time today. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 11, 2011 6:49 AM To: advanced-graphics Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility Derek, I found the img_decode_simple app. I followed the procedures mentioned on the QNX website link "working with images". I edited the img.conf file to have the entries for JPEG and BMP only. Added the img_decode_simple binary into the target as well as added the jpg/bmp files for the drawing. I added this line : img_decode_simple my.jpg into the build script so that it starts the drawing as soon as photon/io-display/io-graphics starts up and running. However, I am getting this error gf_setup() failed with error 8 which means there is something wrong with the format. My display resolution is 240x320 and I am trying with images (125x94/300x282 as I couldn't find the image with exact 240x320 resolution). Do you know what is wrong? regarding the hybrid apps that you shared, I am not able see anything on the LCD panel after running gf-ph-2d & gf-ph-3d app. gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such process" and gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". But the gf-gl_pg_demo app runs perfectly and I could see the gears moving with some text on the top as well. Please tell what is wrong I am doing. Regards, _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83110 Fri, 11 Feb 2011 14:52:16 GMT http://community.qnx.com/sf/go/post83111 Derek Leach 2011-02-11T14:52:16Z http://community.qnx.com/sf/go/post83110 Derek, I found the img_decode_simple app. I followed the procedures mentioned on the QNX website link "working with images". I edited the img.conf file to have the entries for JPEG and BMP only. Added the img_decode_simple binary into the target as well as added the jpg/bmp files for the drawing. I added this line : img_decode_simple my.jpg into the build script so that it starts the drawing as soon as photon/io-display/io-graphics starts up and running. However, I am getting this error gf_setup() failed with error 8 which means there is something wrong with the format. My display resolution is 240x320 and I am trying with images (125x94/300x282 as I couldn't find the image with exact 240x320 resolution). Do you know what is wrong? regarding the hybrid apps that you shared, I am not able see anything on the LCD panel after running gf-ph-2d & gf-ph-3d app. gf-ph-2d complains about "PdCreateOffscreenContextGF(): No such process" and gf-ph-3d complains saying "PdCreateOffscreenContextGF(): failed". But the gf-gl_pg_demo app runs perfectly and I could see the gears moving with some text on the top as well. Please tell what is wrong I am doing. Regards, Fri, 11 Feb 2011 11:49:10 GMT http://community.qnx.com/sf/go/post83110 Raj Pandey 2011-02-11T11:49:10Z http://community.qnx.com/sf/go/post83099 Thanks. It means Photon is running OK. I guess I got the idea of running the app in access group. Is it that we need to put the gf-ph-2d app in the build file under the display driver group where all the other default apps like, vsync, pterm, egl-gears are? I am definitely not talking about the source code of img_decode_simple. I'll just check if we have this under /usr/bin folder. Thanks again Derek. Very much appreciated your help. Regards, Raj > If you can see your pterm, it is running OK. > > Yes, GF apps need root priviledge, or you need to set up an access > group, see the documentation for io-display. > > The binary for img_decode_simple should be shipped, under /usr/bin, or > do you mean the source? > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 10, 2011 12:42 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm > Utility > > I guess Photon is running alright. All I see is a window with some color > on LCD panel along with a command prompt terminal just like a serial > console. What will be the best way to check if the Photon is running > perfectly? > Also, how do I run all the GF apps with root privilage? > > Derek, my 2nd question was do I really need "img_decode_simple" utility > to draw a bmp/jpg/gif image? If yes then how do I get it? > > Regards, > Raj > > ok, Photon is running, correct? Are you running it as root? By > > default, all GF applications must run as root user. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 10, 2011 12:18 PM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm > Utility > > > > You are right Derek, there is no call to attach with any layer in the > > gf-ph-2d code. > > So, what went wrong. Why I can't see the gf-ph-2d app running? > > > > Do you suspect anything wrong with my settings? Be it > > display.conf/omap35xx.conf or the build file. I need to mention one > > thing that I added layer=0 entry in the photon part of the > display.conf > > file. > > > > Regards, > > Raj > > > > > Is there any gf_layer_attach calls in the gf-ph-2d code? I don't > > > believe it attaches directly to any layer ... > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 10, 2011 11:51 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > Thanks Derek. > > > > > > Primarily we would have liked to do this during startup but now we > > > abandon the idea. Now we want to do it once the Photon is up and > > display > > > driver is running. > > > I am assuming Photon is running on the main layer, layer=0. I tried > > with > > > the hybrid app that you shared yesterday but could not see any thing > > on > > > the LCD panel. Looking at the log it seems the GF app is trying to > run > > > on the layer=1. Pasting excerpt from the log after launching > > "gf-ph-2d" > > > app. > > > > > > ================================================ > > > # gf-ph-2d > > > Raw Widget: width = 235, height = 166 > > > +devg_get_miscfuncs > > > -devg_get_miscfuncs > > > omap_module_info TI OMAP 35xx display Controller > > > omap_alloc_surface ++ > > > omap_get_alloc_info ++ > > > **************PdCreateOffscreenContextGF(): No such process > > > omap_layer_update_begin ++ > > > omap_layer_set_surface ++ > > > DISP_LAYER_FORMAT_RGB565 > > > omap_layer_set_surface -- > > > omap_layer_update_end ++ > > > omap_layer_program ++ > > > Video layer1 no scaling widthomap_layer_program > > > OMAP_LAYER_VID1 > > > omap_layer_program -- > > > omap_layer_update_end -- > > > > > > ================================================ > > > > > > demarked the error text in the log. Why I got this error? > > > > > > the sloginfo is : > > > > > > ======================== > > > > > > # sloginfo > > > Time Sev Major Minor Args > > > Jan 01 00:00:09 1 8 0 phfont.so: init... > > > Jan 01 00:00:09 1 8 0 phfont.so: initialized. > > > Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' > > > server installed. > > > Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode > > > Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing > > > Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no > > > more layers, maybe end of layer query) > > > Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 > > > Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 > > > ======================== > > > If my assumptions are right, by default photon starts on > layer=0(GFX), > > > any 2D app starts on layer=1(Video1) and 3D starts on > layer=2(Video2). > > > > > > I was trying to display one JPEG image on the LCD panel and reading > > > through the QNX docs I got to know that I will need > > "img_decode_simple" > > > to draw the image. I do have libimg.so in my image and do see the > > > entries for various image formats in img.conf file. > > > > > > Right now, I do not have "img_decode_simple" utility and I heard it > > > comes with Advanced Graphics. > > > How do I get this utility to draw some image on the LCD panel. I > would > > > appreciate if you can clarify few of my doubts. > > > > > > Regards, > > > Raj > > > > > > > Depends how soon you want it to come up ... do you want it > > immediate, > > > or > > > > once io-display is running, or is it OK to wait until Photon is > > > booted? > > > > > > > > Immediate is much more difficult. > > > > > > > > If once io-display is running, just run a GF application on a > layer > > > that > > > > is behind the layer that Photon will use (if you have more than > one > > > > layer). You can slay it off later. > > > > > > > > If after Photon has booted, just run you Photon application before > > any > > > > other Photon applications. > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 9, 2011 12:20 PM > > > > To: advanced-graphics > > > > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > > > Thanks Again Derek for the reply. Appreciated it very much. I'll > > work > > > on > > > > hybrid application tomorrow. > > > > Is there a way to display QNX homescreen like all the other OS > does > > > ,e.g > > > > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > > > > during/after boot up? > > > > > > > > Regards, > > > > Raj > > > > > Ok, you will need to run it on a different layer than Photon, or > > > turn > > > > > your application into a Photon/GF hybrid application. Examples > of > > > > > hybrid applications can be found at: > > > > > > > > > > > > > > > > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > > > > ton.gf_ph_2d > > > > > > > > > > -----Original Message----- > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > Sent: February 9, 2011 11:37 AM > > > > > To: advanced-graphics > > > > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > > > > > Thanks for the reply Derek. It is a GF application and not the > > > Photon > > > > > one. > > > > > > > > > > > Is this rectangle application a GF or a Photon application? > > > > > > > > > > > > No, there is no need to run it from pterm. > > > > > > > > > > > > -----Original Message----- > > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > > Sent: February 9, 2011 8:49 AM > > > > > > To: advanced-graphics > > > > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > > > > > > > I got the Pterm working. I ran the Pterm in background and I > > could > > > > see > > > > > > the blinking cursor and I can type the commands in serial > > > terminal. > > > > > > > > > > > > I created one simple app to draw a rectangle and I am trying > to > > > > launch > > > > > > this app from the serial terminal and not the Pterm. I have > put > > > that > > > > > > application in /src/utils/ folder. The application is there in > > the > > > > > > image. > > > > > > > > > > > > I have two question regarding this. > > > > > > > > > > > > i) Do I need to launch the app from the Pterm? > > > > > > If yes, then I will need an input driver. > > > > > > > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > > > > > > > I tried doing it but it doesn't draw the rectangle. > > > > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno > 1. > > > > > > > > > > > > Does anybody know why I got this error? I would appreciate the > > > > reply. > > > > > > > > > > > > Note: > > > > > > I could draw the rectangle by typing following command on > pterm > > > > "pterm > > > > > > -x10 -y10 -height100 -width100". > > > > > > > > > > > > One final question. Is there a way to display the QNX home > > screen > > > on > > > > > the > > > > > > LCD panel? If yes, then how? > > > > > > > > > > > > Regards, > > > > > > > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## START OF BUILD SCRIPT > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > > > > > > > > [image=0x80010000] > > > > > > > [+compress] > > > > > > > #[virtual=armle,binary] .bootstrap = { > > > > > > > [virtual=armle,raw] .bootstrap = { > > > > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## PATH set here is the *safe* path for executables. > > > > > > > ## LD_LIBRARY_PATH set here is the *safe* path for > > > libraries. > > > > > > > ## i.e. These are the paths searched by > > > setuid/setgid > > > > > > binaries. > > > > > > > ## (confstr(_CS_PATH...) and > > > confstr(_CS_LIBPATH...)) > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon > > > PHFONT=/dev/phfont > > > > > > procnto-v6 > > > > > > > } > > > > > > > [+script] .script = { > > > > > > > procmgr_symlink ../../proc/boot/libc.so.3 > > > /usr/lib/ldqnx.so.2 > > > > > > > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > > > > Instruments > > > > > > > OMAP2430SDP Board > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## SERIAL driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > > > > waitfor /dev/ser1 4 > > > > > > > reopen /dev/ser1 > > > > > > > > > > > > > > slogger > > > > > > > pipe > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## NAND_ETFS driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > #display_msg Starting etfs driver... > > > > > > > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## NETWORK driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > # > > > > > > > #display_msg Starting on-board ethernet with TCP/IP > > > stack... > > > > > > > # > > > > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > > > > # > > > > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## I2C driver > > > > > > > ## - Required for both USB and AUDIO > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > display_msg Starting I2C driver... > > > > > > > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## USB driver > > > > > > > ## - Requires the I2C driver to be running > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > #display_msg Starting USB stack... > > > > > > > > > > > > > > #omap2420sdp_usb_init > > > > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## input > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## These env variables are inherited by all the programs > > > which > > > > > > follow > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > SYSNAME=nto > > > > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > > > > PHOTON_PATH=/usr/photon > > > > > > > PHOTON=/dev/photon > > > > > > > PHFONT=/dev/phfont > > > > > > > TERM=qansi > > > > > > > HOME=/ > > > > > > > > > > > > > > > > > > > > > > > > > > ###################################################################### > > > > > > > # > > > > > > > ## GRAPHICS > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > display_msg Starting io-display... > > > > > > > > > > > > > > io-display -dvid=0,did=0 > > > > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## Photon and Phfont > > > > > > > ## - NOTE: Photon and phfont MUST be started before the > > > GRAPHICS > > > > > > driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > display_msg Starting Photon... > > > > > > > Photon & > > > > > > > waitfor /dev/photon 10 > > > > > > > display_msg Starting Phfont... > > > > > > > Phfont & > > > > > > > waitfor /proc/boot/phfont 10 > > > > > > > display_msg Starting io-graphics... > > > > > > > io-graphics > > > > > > > display_msg Starting PWM... > > > > > > > pwm & > > > > > > > display_msg Starting DEVC-PTY... > > > > > > > devc-pty & > > > > > > > display_msg Starting PTERM... > > > > > > > pterm > > > > > > > display_msg Starting BKGDMGR... > > > > > > > bkgdmgr > > > > > > > sloginfo > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > ## input > > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > > > > } > > > > > > > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > > > > [type=link] /dev/console=/dev/ser1 > > > > > > > [type=link] /tmp=/dev/shmem > > > > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > > > > earlier) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > #libc.so.2 > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for standard libs > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > libc.so > > > > > > > libm.so > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > libph.so > > > > > > > libAp.so > > > > > > > libphexlib.so > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > devg-omap35xx.so > > > > > > > libgf.so > > > > > > > libGLES_CM.so > > > > > > > libimg.so > > > > > > > gri-photon.so > > > > > > > libphrender.so > > > > > > > libgri.so > > > > > > > libdisputil.so > > > > > > > libffb.so > > > > > > > libgf.so.1 > > > > > > > libGLES_CL.so.1 > > > > > > > > > > > > > > > > > > > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > > > > ttings > > > > > > > > > > > > > > > > > > > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > > > > .pal > > > > > > > > > > > > > > > > > > > > > [data=c] > > > > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ## > > > > > > > ## font libs (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ## > > > > > > > devg-svga.so > > > > > > > /etc/system/config/omap35xx.conf = > > > > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > > > > /lib/dll/font/ttfFFcore.so = > > > > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > > > > /lib/dll/font/PHFcore.so = > > > > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > > > > /lib/dll/font/FCcore.so = > > > > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > > > > libfontharnessutils.so > > > > > > > libfontutils.so > > > > > > > libblkcache.so > > > > > > > libFF-T2K.so > > > > > > > libFF-T2K-cache.so > > > > > > > libFF-T2K-fm.so > > > > > > > libfont.so > > > > > > > phfont.so > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ## > > > > > > > ## font config (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ## > > > > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > > > > /usr/photon/font_repository/phcursor.phf = > > > > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > > > > /usr/photon/font_repository/mappings = > > > > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > > > > /usr/photon/font_repository/fontopts = > > > > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > > > > /usr/photon/font_repository/fontkey = > > > > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > > > > ; > > > > > > > ; fontdir config file > > > > > > > ; > > > > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > > > > BT,0,,0020-F002,f,79x170,109K > > > > > > > } > > > > > > > > > > > > > > /usr/photon/font_repository/fontext = { > > > > > > > ; > > > > > > > ; fontext config file > > > > > > > ; > > > > > > > +normal = primasansmonobts, phcursor > > > > > > > } > > > > > > > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > > > > [SANSERIF] > > > > > > > PrimaSansMono BT > > > > > > > } > > > > > > > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > > > > ; > > > > > > > ; fontmap config file > > > > > > > ; > > > > > > > ? = primasansmonobts > > > > > > > } > > > > > > > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > > > > =Desktop Menu > > > > > > > Terminal T pterm > > > > > > > Calculator C phcalc_sm > > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > devn-smc9000.so > > > > > > > libsocket.so > > > > > > > devnp-shim.so > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > libusbdi.so > > > > > > > devu-ohci.so > > > > > > > > > > > > > > ##################################### > > > > > > > #input driver > > > > > > > ###################################### > > > > > > > devi-omap_keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## Needed for Photon > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > devc-pty > > > > > > > ksh > > > > > > > slogger > > > > > > > sloginfo > > > > > > > Photon > > > > > > > io-graphics > > > > > > > io-display > > > > > > > devi-hirun > > > > > > > phfont > > > > > > > pwm > > > > > > > # photon applications required to be unstriped by mkifs, > hence > > > > these > > > > > > have > > > > > > > # +raw tag to tell mkifs not to strip them > > > > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > > > > > > > # allow pterm to save its configuration to RAM, if the user > > > > changes > > > > > > it. > > > > > > > [type=link] /.ph/pterm = /dev/shmem > > > > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for etfs driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > fs-etfs-omap2420 > > > > > > > etfsctl > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for I2C driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > i2c-omap59xx > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > io-pkt-v4 > > > > > > > nicinfo > > > > > > > ifconfig > > > > > > > ping > > > > > > > cat > > > > > > > fs-nfs2 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > io-usb > > > > > > > omap2420sdp_usb_init > > > > > > > usb > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## uncomment for Graphics driver > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > vsync > > > > > > > egl-gears-lite > > > > > > > io-display > > > > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > > > > /etc/system/config/display.conf={ > > > > > > > device \{ > > > > > > > drivername=omap35xx > > > > > > > vid=0 > > > > > > > did=0 > > > > > > > modeopts=/etc/system/config/omap35xx.conf > > > > > > > display \{ > > > > > > > xres=240 > > > > > > > yres=320 > > > > > > > refresh=60 > > > > > > > pixel_format=rgb565 > > > > > > > photon \{ > > > > > > > enabled=1 > > > > > > > xoffset=0 > > > > > > > yoffset=0 > > > > > > > cursor=software > > > > > > > input_group=1 > > > > > > > \} > > > > > > > > > > > > > > \} > > > > > > > \} > > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## general commands > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ls > > > > > > > ksh > > > > > > > pipe > > > > > > > pidin > > > > > > > uname > > > > > > > slogger > > > > > > > sloginfo > > > > > > > slay > > > > > > > cp > > > > > > > chmod > > > > > > > waitfor > > > > > > > shutdown > > > > > > > > > > > > > > ##i2c utility > > > > > > > i2c-reg > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > ## END OF BUILD SCRIPT > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > > ### > > > > > > > > > > > > > > ## GRAPHICS: > > > > > > > ## example buildfile commands: > > > > > > > ## io-graphics -domap2420 > > xres=240,yres=320,bitpp=16,photon > > > > > > -pphoton > > > > > > > ## > > > > > > > ## > > > > > > > ## required libraries: > > > > > > > ## Please refer to the photon embedding documentation > > > > > > > ## > > > > > > > ## required binaries: > > > > > > > ## Please refer to the photon embedding documentation > > > > > > > ## > > > > > > > ## > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > -- > > > > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > > > > Sent: February 8, 2011 12:26 PM > > > > > > > > To: advanced-graphics > > > > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > > > > > > > Thanks Derek for the reply. > > > > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), > > but > > > > you > > > > > > are > > > > > > > > right I could be getting the continuous calls because my > > > cursor > > > > is > > > > > > > > blinking. > > > > > > > > > > > > > > > > You are absolutely right about "minicom". I am using a > > serial > > > > > > terminal > > > > > > > > to launch the Pterm utility. I am not sure on what > priority > > my > > > > > > serial > > > > > > > > driver is running on. > > > > > > > > > > > > > > > > I would appreciate Derek if you could look at the attached > > > files > > > > > and > > > > > > see > > > > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > > > > > Advanced Graphics > > > > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > Advanced Graphics > > > > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Advanced Graphics > > > > > http://community.qnx.com/sf/go/post83038 > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post83041 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83091 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83093 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83097 Thu, 10 Feb 2011 18:13:30 GMT http://community.qnx.com/sf/go/post83099 Raj Pandey 2011-02-10T18:13:30Z http://community.qnx.com/sf/go/post83098 If you can see your pterm, it is running OK. Yes, GF apps need root priviledge, or you need to set up an access group, see the documentation for io-display. The binary for img_decode_simple should be shipped, under /usr/bin, or do you mean the source? -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 10, 2011 12:42 PM To: advanced-graphics Subject: Re: RE: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility I guess Photon is running alright. All I see is a window with some color on LCD panel along with a command prompt terminal just like a serial console. What will be the best way to check if the Photon is running perfectly? Also, how do I run all the GF apps with root privilage? Derek, my 2nd question was do I really need "img_decode_simple" utility to draw a bmp/jpg/gif image? If yes then how do I get it? Regards, Raj > ok, Photon is running, correct? Are you running it as root? By > default, all GF applications must run as root user. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 10, 2011 12:18 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > You are right Derek, there is no call to attach with any layer in the > gf-ph-2d code. > So, what went wrong. Why I can't see the gf-ph-2d app running? > > Do you suspect anything wrong with my settings? Be it > display.conf/omap35xx.conf or the build file. I need to mention one > thing that I added layer=0 entry in the photon part of the display.conf > file. > > Regards, > Raj > > > Is there any gf_layer_attach calls in the gf-ph-2d code? I don't > > believe it attaches directly to any layer ... > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 10, 2011 11:51 AM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > Thanks Derek. > > > > Primarily we would have liked to do this during startup but now we > > abandon the idea. Now we want to do it once the Photon is up and > display > > driver is running. > > I am assuming Photon is running on the main layer, layer=0. I tried > with > > the hybrid app that you shared yesterday but could not see any thing > on > > the LCD panel. Looking at the log it seems the GF app is trying to run > > on the layer=1. Pasting excerpt from the log after launching > "gf-ph-2d" > > app. > > > > ================================================ > > # gf-ph-2d > > Raw Widget: width = 235, height = 166 > > +devg_get_miscfuncs > > -devg_get_miscfuncs > > omap_module_info TI OMAP 35xx display Controller > > omap_alloc_surface ++ > > omap_get_alloc_info ++ > > **************PdCreateOffscreenContextGF(): No such process > > omap_layer_update_begin ++ > > omap_layer_set_surface ++ > > DISP_LAYER_FORMAT_RGB565 > > omap_layer_set_surface -- > > omap_layer_update_end ++ > > omap_layer_program ++ > > Video layer1 no scaling widthomap_layer_program > > OMAP_LAYER_VID1 > > omap_layer_program -- > > omap_layer_update_end -- > > > > ================================================ > > > > demarked the error text in the log. Why I got this error? > > > > the sloginfo is : > > > > ======================== > > > > # sloginfo > > Time Sev Major Minor Args > > Jan 01 00:00:09 1 8 0 phfont.so: init... > > Jan 01 00:00:09 1 8 0 phfont.so: initialized. > > Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' > > server installed. > > Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode > > Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing > > Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no > > more layers, maybe end of layer query) > > Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 > > Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 > > ======================== > > If my assumptions are right, by default photon starts on layer=0(GFX), > > any 2D app starts on layer=1(Video1) and 3D starts on layer=2(Video2). > > > > I was trying to display one JPEG image on the LCD panel and reading > > through the QNX docs I got to know that I will need > "img_decode_simple" > > to draw the image. I do have libimg.so in my image and do see the > > entries for various image formats in img.conf file. > > > > Right now, I do not have "img_decode_simple" utility and I heard it > > comes with Advanced Graphics. > > How do I get this utility to draw some image on the LCD panel. I would > > appreciate if you can clarify few of my doubts. > > > > Regards, > > Raj > > > > > Depends how soon you want it to come up ... do you want it > immediate, > > or > > > once io-display is running, or is it OK to wait until Photon is > > booted? > > > > > > Immediate is much more difficult. > > > > > > If once io-display is running, just run a GF application on a layer > > that > > > is behind the layer that Photon will use (if you have more than one > > > layer). You can slay it off later. > > > > > > If after Photon has booted, just run you Photon application before > any > > > other Photon applications. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 9, 2011 12:20 PM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > Thanks Again Derek for the reply. Appreciated it very much. I'll > work > > on > > > hybrid application tomorrow. > > > Is there a way to display QNX homescreen like all the other OS does > > ,e.g > > > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > > > during/after boot up? > > > > > > Regards, > > > Raj > > > > Ok, you will need to run it on a different layer than Photon, or > > turn > > > > your application into a Photon/GF hybrid application. Examples of > > > > hybrid applications can be found at: > > > > > > > > > > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > > > ton.gf_ph_2d > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 9, 2011 11:37 AM > > > > To: advanced-graphics > > > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > > > Thanks for the reply Derek. It is a GF application and not the > > Photon > > > > one. > > > > > > > > > Is this rectangle application a GF or a Photon application? > > > > > > > > > > No, there is no need to run it from pterm. > > > > > > > > > > -----Original Message----- > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > Sent: February 9, 2011 8:49 AM > > > > > To: advanced-graphics > > > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > > > > > I got the Pterm working. I ran the Pterm in background and I > could > > > see > > > > > the blinking cursor and I can type the commands in serial > > terminal. > > > > > > > > > > I created one simple app to draw a rectangle and I am trying to > > > launch > > > > > this app from the serial terminal and not the Pterm. I have put > > that > > > > > application in /src/utils/ folder. The application is there in > the > > > > > image. > > > > > > > > > > I have two question regarding this. > > > > > > > > > > i) Do I need to launch the app from the Pterm? > > > > > If yes, then I will need an input driver. > > > > > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > > > > > I tried doing it but it doesn't draw the rectangle. > > > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > > > > > > > Does anybody know why I got this error? I would appreciate the > > > reply. > > > > > > > > > > Note: > > > > > I could draw the rectangle by typing following command on pterm > > > "pterm > > > > > -x10 -y10 -height100 -width100". > > > > > > > > > > One final question. Is there a way to display the QNX home > screen > > on > > > > the > > > > > LCD panel? If yes, then how? > > > > > > > > > > Regards, > > > > > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## START OF BUILD SCRIPT > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > > > > > > > [image=0x80010000] > > > > > > [+compress] > > > > > > #[virtual=armle,binary] .bootstrap = { > > > > > > [virtual=armle,raw] .bootstrap = { > > > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## PATH set here is the *safe* path for executables. > > > > > > ## LD_LIBRARY_PATH set here is the *safe* path for > > libraries. > > > > > > ## i.e. These are the paths searched by > > setuid/setgid > > > > > binaries. > > > > > > ## (confstr(_CS_PATH...) and > > confstr(_CS_LIBPATH...)) > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon > > PHFONT=/dev/phfont > > > > > procnto-v6 > > > > > > } > > > > > > [+script] .script = { > > > > > > procmgr_symlink ../../proc/boot/libc.so.3 > > /usr/lib/ldqnx.so.2 > > > > > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > > > Instruments > > > > > > OMAP2430SDP Board > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## SERIAL driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > > > waitfor /dev/ser1 4 > > > > > > reopen /dev/ser1 > > > > > > > > > > > > slogger > > > > > > pipe > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## NAND_ETFS driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting etfs driver... > > > > > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## NETWORK driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > # > > > > > > #display_msg Starting on-board ethernet with TCP/IP > > stack... > > > > > > # > > > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > > > # > > > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## I2C driver > > > > > > ## - Required for both USB and AUDIO > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > display_msg Starting I2C driver... > > > > > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## USB driver > > > > > > ## - Requires the I2C driver to be running > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting USB stack... > > > > > > > > > > > > #omap2420sdp_usb_init > > > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## input > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## These env variables are inherited by all the programs > > which > > > > > follow > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > SYSNAME=nto > > > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > > > PHOTON_PATH=/usr/photon > > > > > > PHOTON=/dev/photon > > > > > > PHFONT=/dev/phfont > > > > > > TERM=qansi > > > > > > HOME=/ > > > > > > > > > > > > > > > > > > > > > ###################################################################### > > > > > > # > > > > > > ## GRAPHICS > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > display_msg Starting io-display... > > > > > > > > > > > > io-display -dvid=0,did=0 > > > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## Photon and Phfont > > > > > > ## - NOTE: Photon and phfont MUST be started before the > > GRAPHICS > > > > > driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > display_msg Starting Photon... > > > > > > Photon & > > > > > > waitfor /dev/photon 10 > > > > > > display_msg Starting Phfont... > > > > > > Phfont & > > > > > > waitfor /proc/boot/phfont 10 > > > > > > display_msg Starting io-graphics... > > > > > > io-graphics > > > > > > display_msg Starting PWM... > > > > > > pwm & > > > > > > display_msg Starting DEVC-PTY... > > > > > > devc-pty & > > > > > > display_msg Starting PTERM... > > > > > > pterm > > > > > > display_msg Starting BKGDMGR... > > > > > > bkgdmgr > > > > > > sloginfo > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## input > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > > > } > > > > > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > > > [type=link] /dev/console=/dev/ser1 > > > > > > [type=link] /tmp=/dev/shmem > > > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > > > earlier) > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > #libc.so.2 > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for standard libs > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > libc.so > > > > > > libm.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > libph.so > > > > > > libAp.so > > > > > > libphexlib.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > devg-omap35xx.so > > > > > > libgf.so > > > > > > libGLES_CM.so > > > > > > libimg.so > > > > > > gri-photon.so > > > > > > libphrender.so > > > > > > libgri.so > > > > > > libdisputil.so > > > > > > libffb.so > > > > > > libgf.so.1 > > > > > > libGLES_CL.so.1 > > > > > > > > > > > > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > > > ttings > > > > > > > > > > > > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > > > .pal > > > > > > > > > > > > > > > > > > [data=c] > > > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > ## font libs (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > devg-svga.so > > > > > > /etc/system/config/omap35xx.conf = > > > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > > > /lib/dll/font/ttfFFcore.so = > > > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > > > /lib/dll/font/PHFcore.so = > > > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > > > /lib/dll/font/FCcore.so = > > > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > > > libfontharnessutils.so > > > > > > libfontutils.so > > > > > > libblkcache.so > > > > > > libFF-T2K.so > > > > > > libFF-T2K-cache.so > > > > > > libFF-T2K-fm.so > > > > > > libfont.so > > > > > > phfont.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > ## font config (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > > > /usr/photon/font_repository/phcursor.phf = > > > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > > > /usr/photon/font_repository/mappings = > > > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > > > /usr/photon/font_repository/fontopts = > > > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > > > /usr/photon/font_repository/fontkey = > > > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > > > ; > > > > > > ; fontdir config file > > > > > > ; > > > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > > > BT,0,,0020-F002,f,79x170,109K > > > > > > } > > > > > > > > > > > > /usr/photon/font_repository/fontext = { > > > > > > ; > > > > > > ; fontext config file > > > > > > ; > > > > > > +normal = primasansmonobts, phcursor > > > > > > } > > > > > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > > > [SANSERIF] > > > > > > PrimaSansMono BT > > > > > > } > > > > > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > > > ; > > > > > > ; fontmap config file > > > > > > ; > > > > > > ? = primasansmonobts > > > > > > } > > > > > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > > > =Desktop Menu > > > > > > Terminal T pterm > > > > > > Calculator C phcalc_sm > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > devn-smc9000.so > > > > > > libsocket.so > > > > > > devnp-shim.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > libusbdi.so > > > > > > devu-ohci.so > > > > > > > > > > > > ##################################### > > > > > > #input driver > > > > > > ###################################### > > > > > > devi-omap_keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## Needed for Photon > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > devc-pty > > > > > > ksh > > > > > > slogger > > > > > > sloginfo > > > > > > Photon > > > > > > io-graphics > > > > > > io-display > > > > > > devi-hirun > > > > > > phfont > > > > > > pwm > > > > > > # photon applications required to be unstriped by mkifs, hence > > > these > > > > > have > > > > > > # +raw tag to tell mkifs not to strip them > > > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > > > > > # allow pterm to save its configuration to RAM, if the user > > > changes > > > > > it. > > > > > > [type=link] /.ph/pterm = /dev/shmem > > > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for etfs driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > fs-etfs-omap2420 > > > > > > etfsctl > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for I2C driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > i2c-omap59xx > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > io-pkt-v4 > > > > > > nicinfo > > > > > > ifconfig > > > > > > ping > > > > > > cat > > > > > > fs-nfs2 > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > io-usb > > > > > > omap2420sdp_usb_init > > > > > > usb > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for Graphics driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > vsync > > > > > > egl-gears-lite > > > > > > io-display > > > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > > > /etc/system/config/display.conf={ > > > > > > device \{ > > > > > > drivername=omap35xx > > > > > > vid=0 > > > > > > did=0 > > > > > > modeopts=/etc/system/config/omap35xx.conf > > > > > > display \{ > > > > > > xres=240 > > > > > > yres=320 > > > > > > refresh=60 > > > > > > pixel_format=rgb565 > > > > > > photon \{ > > > > > > enabled=1 > > > > > > xoffset=0 > > > > > > yoffset=0 > > > > > > cursor=software > > > > > > input_group=1 > > > > > > \} > > > > > > > > > > > > \} > > > > > > \} > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## general commands > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ls > > > > > > ksh > > > > > > pipe > > > > > > pidin > > > > > > uname > > > > > > slogger > > > > > > sloginfo > > > > > > slay > > > > > > cp > > > > > > chmod > > > > > > waitfor > > > > > > shutdown > > > > > > > > > > > > ##i2c utility > > > > > > i2c-reg > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## END OF BUILD SCRIPT > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > > > > > > > ## GRAPHICS: > > > > > > ## example buildfile commands: > > > > > > ## io-graphics -domap2420 > xres=240,yres=320,bitpp=16,photon > > > > > -pphoton > > > > > > ## > > > > > > ## > > > > > > ## required libraries: > > > > > > ## Please refer to the photon embedding documentation > > > > > > ## > > > > > > ## required binaries: > > > > > > ## Please refer to the photon embedding documentation > > > > > > ## > > > > > > ## > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > -- > > > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > > > Sent: February 8, 2011 12:26 PM > > > > > > > To: advanced-graphics > > > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > > > > > Thanks Derek for the reply. > > > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), > but > > > you > > > > > are > > > > > > > right I could be getting the continuous calls because my > > cursor > > > is > > > > > > > blinking. > > > > > > > > > > > > > > You are absolutely right about "minicom". I am using a > serial > > > > > terminal > > > > > > > to launch the Pterm utility. I am not sure on what priority > my > > > > > serial > > > > > > > driver is running on. > > > > > > > > > > > > > > I would appreciate Derek if you could look at the attached > > files > > > > and > > > > > see > > > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > > > Advanced Graphics > > > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Advanced Graphics > > > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post83038 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83041 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83091 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83093 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83097 Thu, 10 Feb 2011 17:44:53 GMT http://community.qnx.com/sf/go/post83098 Derek Leach 2011-02-10T17:44:53Z http://community.qnx.com/sf/go/post83097 I guess Photon is running alright. All I see is a window with some color on LCD panel along with a command prompt terminal just like a serial console. What will be the best way to check if the Photon is running perfectly? Also, how do I run all the GF apps with root privilage? Derek, my 2nd question was do I really need "img_decode_simple" utility to draw a bmp/jpg/gif image? If yes then how do I get it? Regards, Raj > ok, Photon is running, correct? Are you running it as root? By > default, all GF applications must run as root user. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 10, 2011 12:18 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > You are right Derek, there is no call to attach with any layer in the > gf-ph-2d code. > So, what went wrong. Why I can't see the gf-ph-2d app running? > > Do you suspect anything wrong with my settings? Be it > display.conf/omap35xx.conf or the build file. I need to mention one > thing that I added layer=0 entry in the photon part of the display.conf > file. > > Regards, > Raj > > > Is there any gf_layer_attach calls in the gf-ph-2d code? I don't > > believe it attaches directly to any layer ... > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 10, 2011 11:51 AM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > Thanks Derek. > > > > Primarily we would have liked to do this during startup but now we > > abandon the idea. Now we want to do it once the Photon is up and > display > > driver is running. > > I am assuming Photon is running on the main layer, layer=0. I tried > with > > the hybrid app that you shared yesterday but could not see any thing > on > > the LCD panel. Looking at the log it seems the GF app is trying to run > > on the layer=1. Pasting excerpt from the log after launching > "gf-ph-2d" > > app. > > > > ================================================ > > # gf-ph-2d > > Raw Widget: width = 235, height = 166 > > +devg_get_miscfuncs > > -devg_get_miscfuncs > > omap_module_info TI OMAP 35xx display Controller > > omap_alloc_surface ++ > > omap_get_alloc_info ++ > > **************PdCreateOffscreenContextGF(): No such process > > omap_layer_update_begin ++ > > omap_layer_set_surface ++ > > DISP_LAYER_FORMAT_RGB565 > > omap_layer_set_surface -- > > omap_layer_update_end ++ > > omap_layer_program ++ > > Video layer1 no scaling widthomap_layer_program > > OMAP_LAYER_VID1 > > omap_layer_program -- > > omap_layer_update_end -- > > > > ================================================ > > > > demarked the error text in the log. Why I got this error? > > > > the sloginfo is : > > > > ======================== > > > > # sloginfo > > Time Sev Major Minor Args > > Jan 01 00:00:09 1 8 0 phfont.so: init... > > Jan 01 00:00:09 1 8 0 phfont.so: initialized. > > Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' > > server installed. > > Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode > > Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing > > Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no > > more layers, maybe end of layer query) > > Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 > > Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 > > ======================== > > If my assumptions are right, by default photon starts on layer=0(GFX), > > any 2D app starts on layer=1(Video1) and 3D starts on layer=2(Video2). > > > > I was trying to display one JPEG image on the LCD panel and reading > > through the QNX docs I got to know that I will need > "img_decode_simple" > > to draw the image. I do have libimg.so in my image and do see the > > entries for various image formats in img.conf file. > > > > Right now, I do not have "img_decode_simple" utility and I heard it > > comes with Advanced Graphics. > > How do I get this utility to draw some image on the LCD panel. I would > > appreciate if you can clarify few of my doubts. > > > > Regards, > > Raj > > > > > Depends how soon you want it to come up ... do you want it > immediate, > > or > > > once io-display is running, or is it OK to wait until Photon is > > booted? > > > > > > Immediate is much more difficult. > > > > > > If once io-display is running, just run a GF application on a layer > > that > > > is behind the layer that Photon will use (if you have more than one > > > layer). You can slay it off later. > > > > > > If after Photon has booted, just run you Photon application before > any > > > other Photon applications. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 9, 2011 12:20 PM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > Thanks Again Derek for the reply. Appreciated it very much. I'll > work > > on > > > hybrid application tomorrow. > > > Is there a way to display QNX homescreen like all the other OS does > > ,e.g > > > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > > > during/after boot up? > > > > > > Regards, > > > Raj > > > > Ok, you will need to run it on a different layer than Photon, or > > turn > > > > your application into a Photon/GF hybrid application. Examples of > > > > hybrid applications can be found at: > > > > > > > > > > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > > > ton.gf_ph_2d > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 9, 2011 11:37 AM > > > > To: advanced-graphics > > > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > > > Thanks for the reply Derek. It is a GF application and not the > > Photon > > > > one. > > > > > > > > > Is this rectangle application a GF or a Photon application? > > > > > > > > > > No, there is no need to run it from pterm. > > > > > > > > > > -----Original Message----- > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > Sent: February 9, 2011 8:49 AM > > > > > To: advanced-graphics > > > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > > > > > I got the Pterm working. I ran the Pterm in background and I > could > > > see > > > > > the blinking cursor and I can type the commands in serial > > terminal. > > > > > > > > > > I created one simple app to draw a rectangle and I am trying to > > > launch > > > > > this app from the serial terminal and not the Pterm. I have put > > that > > > > > application in /src/utils/ folder. The application is there in > the > > > > > image. > > > > > > > > > > I have two question regarding this. > > > > > > > > > > i) Do I need to launch the app from the Pterm? > > > > > If yes, then I will need an input driver. > > > > > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > > > > > I tried doing it but it doesn't draw the rectangle. > > > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > > > > > > > Does anybody know why I got this error? I would appreciate the > > > reply. > > > > > > > > > > Note: > > > > > I could draw the rectangle by typing following command on pterm > > > "pterm > > > > > -x10 -y10 -height100 -width100". > > > > > > > > > > One final question. Is there a way to display the QNX home > screen > > on > > > > the > > > > > LCD panel? If yes, then how? > > > > > > > > > > Regards, > > > > > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## START OF BUILD SCRIPT > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > > > > > > > [image=0x80010000] > > > > > > [+compress] > > > > > > #[virtual=armle,binary] .bootstrap = { > > > > > > [virtual=armle,raw] .bootstrap = { > > > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## PATH set here is the *safe* path for executables. > > > > > > ## LD_LIBRARY_PATH set here is the *safe* path for > > libraries. > > > > > > ## i.e. These are the paths searched by > > setuid/setgid > > > > > binaries. > > > > > > ## (confstr(_CS_PATH...) and > > confstr(_CS_LIBPATH...)) > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon > > PHFONT=/dev/phfont > > > > > procnto-v6 > > > > > > } > > > > > > [+script] .script = { > > > > > > procmgr_symlink ../../proc/boot/libc.so.3 > > /usr/lib/ldqnx.so.2 > > > > > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > > > Instruments > > > > > > OMAP2430SDP Board > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## SERIAL driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > > > waitfor /dev/ser1 4 > > > > > > reopen /dev/ser1 > > > > > > > > > > > > slogger > > > > > > pipe > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## NAND_ETFS driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting etfs driver... > > > > > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## NETWORK driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > # > > > > > > #display_msg Starting on-board ethernet with TCP/IP > > stack... > > > > > > # > > > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > > > # > > > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## I2C driver > > > > > > ## - Required for both USB and AUDIO > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > display_msg Starting I2C driver... > > > > > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## USB driver > > > > > > ## - Requires the I2C driver to be running > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting USB stack... > > > > > > > > > > > > #omap2420sdp_usb_init > > > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## input > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## These env variables are inherited by all the programs > > which > > > > > follow > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > SYSNAME=nto > > > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > > > PHOTON_PATH=/usr/photon > > > > > > PHOTON=/dev/photon > > > > > > PHFONT=/dev/phfont > > > > > > TERM=qansi > > > > > > HOME=/ > > > > > > > > > > > > > > > > > > > > > ###################################################################### > > > > > > # > > > > > > ## GRAPHICS > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > display_msg Starting io-display... > > > > > > > > > > > > io-display -dvid=0,did=0 > > > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## Photon and Phfont > > > > > > ## - NOTE: Photon and phfont MUST be started before the > > GRAPHICS > > > > > driver > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > display_msg Starting Photon... > > > > > > Photon & > > > > > > waitfor /dev/photon 10 > > > > > > display_msg Starting Phfont... > > > > > > Phfont & > > > > > > waitfor /proc/boot/phfont 10 > > > > > > display_msg Starting io-graphics... > > > > > > io-graphics > > > > > > display_msg Starting PWM... > > > > > > pwm & > > > > > > display_msg Starting DEVC-PTY... > > > > > > devc-pty & > > > > > > display_msg Starting PTERM... > > > > > > pterm > > > > > > display_msg Starting BKGDMGR... > > > > > > bkgdmgr > > > > > > sloginfo > > > > > > > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > ## input > > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > > > } > > > > > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > > > [type=link] /dev/console=/dev/ser1 > > > > > > [type=link] /tmp=/dev/shmem > > > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > > > earlier) > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > #libc.so.2 > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for standard libs > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > libc.so > > > > > > libm.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > libph.so > > > > > > libAp.so > > > > > > libphexlib.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > devg-omap35xx.so > > > > > > libgf.so > > > > > > libGLES_CM.so > > > > > > libimg.so > > > > > > gri-photon.so > > > > > > libphrender.so > > > > > > libgri.so > > > > > > libdisputil.so > > > > > > libffb.so > > > > > > libgf.so.1 > > > > > > libGLES_CL.so.1 > > > > > > > > > > > > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > > > ttings > > > > > > > > > > > > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > > > .pal > > > > > > > > > > > > > > > > > > [data=c] > > > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > ## font libs (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > devg-svga.so > > > > > > /etc/system/config/omap35xx.conf = > > > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > > > /lib/dll/font/ttfFFcore.so = > > > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > > > /lib/dll/font/PHFcore.so = > > > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > > > /lib/dll/font/FCcore.so = > > > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > > > libfontharnessutils.so > > > > > > libfontutils.so > > > > > > libblkcache.so > > > > > > libFF-T2K.so > > > > > > libFF-T2K-cache.so > > > > > > libFF-T2K-fm.so > > > > > > libfont.so > > > > > > phfont.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > ## font config (GRAPHICS) > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ## > > > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > > > /usr/photon/font_repository/phcursor.phf = > > > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > > > /usr/photon/font_repository/mappings = > > > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > > > /usr/photon/font_repository/fontopts = > > > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > > > /usr/photon/font_repository/fontkey = > > > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > > > ; > > > > > > ; fontdir config file > > > > > > ; > > > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > > > BT,0,,0020-F002,f,79x170,109K > > > > > > } > > > > > > > > > > > > /usr/photon/font_repository/fontext = { > > > > > > ; > > > > > > ; fontext config file > > > > > > ; > > > > > > +normal = primasansmonobts, phcursor > > > > > > } > > > > > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > > > [SANSERIF] > > > > > > PrimaSansMono BT > > > > > > } > > > > > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > > > ; > > > > > > ; fontmap config file > > > > > > ; > > > > > > ? = primasansmonobts > > > > > > } > > > > > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > > > =Desktop Menu > > > > > > Terminal T pterm > > > > > > Calculator C phcalc_sm > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > devn-smc9000.so > > > > > > libsocket.so > > > > > > devnp-shim.so > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > libusbdi.so > > > > > > devu-ohci.so > > > > > > > > > > > > ##################################### > > > > > > #input driver > > > > > > ###################################### > > > > > > devi-omap_keypad > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## Needed for Photon > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > devc-pty > > > > > > ksh > > > > > > slogger > > > > > > sloginfo > > > > > > Photon > > > > > > io-graphics > > > > > > io-display > > > > > > devi-hirun > > > > > > phfont > > > > > > pwm > > > > > > # photon applications required to be unstriped by mkifs, hence > > > these > > > > > have > > > > > > # +raw tag to tell mkifs not to strip them > > > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > > > > > # allow pterm to save its configuration to RAM, if the user > > > changes > > > > > it. > > > > > > [type=link] /.ph/pterm = /dev/shmem > > > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for etfs driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > fs-etfs-omap2420 > > > > > > etfsctl > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for I2C driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > i2c-omap59xx > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > io-pkt-v4 > > > > > > nicinfo > > > > > > ifconfig > > > > > > ping > > > > > > cat > > > > > > fs-nfs2 > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > io-usb > > > > > > omap2420sdp_usb_init > > > > > > usb > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## uncomment for Graphics driver > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > vsync > > > > > > egl-gears-lite > > > > > > io-display > > > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > > > /etc/system/config/display.conf={ > > > > > > device \{ > > > > > > drivername=omap35xx > > > > > > vid=0 > > > > > > did=0 > > > > > > modeopts=/etc/system/config/omap35xx.conf > > > > > > display \{ > > > > > > xres=240 > > > > > > yres=320 > > > > > > refresh=60 > > > > > > pixel_format=rgb565 > > > > > > photon \{ > > > > > > enabled=1 > > > > > > xoffset=0 > > > > > > yoffset=0 > > > > > > cursor=software > > > > > > input_group=1 > > > > > > \} > > > > > > > > > > > > \} > > > > > > \} > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## general commands > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ls > > > > > > ksh > > > > > > pipe > > > > > > pidin > > > > > > uname > > > > > > slogger > > > > > > sloginfo > > > > > > slay > > > > > > cp > > > > > > chmod > > > > > > waitfor > > > > > > shutdown > > > > > > > > > > > > ##i2c utility > > > > > > i2c-reg > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > ## END OF BUILD SCRIPT > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > > ### > > > > > > > > > > > > ## GRAPHICS: > > > > > > ## example buildfile commands: > > > > > > ## io-graphics -domap2420 > xres=240,yres=320,bitpp=16,photon > > > > > -pphoton > > > > > > ## > > > > > > ## > > > > > > ## required libraries: > > > > > > ## Please refer to the photon embedding documentation > > > > > > ## > > > > > > ## required binaries: > > > > > > ## Please refer to the photon embedding documentation > > > > > > ## > > > > > > ## > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > -- > > > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > > > Sent: February 8, 2011 12:26 PM > > > > > > > To: advanced-graphics > > > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > > > > > Thanks Derek for the reply. > > > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), > but > > > you > > > > > are > > > > > > > right I could be getting the continuous calls because my > > cursor > > > is > > > > > > > blinking. > > > > > > > > > > > > > > You are absolutely right about "minicom". I am using a > serial > > > > > terminal > > > > > > > to launch the Pterm utility. I am not sure on what priority > my > > > > > serial > > > > > > > driver is running on. > > > > > > > > > > > > > > I would appreciate Derek if you could look at the attached > > files > > > > and > > > > > see > > > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > > > Advanced Graphics > > > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Advanced Graphics > > > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post83038 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83041 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83091 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83093 Thu, 10 Feb 2011 17:42:00 GMT http://community.qnx.com/sf/go/post83097 Raj Pandey 2011-02-10T17:42:00Z http://community.qnx.com/sf/go/post83094 ok, Photon is running, correct? Are you running it as root? By default, all GF applications must run as root user. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 10, 2011 12:18 PM To: advanced-graphics Subject: Re: RE: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility You are right Derek, there is no call to attach with any layer in the gf-ph-2d code. So, what went wrong. Why I can't see the gf-ph-2d app running? Do you suspect anything wrong with my settings? Be it display.conf/omap35xx.conf or the build file. I need to mention one thing that I added layer=0 entry in the photon part of the display.conf file. Regards, Raj > Is there any gf_layer_attach calls in the gf-ph-2d code? I don't > believe it attaches directly to any layer ... > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 10, 2011 11:51 AM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > Thanks Derek. > > Primarily we would have liked to do this during startup but now we > abandon the idea. Now we want to do it once the Photon is up and display > driver is running. > I am assuming Photon is running on the main layer, layer=0. I tried with > the hybrid app that you shared yesterday but could not see any thing on > the LCD panel. Looking at the log it seems the GF app is trying to run > on the layer=1. Pasting excerpt from the log after launching "gf-ph-2d" > app. > > ================================================ > # gf-ph-2d > Raw Widget: width = 235, height = 166 > +devg_get_miscfuncs > -devg_get_miscfuncs > omap_module_info TI OMAP 35xx display Controller > omap_alloc_surface ++ > omap_get_alloc_info ++ > **************PdCreateOffscreenContextGF(): No such process > omap_layer_update_begin ++ > omap_layer_set_surface ++ > DISP_LAYER_FORMAT_RGB565 > omap_layer_set_surface -- > omap_layer_update_end ++ > omap_layer_program ++ > Video layer1 no scaling widthomap_layer_program > OMAP_LAYER_VID1 > omap_layer_program -- > omap_layer_update_end -- > > ================================================ > > demarked the error text in the log. Why I got this error? > > the sloginfo is : > > ======================== > > # sloginfo > Time Sev Major Minor Args > Jan 01 00:00:09 1 8 0 phfont.so: init... > Jan 01 00:00:09 1 8 0 phfont.so: initialized. > Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' > server installed. > Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode > Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing > Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no > more layers, maybe end of layer query) > Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 > Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 > ======================== > If my assumptions are right, by default photon starts on layer=0(GFX), > any 2D app starts on layer=1(Video1) and 3D starts on layer=2(Video2). > > I was trying to display one JPEG image on the LCD panel and reading > through the QNX docs I got to know that I will need "img_decode_simple" > to draw the image. I do have libimg.so in my image and do see the > entries for various image formats in img.conf file. > > Right now, I do not have "img_decode_simple" utility and I heard it > comes with Advanced Graphics. > How do I get this utility to draw some image on the LCD panel. I would > appreciate if you can clarify few of my doubts. > > Regards, > Raj > > > Depends how soon you want it to come up ... do you want it immediate, > or > > once io-display is running, or is it OK to wait until Photon is > booted? > > > > Immediate is much more difficult. > > > > If once io-display is running, just run a GF application on a layer > that > > is behind the layer that Photon will use (if you have more than one > > layer). You can slay it off later. > > > > If after Photon has booted, just run you Photon application before any > > other Photon applications. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 9, 2011 12:20 PM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > Thanks Again Derek for the reply. Appreciated it very much. I'll work > on > > hybrid application tomorrow. > > Is there a way to display QNX homescreen like all the other OS does > ,e.g > > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > > during/after boot up? > > > > Regards, > > Raj > > > Ok, you will need to run it on a different layer than Photon, or > turn > > > your application into a Photon/GF hybrid application. Examples of > > > hybrid applications can be found at: > > > > > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > > ton.gf_ph_2d > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 9, 2011 11:37 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > Thanks for the reply Derek. It is a GF application and not the > Photon > > > one. > > > > > > > Is this rectangle application a GF or a Photon application? > > > > > > > > No, there is no need to run it from pterm. > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 9, 2011 8:49 AM > > > > To: advanced-graphics > > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > > > I got the Pterm working. I ran the Pterm in background and I could > > see > > > > the blinking cursor and I can type the commands in serial > terminal. > > > > > > > > I created one simple app to draw a rectangle and I am trying to > > launch > > > > this app from the serial terminal and not the Pterm. I have put > that > > > > application in /src/utils/ folder. The application is there in the > > > > image. > > > > > > > > I have two question regarding this. > > > > > > > > i) Do I need to launch the app from the Pterm? > > > > If yes, then I will need an input driver. > > > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > > > I tried doing it but it doesn't draw the rectangle. > > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > > > > > Does anybody know why I got this error? I would appreciate the > > reply. > > > > > > > > Note: > > > > I could draw the rectangle by typing following command on pterm > > "pterm > > > > -x10 -y10 -height100 -width100". > > > > > > > > One final question. Is there a way to display the QNX home screen > on > > > the > > > > LCD panel? If yes, then how? > > > > > > > > Regards, > > > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## START OF BUILD SCRIPT > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > > > > > > [image=0x80010000] > > > > > [+compress] > > > > > #[virtual=armle,binary] .bootstrap = { > > > > > [virtual=armle,raw] .bootstrap = { > > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > > > > > > ####################################################################### > > > > > ## PATH set here is the *safe* path for executables. > > > > > ## LD_LIBRARY_PATH set here is the *safe* path for > libraries. > > > > > ## i.e. These are the paths searched by > setuid/setgid > > > > binaries. > > > > > ## (confstr(_CS_PATH...) and > confstr(_CS_LIBPATH...)) > > > > > > > > > > > > > > > ####################################################################### > > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon > PHFONT=/dev/phfont > > > > procnto-v6 > > > > > } > > > > > [+script] .script = { > > > > > procmgr_symlink ../../proc/boot/libc.so.3 > /usr/lib/ldqnx.so.2 > > > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > > Instruments > > > > > OMAP2430SDP Board > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## SERIAL driver > > > > > > > > > > > > > > > ####################################################################### > > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > > waitfor /dev/ser1 4 > > > > > reopen /dev/ser1 > > > > > > > > > > slogger > > > > > pipe > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## NAND_ETFS driver > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting etfs driver... > > > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## NETWORK driver > > > > > > > > > > > > > > > ####################################################################### > > > > > # > > > > > #display_msg Starting on-board ethernet with TCP/IP > stack... > > > > > # > > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > > # > > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## I2C driver > > > > > ## - Required for both USB and AUDIO > > > > > > > > > > > > > > > ####################################################################### > > > > > display_msg Starting I2C driver... > > > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## USB driver > > > > > ## - Requires the I2C driver to be running > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting USB stack... > > > > > > > > > > #omap2420sdp_usb_init > > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## input > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## These env variables are inherited by all the programs > which > > > > follow > > > > > > > > > > > > > > > ####################################################################### > > > > > SYSNAME=nto > > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > > PHOTON_PATH=/usr/photon > > > > > PHOTON=/dev/photon > > > > > PHFONT=/dev/phfont > > > > > TERM=qansi > > > > > HOME=/ > > > > > > > > > > > > > > > > ###################################################################### > > > > > # > > > > > ## GRAPHICS > > > > > > > > > > > > > > > ####################################################################### > > > > > display_msg Starting io-display... > > > > > > > > > > io-display -dvid=0,did=0 > > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## Photon and Phfont > > > > > ## - NOTE: Photon and phfont MUST be started before the > GRAPHICS > > > > driver > > > > > > > > > > > > > > > ####################################################################### > > > > > display_msg Starting Photon... > > > > > Photon & > > > > > waitfor /dev/photon 10 > > > > > display_msg Starting Phfont... > > > > > Phfont & > > > > > waitfor /proc/boot/phfont 10 > > > > > display_msg Starting io-graphics... > > > > > io-graphics > > > > > display_msg Starting PWM... > > > > > pwm & > > > > > display_msg Starting DEVC-PTY... > > > > > devc-pty & > > > > > display_msg Starting PTERM... > > > > > pterm > > > > > display_msg Starting BKGDMGR... > > > > > bkgdmgr > > > > > sloginfo > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## input > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > > } > > > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > > [type=link] /dev/console=/dev/ser1 > > > > > [type=link] /tmp=/dev/shmem > > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > > earlier) > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > #libc.so.2 > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for standard libs > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > libc.so > > > > > libm.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > libph.so > > > > > libAp.so > > > > > libphexlib.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > devg-omap35xx.so > > > > > libgf.so > > > > > libGLES_CM.so > > > > > libimg.so > > > > > gri-photon.so > > > > > libphrender.so > > > > > libgri.so > > > > > libdisputil.so > > > > > libffb.so > > > > > libgf.so.1 > > > > > libGLES_CL.so.1 > > > > > > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > > ttings > > > > > > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > > .pal > > > > > > > > > > > > > > > [data=c] > > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > ## font libs (GRAPHICS) > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > devg-svga.so > > > > > /etc/system/config/omap35xx.conf = > > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > > /lib/dll/font/ttfFFcore.so = > > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > > /lib/dll/font/PHFcore.so = > > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > > /lib/dll/font/FCcore.so = > > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > > libfontharnessutils.so > > > > > libfontutils.so > > > > > libblkcache.so > > > > > libFF-T2K.so > > > > > libFF-T2K-cache.so > > > > > libFF-T2K-fm.so > > > > > libfont.so > > > > > phfont.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > ## font config (GRAPHICS) > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > > /usr/photon/font_repository/phcursor.phf = > > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > > /usr/photon/font_repository/mappings = > > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > > /usr/photon/font_repository/fontopts = > > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > > /usr/photon/font_repository/fontkey = > > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > > ; > > > > > ; fontdir config file > > > > > ; > > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > > BT,0,,0020-F002,f,79x170,109K > > > > > } > > > > > > > > > > /usr/photon/font_repository/fontext = { > > > > > ; > > > > > ; fontext config file > > > > > ; > > > > > +normal = primasansmonobts, phcursor > > > > > } > > > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > > [SANSERIF] > > > > > PrimaSansMono BT > > > > > } > > > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > > ; > > > > > ; fontmap config file > > > > > ; > > > > > ? = primasansmonobts > > > > > } > > > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > > =Desktop Menu > > > > > Terminal T pterm > > > > > Calculator C phcalc_sm > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > devn-smc9000.so > > > > > libsocket.so > > > > > devnp-shim.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > libusbdi.so > > > > > devu-ohci.so > > > > > > > > > > ##################################### > > > > > #input driver > > > > > ###################################### > > > > > devi-omap_keypad > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## Needed for Photon > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > devc-pty > > > > > ksh > > > > > slogger > > > > > sloginfo > > > > > Photon > > > > > io-graphics > > > > > io-display > > > > > devi-hirun > > > > > phfont > > > > > pwm > > > > > # photon applications required to be unstriped by mkifs, hence > > these > > > > have > > > > > # +raw tag to tell mkifs not to strip them > > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > > > # allow pterm to save its configuration to RAM, if the user > > changes > > > > it. > > > > > [type=link] /.ph/pterm = /dev/shmem > > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for etfs driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > fs-etfs-omap2420 > > > > > etfsctl > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for I2C driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > i2c-omap59xx > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > io-pkt-v4 > > > > > nicinfo > > > > > ifconfig > > > > > ping > > > > > cat > > > > > fs-nfs2 > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > io-usb > > > > > omap2420sdp_usb_init > > > > > usb > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for Graphics driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > vsync > > > > > egl-gears-lite > > > > > io-display > > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > > /etc/system/config/display.conf={ > > > > > device \{ > > > > > drivername=omap35xx > > > > > vid=0 > > > > > did=0 > > > > > modeopts=/etc/system/config/omap35xx.conf > > > > > display \{ > > > > > xres=240 > > > > > yres=320 > > > > > refresh=60 > > > > > pixel_format=rgb565 > > > > > photon \{ > > > > > enabled=1 > > > > > xoffset=0 > > > > > yoffset=0 > > > > > cursor=software > > > > > input_group=1 > > > > > \} > > > > > > > > > > \} > > > > > \} > > > > > } > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## general commands > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ls > > > > > ksh > > > > > pipe > > > > > pidin > > > > > uname > > > > > slogger > > > > > sloginfo > > > > > slay > > > > > cp > > > > > chmod > > > > > waitfor > > > > > shutdown > > > > > > > > > > ##i2c utility > > > > > i2c-reg > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## END OF BUILD SCRIPT > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > > > > > > ## GRAPHICS: > > > > > ## example buildfile commands: > > > > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > > > > -pphoton > > > > > ## > > > > > ## > > > > > ## required libraries: > > > > > ## Please refer to the photon embedding documentation > > > > > ## > > > > > ## required binaries: > > > > > ## Please refer to the photon embedding documentation > > > > > ## > > > > > ## > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > -- > > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > > > -----Original Message----- > > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > > Sent: February 8, 2011 12:26 PM > > > > > > To: advanced-graphics > > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > > > Thanks Derek for the reply. > > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), but > > you > > > > are > > > > > > right I could be getting the continuous calls because my > cursor > > is > > > > > > blinking. > > > > > > > > > > > > You are absolutely right about "minicom". I am using a serial > > > > terminal > > > > > > to launch the Pterm utility. I am not sure on what priority my > > > > serial > > > > > > driver is running on. > > > > > > > > > > > > I would appreciate Derek if you could look at the attached > files > > > and > > > > see > > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > Advanced Graphics > > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83038 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83041 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83091 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83093 Thu, 10 Feb 2011 17:20:59 GMT http://community.qnx.com/sf/go/post83094 Derek Leach 2011-02-10T17:20:59Z http://community.qnx.com/sf/go/post83093 You are right Derek, there is no call to attach with any layer in the gf-ph-2d code. So, what went wrong. Why I can't see the gf-ph-2d app running? Do you suspect anything wrong with my settings? Be it display.conf/omap35xx.conf or the build file. I need to mention one thing that I added layer=0 entry in the photon part of the display.conf file. Regards, Raj > Is there any gf_layer_attach calls in the gf-ph-2d code? I don't > believe it attaches directly to any layer ... > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 10, 2011 11:51 AM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility > > Thanks Derek. > > Primarily we would have liked to do this during startup but now we > abandon the idea. Now we want to do it once the Photon is up and display > driver is running. > I am assuming Photon is running on the main layer, layer=0. I tried with > the hybrid app that you shared yesterday but could not see any thing on > the LCD panel. Looking at the log it seems the GF app is trying to run > on the layer=1. Pasting excerpt from the log after launching "gf-ph-2d" > app. > > ================================================ > # gf-ph-2d > Raw Widget: width = 235, height = 166 > +devg_get_miscfuncs > -devg_get_miscfuncs > omap_module_info TI OMAP 35xx display Controller > omap_alloc_surface ++ > omap_get_alloc_info ++ > **************PdCreateOffscreenContextGF(): No such process > omap_layer_update_begin ++ > omap_layer_set_surface ++ > DISP_LAYER_FORMAT_RGB565 > omap_layer_set_surface -- > omap_layer_update_end ++ > omap_layer_program ++ > Video layer1 no scaling widthomap_layer_program > OMAP_LAYER_VID1 > omap_layer_program -- > omap_layer_update_end -- > > ================================================ > > demarked the error text in the log. Why I got this error? > > the sloginfo is : > > ======================== > > # sloginfo > Time Sev Major Minor Args > Jan 01 00:00:09 1 8 0 phfont.so: init... > Jan 01 00:00:09 1 8 0 phfont.so: initialized. > Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' > server installed. > Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode > Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing > Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no > more layers, maybe end of layer query) > Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 > Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 > ======================== > If my assumptions are right, by default photon starts on layer=0(GFX), > any 2D app starts on layer=1(Video1) and 3D starts on layer=2(Video2). > > I was trying to display one JPEG image on the LCD panel and reading > through the QNX docs I got to know that I will need "img_decode_simple" > to draw the image. I do have libimg.so in my image and do see the > entries for various image formats in img.conf file. > > Right now, I do not have "img_decode_simple" utility and I heard it > comes with Advanced Graphics. > How do I get this utility to draw some image on the LCD panel. I would > appreciate if you can clarify few of my doubts. > > Regards, > Raj > > > Depends how soon you want it to come up ... do you want it immediate, > or > > once io-display is running, or is it OK to wait until Photon is > booted? > > > > Immediate is much more difficult. > > > > If once io-display is running, just run a GF application on a layer > that > > is behind the layer that Photon will use (if you have more than one > > layer). You can slay it off later. > > > > If after Photon has booted, just run you Photon application before any > > other Photon applications. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 9, 2011 12:20 PM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > > > Thanks Again Derek for the reply. Appreciated it very much. I'll work > on > > hybrid application tomorrow. > > Is there a way to display QNX homescreen like all the other OS does > ,e.g > > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > > during/after boot up? > > > > Regards, > > Raj > > > Ok, you will need to run it on a different layer than Photon, or > turn > > > your application into a Photon/GF hybrid application. Examples of > > > hybrid applications can be found at: > > > > > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > > ton.gf_ph_2d > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 9, 2011 11:37 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > > > Thanks for the reply Derek. It is a GF application and not the > Photon > > > one. > > > > > > > Is this rectangle application a GF or a Photon application? > > > > > > > > No, there is no need to run it from pterm. > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 9, 2011 8:49 AM > > > > To: advanced-graphics > > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > > > I got the Pterm working. I ran the Pterm in background and I could > > see > > > > the blinking cursor and I can type the commands in serial > terminal. > > > > > > > > I created one simple app to draw a rectangle and I am trying to > > launch > > > > this app from the serial terminal and not the Pterm. I have put > that > > > > application in /src/utils/ folder. The application is there in the > > > > image. > > > > > > > > I have two question regarding this. > > > > > > > > i) Do I need to launch the app from the Pterm? > > > > If yes, then I will need an input driver. > > > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > > > I tried doing it but it doesn't draw the rectangle. > > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > > > > > Does anybody know why I got this error? I would appreciate the > > reply. > > > > > > > > Note: > > > > I could draw the rectangle by typing following command on pterm > > "pterm > > > > -x10 -y10 -height100 -width100". > > > > > > > > One final question. Is there a way to display the QNX home screen > on > > > the > > > > LCD panel? If yes, then how? > > > > > > > > Regards, > > > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## START OF BUILD SCRIPT > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > > > > > > [image=0x80010000] > > > > > [+compress] > > > > > #[virtual=armle,binary] .bootstrap = { > > > > > [virtual=armle,raw] .bootstrap = { > > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > > > > > > ####################################################################### > > > > > ## PATH set here is the *safe* path for executables. > > > > > ## LD_LIBRARY_PATH set here is the *safe* path for > libraries. > > > > > ## i.e. These are the paths searched by > setuid/setgid > > > > binaries. > > > > > ## (confstr(_CS_PATH...) and > confstr(_CS_LIBPATH...)) > > > > > > > > > > > > > > > ####################################################################### > > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon > PHFONT=/dev/phfont > > > > procnto-v6 > > > > > } > > > > > [+script] .script = { > > > > > procmgr_symlink ../../proc/boot/libc.so.3 > /usr/lib/ldqnx.so.2 > > > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > > Instruments > > > > > OMAP2430SDP Board > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## SERIAL driver > > > > > > > > > > > > > > > ####################################################################### > > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > > waitfor /dev/ser1 4 > > > > > reopen /dev/ser1 > > > > > > > > > > slogger > > > > > pipe > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## NAND_ETFS driver > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting etfs driver... > > > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## NETWORK driver > > > > > > > > > > > > > > > ####################################################################### > > > > > # > > > > > #display_msg Starting on-board ethernet with TCP/IP > stack... > > > > > # > > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > > # > > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## I2C driver > > > > > ## - Required for both USB and AUDIO > > > > > > > > > > > > > > > ####################################################################### > > > > > display_msg Starting I2C driver... > > > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## USB driver > > > > > ## - Requires the I2C driver to be running > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting USB stack... > > > > > > > > > > #omap2420sdp_usb_init > > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## input > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## These env variables are inherited by all the programs > which > > > > follow > > > > > > > > > > > > > > > ####################################################################### > > > > > SYSNAME=nto > > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > > PHOTON_PATH=/usr/photon > > > > > PHOTON=/dev/photon > > > > > PHFONT=/dev/phfont > > > > > TERM=qansi > > > > > HOME=/ > > > > > > > > > > > > > > > > ###################################################################### > > > > > # > > > > > ## GRAPHICS > > > > > > > > > > > > > > > ####################################################################### > > > > > display_msg Starting io-display... > > > > > > > > > > io-display -dvid=0,did=0 > > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## Photon and Phfont > > > > > ## - NOTE: Photon and phfont MUST be started before the > GRAPHICS > > > > driver > > > > > > > > > > > > > > > ####################################################################### > > > > > display_msg Starting Photon... > > > > > Photon & > > > > > waitfor /dev/photon 10 > > > > > display_msg Starting Phfont... > > > > > Phfont & > > > > > waitfor /proc/boot/phfont 10 > > > > > display_msg Starting io-graphics... > > > > > io-graphics > > > > > display_msg Starting PWM... > > > > > pwm & > > > > > display_msg Starting DEVC-PTY... > > > > > devc-pty & > > > > > display_msg Starting PTERM... > > > > > pterm > > > > > display_msg Starting BKGDMGR... > > > > > bkgdmgr > > > > > sloginfo > > > > > > > > > > > > > > > > > > > > ####################################################################### > > > > > ## input > > > > > > > > > > > > > > > ####################################################################### > > > > > #display_msg Starting Keypad driver... > > > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > > } > > > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > > [type=link] /dev/console=/dev/ser1 > > > > > [type=link] /tmp=/dev/shmem > > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > > earlier) > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > #libc.so.2 > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for standard libs > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > libc.so > > > > > libm.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > libph.so > > > > > libAp.so > > > > > libphexlib.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > devg-omap35xx.so > > > > > libgf.so > > > > > libGLES_CM.so > > > > > libimg.so > > > > > gri-photon.so > > > > > libphrender.so > > > > > libgri.so > > > > > libdisputil.so > > > > > libffb.so > > > > > libgf.so.1 > > > > > libGLES_CL.so.1 > > > > > > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > > ttings > > > > > > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > > .pal > > > > > > > > > > > > > > > [data=c] > > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > ## font libs (GRAPHICS) > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > devg-svga.so > > > > > /etc/system/config/omap35xx.conf = > > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > > /lib/dll/font/ttfFFcore.so = > > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > > /lib/dll/font/PHFcore.so = > > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > > /lib/dll/font/FCcore.so = > > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > > libfontharnessutils.so > > > > > libfontutils.so > > > > > libblkcache.so > > > > > libFF-T2K.so > > > > > libFF-T2K-cache.so > > > > > libFF-T2K-fm.so > > > > > libfont.so > > > > > phfont.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > ## font config (GRAPHICS) > > > > > > > > > > > > > > > ######################################################################## > > > > ## > > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > > /usr/photon/font_repository/phcursor.phf = > > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > > /usr/photon/font_repository/mappings = > > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > > /usr/photon/font_repository/fontopts = > > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > > /usr/photon/font_repository/fontkey = > > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > > ; > > > > > ; fontdir config file > > > > > ; > > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > > BT,0,,0020-F002,f,79x170,109K > > > > > } > > > > > > > > > > /usr/photon/font_repository/fontext = { > > > > > ; > > > > > ; fontext config file > > > > > ; > > > > > +normal = primasansmonobts, phcursor > > > > > } > > > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > > [SANSERIF] > > > > > PrimaSansMono BT > > > > > } > > > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > > ; > > > > > ; fontmap config file > > > > > ; > > > > > ? = primasansmonobts > > > > > } > > > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > > =Desktop Menu > > > > > Terminal T pterm > > > > > Calculator C phcalc_sm > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > devn-smc9000.so > > > > > libsocket.so > > > > > devnp-shim.so > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > libusbdi.so > > > > > devu-ohci.so > > > > > > > > > > ##################################### > > > > > #input driver > > > > > ###################################### > > > > > devi-omap_keypad > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## Needed for Photon > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > devc-pty > > > > > ksh > > > > > slogger > > > > > sloginfo > > > > > Photon > > > > > io-graphics > > > > > io-display > > > > > devi-hirun > > > > > phfont > > > > > pwm > > > > > # photon applications required to be unstriped by mkifs, hence > > these > > > > have > > > > > # +raw tag to tell mkifs not to strip them > > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > > > # allow pterm to save its configuration to RAM, if the user > > changes > > > > it. > > > > > [type=link] /.ph/pterm = /dev/shmem > > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for etfs driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > fs-etfs-omap2420 > > > > > etfsctl > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for I2C driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > i2c-omap59xx > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for NETWORK driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > io-pkt-v4 > > > > > nicinfo > > > > > ifconfig > > > > > ping > > > > > cat > > > > > fs-nfs2 > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for USB driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > io-usb > > > > > omap2420sdp_usb_init > > > > > usb > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## uncomment for Graphics driver > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > vsync > > > > > egl-gears-lite > > > > > io-display > > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > > /etc/system/config/display.conf={ > > > > > device \{ > > > > > drivername=omap35xx > > > > > vid=0 > > > > > did=0 > > > > > modeopts=/etc/system/config/omap35xx.conf > > > > > display \{ > > > > > xres=240 > > > > > yres=320 > > > > > refresh=60 > > > > > pixel_format=rgb565 > > > > > photon \{ > > > > > enabled=1 > > > > > xoffset=0 > > > > > yoffset=0 > > > > > cursor=software > > > > > input_group=1 > > > > > \} > > > > > > > > > > \} > > > > > \} > > > > > } > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## general commands > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ls > > > > > ksh > > > > > pipe > > > > > pidin > > > > > uname > > > > > slogger > > > > > sloginfo > > > > > slay > > > > > cp > > > > > chmod > > > > > waitfor > > > > > shutdown > > > > > > > > > > ##i2c utility > > > > > i2c-reg > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > ## END OF BUILD SCRIPT > > > > > > > > > > > > > > > ######################################################################## > > > > ### > > > > > > > > > > ## GRAPHICS: > > > > > ## example buildfile commands: > > > > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > > > > -pphoton > > > > > ## > > > > > ## > > > > > ## required libraries: > > > > > ## Please refer to the photon embedding documentation > > > > > ## > > > > > ## required binaries: > > > > > ## Please refer to the photon embedding documentation > > > > > ## > > > > > ## > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > -- > > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > > > -----Original Message----- > > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > > Sent: February 8, 2011 12:26 PM > > > > > > To: advanced-graphics > > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > > > Thanks Derek for the reply. > > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), but > > you > > > > are > > > > > > right I could be getting the continuous calls because my > cursor > > is > > > > > > blinking. > > > > > > > > > > > > You are absolutely right about "minicom". I am using a serial > > > > terminal > > > > > > to launch the Pterm utility. I am not sure on what priority my > > > > serial > > > > > > driver is running on. > > > > > > > > > > > > I would appreciate Derek if you could look at the attached > files > > > and > > > > see > > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > Advanced Graphics > > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83038 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83041 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83091 Thu, 10 Feb 2011 17:17:55 GMT http://community.qnx.com/sf/go/post83093 Raj Pandey 2011-02-10T17:17:55Z http://community.qnx.com/sf/go/post83092 Is there any gf_layer_attach calls in the gf-ph-2d code? I don't believe it attaches directly to any layer ... -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 10, 2011 11:51 AM To: advanced-graphics Subject: Re: RE: RE: RE: RE: RE: Display Hanging after Pterm Utility Thanks Derek. Primarily we would have liked to do this during startup but now we abandon the idea. Now we want to do it once the Photon is up and display driver is running. I am assuming Photon is running on the main layer, layer=0. I tried with the hybrid app that you shared yesterday but could not see any thing on the LCD panel. Looking at the log it seems the GF app is trying to run on the layer=1. Pasting excerpt from the log after launching "gf-ph-2d" app. ================================================ # gf-ph-2d Raw Widget: width = 235, height = 166 +devg_get_miscfuncs -devg_get_miscfuncs omap_module_info TI OMAP 35xx display Controller omap_alloc_surface ++ omap_get_alloc_info ++ **************PdCreateOffscreenContextGF(): No such process omap_layer_update_begin ++ omap_layer_set_surface ++ DISP_LAYER_FORMAT_RGB565 omap_layer_set_surface -- omap_layer_update_end ++ omap_layer_program ++ Video layer1 no scaling widthomap_layer_program OMAP_LAYER_VID1 omap_layer_program -- omap_layer_update_end -- ================================================ demarked the error text in the log. Why I got this error? the sloginfo is : ======================== # sloginfo Time Sev Major Minor Args Jan 01 00:00:09 1 8 0 phfont.so: init... Jan 01 00:00:09 1 8 0 phfont.so: initialized. Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' server installed. Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no more layers, maybe end of layer query) Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 ======================== If my assumptions are right, by default photon starts on layer=0(GFX), any 2D app starts on layer=1(Video1) and 3D starts on layer=2(Video2). I was trying to display one JPEG image on the LCD panel and reading through the QNX docs I got to know that I will need "img_decode_simple" to draw the image. I do have libimg.so in my image and do see the entries for various image formats in img.conf file. Right now, I do not have "img_decode_simple" utility and I heard it comes with Advanced Graphics. How do I get this utility to draw some image on the LCD panel. I would appreciate if you can clarify few of my doubts. Regards, Raj > Depends how soon you want it to come up ... do you want it immediate, or > once io-display is running, or is it OK to wait until Photon is booted? > > Immediate is much more difficult. > > If once io-display is running, just run a GF application on a layer that > is behind the layer that Photon will use (if you have more than one > layer). You can slay it off later. > > If after Photon has booted, just run you Photon application before any > other Photon applications. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 9, 2011 12:20 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > Thanks Again Derek for the reply. Appreciated it very much. I'll work on > hybrid application tomorrow. > Is there a way to display QNX homescreen like all the other OS does ,e.g > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > during/after boot up? > > Regards, > Raj > > Ok, you will need to run it on a different layer than Photon, or turn > > your application into a Photon/GF hybrid application. Examples of > > hybrid applications can be found at: > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > ton.gf_ph_2d > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 9, 2011 11:37 AM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > Thanks for the reply Derek. It is a GF application and not the Photon > > one. > > > > > Is this rectangle application a GF or a Photon application? > > > > > > No, there is no need to run it from pterm. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 9, 2011 8:49 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > I got the Pterm working. I ran the Pterm in background and I could > see > > > the blinking cursor and I can type the commands in serial terminal. > > > > > > I created one simple app to draw a rectangle and I am trying to > launch > > > this app from the serial terminal and not the Pterm. I have put that > > > application in /src/utils/ folder. The application is there in the > > > image. > > > > > > I have two question regarding this. > > > > > > i) Do I need to launch the app from the Pterm? > > > If yes, then I will need an input driver. > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > I tried doing it but it doesn't draw the rectangle. > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > > > Does anybody know why I got this error? I would appreciate the > reply. > > > > > > Note: > > > I could draw the rectangle by typing following command on pterm > "pterm > > > -x10 -y10 -height100 -width100". > > > > > > One final question. Is there a way to display the QNX home screen on > > the > > > LCD panel? If yes, then how? > > > > > > Regards, > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## START OF BUILD SCRIPT > > > > > > > > > > ######################################################################## > > > ### > > > > > > > > [image=0x80010000] > > > > [+compress] > > > > #[virtual=armle,binary] .bootstrap = { > > > > [virtual=armle,raw] .bootstrap = { > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > ####################################################################### > > > > ## PATH set here is the *safe* path for executables. > > > > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > > > > ## i.e. These are the paths searched by setuid/setgid > > > binaries. > > > > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > > > > > > > > > > ####################################################################### > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont > > > procnto-v6 > > > > } > > > > [+script] .script = { > > > > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > Instruments > > > > OMAP2430SDP Board > > > > > > > > > > > > > > ####################################################################### > > > > ## SERIAL driver > > > > > > > > > > ####################################################################### > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > waitfor /dev/ser1 4 > > > > reopen /dev/ser1 > > > > > > > > slogger > > > > pipe > > > > > > > > > > > > > > ####################################################################### > > > > ## NAND_ETFS driver > > > > > > > > > > ####################################################################### > > > > #display_msg Starting etfs driver... > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > ####################################################################### > > > > ## NETWORK driver > > > > > > > > > > ####################################################################### > > > > # > > > > #display_msg Starting on-board ethernet with TCP/IP stack... > > > > # > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > # > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > ####################################################################### > > > > ## I2C driver > > > > ## - Required for both USB and AUDIO > > > > > > > > > > ####################################################################### > > > > display_msg Starting I2C driver... > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > ####################################################################### > > > > ## USB driver > > > > ## - Requires the I2C driver to be running > > > > > > > > > > ####################################################################### > > > > #display_msg Starting USB stack... > > > > > > > > #omap2420sdp_usb_init > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > ####################################################################### > > > > ## input > > > > > > > > > > ####################################################################### > > > > #display_msg Starting Keypad driver... > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > ####################################################################### > > > > ## These env variables are inherited by all the programs which > > > follow > > > > > > > > > > ####################################################################### > > > > SYSNAME=nto > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > PHOTON_PATH=/usr/photon > > > > PHOTON=/dev/photon > > > > PHFONT=/dev/phfont > > > > TERM=qansi > > > > HOME=/ > > > > > > > > > > > > ###################################################################### > > > > # > > > > ## GRAPHICS > > > > > > > > > > ####################################################################### > > > > display_msg Starting io-display... > > > > > > > > io-display -dvid=0,did=0 > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > ####################################################################### > > > > ## Photon and Phfont > > > > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS > > > driver > > > > > > > > > > ####################################################################### > > > > display_msg Starting Photon... > > > > Photon & > > > > waitfor /dev/photon 10 > > > > display_msg Starting Phfont... > > > > Phfont & > > > > waitfor /proc/boot/phfont 10 > > > > display_msg Starting io-graphics... > > > > io-graphics > > > > display_msg Starting PWM... > > > > pwm & > > > > display_msg Starting DEVC-PTY... > > > > devc-pty & > > > > display_msg Starting PTERM... > > > > pterm > > > > display_msg Starting BKGDMGR... > > > > bkgdmgr > > > > sloginfo > > > > > > > > > > > > > > ####################################################################### > > > > ## input > > > > > > > > > > ####################################################################### > > > > #display_msg Starting Keypad driver... > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > } > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > [type=link] /dev/console=/dev/ser1 > > > > [type=link] /tmp=/dev/shmem > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > earlier) > > > > > > > > > > > > ######################################################################## > > > ### > > > > #libc.so.2 > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for standard libs > > > > > > > > > > ######################################################################## > > > ### > > > > libc.so > > > > libm.so > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > ######################################################################## > > > ### > > > > libph.so > > > > libAp.so > > > > libphexlib.so > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > ######################################################################## > > > ### > > > > devg-omap35xx.so > > > > libgf.so > > > > libGLES_CM.so > > > > libimg.so > > > > gri-photon.so > > > > libphrender.so > > > > libgri.so > > > > libdisputil.so > > > > libffb.so > > > > libgf.so.1 > > > > libGLES_CL.so.1 > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > ttings > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > .pal > > > > > > > > > > > > [data=c] > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > ## > > > > ## font libs (GRAPHICS) > > > > > > > > > > ######################################################################## > > > ## > > > > devg-svga.so > > > > /etc/system/config/omap35xx.conf = > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > /lib/dll/font/ttfFFcore.so = > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > /lib/dll/font/PHFcore.so = > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > /lib/dll/font/FCcore.so = > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > libfontharnessutils.so > > > > libfontutils.so > > > > libblkcache.so > > > > libFF-T2K.so > > > > libFF-T2K-cache.so > > > > libFF-T2K-fm.so > > > > libfont.so > > > > phfont.so > > > > > > > > > > > > > > ######################################################################## > > > ## > > > > ## font config (GRAPHICS) > > > > > > > > > > ######################################################################## > > > ## > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > /usr/photon/font_repository/phcursor.phf = > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > /usr/photon/font_repository/mappings = > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > /usr/photon/font_repository/fontopts = > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > /usr/photon/font_repository/fontkey = > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > ; > > > > ; fontdir config file > > > > ; > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > BT,0,,0020-F002,f,79x170,109K > > > > } > > > > > > > > /usr/photon/font_repository/fontext = { > > > > ; > > > > ; fontext config file > > > > ; > > > > +normal = primasansmonobts, phcursor > > > > } > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > [SANSERIF] > > > > PrimaSansMono BT > > > > } > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > ; > > > > ; fontmap config file > > > > ; > > > > ? = primasansmonobts > > > > } > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > =Desktop Menu > > > > Terminal T pterm > > > > Calculator C phcalc_sm > > > > } > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for NETWORK driver > > > > > > > > > > ######################################################################## > > > ### > > > > devn-smc9000.so > > > > libsocket.so > > > > devnp-shim.so > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for USB driver > > > > > > > > > > ######################################################################## > > > ### > > > > libusbdi.so > > > > devu-ohci.so > > > > > > > > ##################################### > > > > #input driver > > > > ###################################### > > > > devi-omap_keypad > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## Needed for Photon > > > > > > > > > > ######################################################################## > > > ### > > > > devc-pty > > > > ksh > > > > slogger > > > > sloginfo > > > > Photon > > > > io-graphics > > > > io-display > > > > devi-hirun > > > > phfont > > > > pwm > > > > # photon applications required to be unstriped by mkifs, hence > these > > > have > > > > # +raw tag to tell mkifs not to strip them > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > # allow pterm to save its configuration to RAM, if the user > changes > > > it. > > > > [type=link] /.ph/pterm = /dev/shmem > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for etfs driver > > > > > > > > > > ######################################################################## > > > ### > > > > fs-etfs-omap2420 > > > > etfsctl > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for I2C driver > > > > > > > > > > ######################################################################## > > > ### > > > > i2c-omap59xx > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for NETWORK driver > > > > > > > > > > ######################################################################## > > > ### > > > > io-pkt-v4 > > > > nicinfo > > > > ifconfig > > > > ping > > > > cat > > > > fs-nfs2 > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for USB driver > > > > > > > > > > ######################################################################## > > > ### > > > > io-usb > > > > omap2420sdp_usb_init > > > > usb > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for Graphics driver > > > > > > > > > > ######################################################################## > > > ### > > > > vsync > > > > egl-gears-lite > > > > io-display > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > /etc/system/config/display.conf={ > > > > device \{ > > > > drivername=omap35xx > > > > vid=0 > > > > did=0 > > > > modeopts=/etc/system/config/omap35xx.conf > > > > display \{ > > > > xres=240 > > > > yres=320 > > > > refresh=60 > > > > pixel_format=rgb565 > > > > photon \{ > > > > enabled=1 > > > > xoffset=0 > > > > yoffset=0 > > > > cursor=software > > > > input_group=1 > > > > \} > > > > > > > > \} > > > > \} > > > > } > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## general commands > > > > > > > > > > ######################################################################## > > > ### > > > > ls > > > > ksh > > > > pipe > > > > pidin > > > > uname > > > > slogger > > > > sloginfo > > > > slay > > > > cp > > > > chmod > > > > waitfor > > > > shutdown > > > > > > > > ##i2c utility > > > > i2c-reg > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## END OF BUILD SCRIPT > > > > > > > > > > ######################################################################## > > > ### > > > > > > > > ## GRAPHICS: > > > > ## example buildfile commands: > > > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > > > -pphoton > > > > ## > > > > ## > > > > ## required libraries: > > > > ## Please refer to the photon embedding documentation > > > > ## > > > > ## required binaries: > > > > ## Please refer to the photon embedding documentation > > > > ## > > > > ## > > > > > > > > > > ------------------------------------------------------------------------ > > > -- > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > -----Original Message----- > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > Sent: February 8, 2011 12:26 PM > > > > > To: advanced-graphics > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > Thanks Derek for the reply. > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), but > you > > > are > > > > > right I could be getting the continuous calls because my cursor > is > > > > > blinking. > > > > > > > > > > You are absolutely right about "minicom". I am using a serial > > > terminal > > > > > to launch the Pterm utility. I am not sure on what priority my > > > serial > > > > > driver is running on. > > > > > > > > > > I would appreciate Derek if you could look at the attached files > > and > > > see > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Advanced Graphics > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83038 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83041 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83091 Thu, 10 Feb 2011 16:56:50 GMT http://community.qnx.com/sf/go/post83092 Derek Leach 2011-02-10T16:56:50Z http://community.qnx.com/sf/go/post83091 Thanks Derek. Primarily we would have liked to do this during startup but now we abandon the idea. Now we want to do it once the Photon is up and display driver is running. I am assuming Photon is running on the main layer, layer=0. I tried with the hybrid app that you shared yesterday but could not see any thing on the LCD panel. Looking at the log it seems the GF app is trying to run on the layer=1. Pasting excerpt from the log after launching "gf-ph-2d" app. ================================================ # gf-ph-2d Raw Widget: width = 235, height = 166 +devg_get_miscfuncs -devg_get_miscfuncs omap_module_info TI OMAP 35xx display Controller omap_alloc_surface ++ omap_get_alloc_info ++ **************PdCreateOffscreenContextGF(): No such process omap_layer_update_begin ++ omap_layer_set_surface ++ DISP_LAYER_FORMAT_RGB565 omap_layer_set_surface -- omap_layer_update_end ++ omap_layer_program ++ Video layer1 no scaling widthomap_layer_program OMAP_LAYER_VID1 omap_layer_program -- omap_layer_update_end -- ================================================ demarked the error text in the log. Why I got this error? the sloginfo is : ======================== # sloginfo Time Sev Major Minor Args Jan 01 00:00:09 1 8 0 phfont.so: init... Jan 01 00:00:09 1 8 0 phfont.so: initialized. Jan 01 00:00:09 1 8 0 phfont.so: '/dev/phfont[<32|64>]' server installed. Jan 01 00:00:11 6 8 0 omap_set_mode QVGA mode Jan 01 00:00:11 6 8 0 omap_set_mode Use custom timing Jan 01 00:00:11 6 8 0 omap_layer_query Layer unknown, (no more layers, maybe end of layer query) Jan 01 00:00:11 6 8 0 omap_layer_program VIDEO 1 Jan 01 00:00:19 6 8 0 omap_layer_program VIDEO 1 ======================== If my assumptions are right, by default photon starts on layer=0(GFX), any 2D app starts on layer=1(Video1) and 3D starts on layer=2(Video2). I was trying to display one JPEG image on the LCD panel and reading through the QNX docs I got to know that I will need "img_decode_simple" to draw the image. I do have libimg.so in my image and do see the entries for various image formats in img.conf file. Right now, I do not have "img_decode_simple" utility and I heard it comes with Advanced Graphics. How do I get this utility to draw some image on the LCD panel. I would appreciate if you can clarify few of my doubts. Regards, Raj > Depends how soon you want it to come up ... do you want it immediate, or > once io-display is running, or is it OK to wait until Photon is booted? > > Immediate is much more difficult. > > If once io-display is running, just run a GF application on a layer that > is behind the layer that Photon will use (if you have more than one > layer). You can slay it off later. > > If after Photon has booted, just run you Photon application before any > other Photon applications. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 9, 2011 12:20 PM > To: advanced-graphics > Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility > > Thanks Again Derek for the reply. Appreciated it very much. I'll work on > hybrid application tomorrow. > Is there a way to display QNX homescreen like all the other OS does ,e.g > Linux shows a "penguin" or WindowsCE/Mobile shows their logo > during/after boot up? > > Regards, > Raj > > Ok, you will need to run it on a different layer than Photon, or turn > > your application into a Photon/GF hybrid application. Examples of > > hybrid applications can be found at: > > > > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > > ton.gf_ph_2d > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 9, 2011 11:37 AM > > To: advanced-graphics > > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > > > Thanks for the reply Derek. It is a GF application and not the Photon > > one. > > > > > Is this rectangle application a GF or a Photon application? > > > > > > No, there is no need to run it from pterm. > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 9, 2011 8:49 AM > > > To: advanced-graphics > > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > > > I got the Pterm working. I ran the Pterm in background and I could > see > > > the blinking cursor and I can type the commands in serial terminal. > > > > > > I created one simple app to draw a rectangle and I am trying to > launch > > > this app from the serial terminal and not the Pterm. I have put that > > > application in /src/utils/ folder. The application is there in the > > > image. > > > > > > I have two question regarding this. > > > > > > i) Do I need to launch the app from the Pterm? > > > If yes, then I will need an input driver. > > > > > > ii) Can I launch that App from the serial terminal? > > > > > > I tried doing it but it doesn't draw the rectangle. > > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > > > Does anybody know why I got this error? I would appreciate the > reply. > > > > > > Note: > > > I could draw the rectangle by typing following command on pterm > "pterm > > > -x10 -y10 -height100 -width100". > > > > > > One final question. Is there a way to display the QNX home screen on > > the > > > LCD panel? If yes, then how? > > > > > > Regards, > > > > > > > No Derek, it is running in foreground. > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## START OF BUILD SCRIPT > > > > > > > > > > ######################################################################## > > > ### > > > > > > > > [image=0x80010000] > > > > [+compress] > > > > #[virtual=armle,binary] .bootstrap = { > > > > [virtual=armle,raw] .bootstrap = { > > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > > > > > ####################################################################### > > > > ## PATH set here is the *safe* path for executables. > > > > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > > > > ## i.e. These are the paths searched by setuid/setgid > > > binaries. > > > > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > > > > > > > > > > ####################################################################### > > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont > > > procnto-v6 > > > > } > > > > [+script] .script = { > > > > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > > Instruments > > > > OMAP2430SDP Board > > > > > > > > > > > > > > ####################################################################### > > > > ## SERIAL driver > > > > > > > > > > ####################################################################### > > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > > waitfor /dev/ser1 4 > > > > reopen /dev/ser1 > > > > > > > > slogger > > > > pipe > > > > > > > > > > > > > > ####################################################################### > > > > ## NAND_ETFS driver > > > > > > > > > > ####################################################################### > > > > #display_msg Starting etfs driver... > > > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > > > > > > ####################################################################### > > > > ## NETWORK driver > > > > > > > > > > ####################################################################### > > > > # > > > > #display_msg Starting on-board ethernet with TCP/IP stack... > > > > # > > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > > # > > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > > > > > > ####################################################################### > > > > ## I2C driver > > > > ## - Required for both USB and AUDIO > > > > > > > > > > ####################################################################### > > > > display_msg Starting I2C driver... > > > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > > waitfor /dev/i2c0 5 > > > > > > > > > > > > > > ####################################################################### > > > > ## USB driver > > > > ## - Requires the I2C driver to be running > > > > > > > > > > ####################################################################### > > > > #display_msg Starting USB stack... > > > > > > > > #omap2420sdp_usb_init > > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > > > > > > ####################################################################### > > > > ## input > > > > > > > > > > ####################################################################### > > > > #display_msg Starting Keypad driver... > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > ####################################################################### > > > > ## These env variables are inherited by all the programs which > > > follow > > > > > > > > > > ####################################################################### > > > > SYSNAME=nto > > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > > PHOTON_PATH=/usr/photon > > > > PHOTON=/dev/photon > > > > PHFONT=/dev/phfont > > > > TERM=qansi > > > > HOME=/ > > > > > > > > > > > > ###################################################################### > > > > # > > > > ## GRAPHICS > > > > > > > > > > ####################################################################### > > > > display_msg Starting io-display... > > > > > > > > io-display -dvid=0,did=0 > > > > waitfor /dev/io-display 10 > > > > > > > > > > > > > > ####################################################################### > > > > ## Photon and Phfont > > > > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS > > > driver > > > > > > > > > > ####################################################################### > > > > display_msg Starting Photon... > > > > Photon & > > > > waitfor /dev/photon 10 > > > > display_msg Starting Phfont... > > > > Phfont & > > > > waitfor /proc/boot/phfont 10 > > > > display_msg Starting io-graphics... > > > > io-graphics > > > > display_msg Starting PWM... > > > > pwm & > > > > display_msg Starting DEVC-PTY... > > > > devc-pty & > > > > display_msg Starting PTERM... > > > > pterm > > > > display_msg Starting BKGDMGR... > > > > bkgdmgr > > > > sloginfo > > > > > > > > > > > > > > ####################################################################### > > > > ## input > > > > > > > > > > ####################################################################### > > > > #display_msg Starting Keypad driver... > > > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > > > > > > [+session] ksh & > > > > } > > > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > > [type=link] /dev/console=/dev/ser1 > > > > [type=link] /tmp=/dev/shmem > > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for legacy binary support (Momentics 6.3.2 and > earlier) > > > > > > > > > > > > ######################################################################## > > > ### > > > > #libc.so.2 > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for standard libs > > > > > > > > > > ######################################################################## > > > ### > > > > libc.so > > > > libm.so > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for photon libs (GRAPHICS) > > > > > > > > > > ######################################################################## > > > ### > > > > libph.so > > > > libAp.so > > > > libphexlib.so > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for GRAPHICS driver > > > > > > > > > > ######################################################################## > > > ### > > > > devg-omap35xx.so > > > > libgf.so > > > > libGLES_CM.so > > > > libimg.so > > > > gri-photon.so > > > > libphrender.so > > > > libgri.so > > > > libdisputil.so > > > > libffb.so > > > > libgf.so.1 > > > > libGLES_CL.so.1 > > > > > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > > ttings > > > > > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > > .pal > > > > > > > > > > > > [data=c] > > > > devc-seromap > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > ## > > > > ## font libs (GRAPHICS) > > > > > > > > > > ######################################################################## > > > ## > > > > devg-svga.so > > > > /etc/system/config/omap35xx.conf = > > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > > /lib/dll/font/ttfFFcore.so = > > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > > /lib/dll/font/PHFcore.so = > > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > > /lib/dll/font/FCcore.so = > ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > > libfontharnessutils.so > > > > libfontutils.so > > > > libblkcache.so > > > > libFF-T2K.so > > > > libFF-T2K-cache.so > > > > libFF-T2K-fm.so > > > > libfont.so > > > > phfont.so > > > > > > > > > > > > > > ######################################################################## > > > ## > > > > ## font config (GRAPHICS) > > > > > > > > > > ######################################################################## > > > ## > > > > /usr/photon/font_repository/tt2009m_.ttf = > > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > > /usr/photon/font_repository/phcursor.phf = > > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > > /usr/photon/font_repository/mappings = > > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > > /usr/photon/font_repository/fontopts = > > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > > /usr/photon/font_repository/fontkey = > > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > > > /usr/photon/font_repository/fontdir = { > > > > ; > > > > ; fontdir config file > > > > ; > > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > > BT,0,,0020-F002,f,79x170,109K > > > > } > > > > > > > > /usr/photon/font_repository/fontext = { > > > > ; > > > > ; fontext config file > > > > ; > > > > +normal = primasansmonobts, phcursor > > > > } > > > > > > > > /proc/boot/font_repository/fontdesc={ > > > > [SANSERIF] > > > > PrimaSansMono BT > > > > } > > > > > > > > /usr/photon/font_repository/fontmap = { > > > > ; > > > > ; fontmap config file > > > > ; > > > > ? = primasansmonobts > > > > } > > > > > > > > /usr/photon/config/wm/wm.menu={ > > > > =Desktop Menu > > > > Terminal T pterm > > > > Calculator C phcalc_sm > > > > } > > > > > > > > > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for NETWORK driver > > > > > > > > > > ######################################################################## > > > ### > > > > devn-smc9000.so > > > > libsocket.so > > > > devnp-shim.so > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for USB driver > > > > > > > > > > ######################################################################## > > > ### > > > > libusbdi.so > > > > devu-ohci.so > > > > > > > > ##################################### > > > > #input driver > > > > ###################################### > > > > devi-omap_keypad > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## Needed for Photon > > > > > > > > > > ######################################################################## > > > ### > > > > devc-pty > > > > ksh > > > > slogger > > > > sloginfo > > > > Photon > > > > io-graphics > > > > io-display > > > > devi-hirun > > > > phfont > > > > pwm > > > > # photon applications required to be unstriped by mkifs, hence > these > > > have > > > > # +raw tag to tell mkifs not to strip them > > > > [+raw] /usr/photon/bin/pterm = pterm > > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > > > # allow pterm to save its configuration to RAM, if the user > changes > > > it. > > > > [type=link] /.ph/pterm = /dev/shmem > > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for etfs driver > > > > > > > > > > ######################################################################## > > > ### > > > > fs-etfs-omap2420 > > > > etfsctl > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for I2C driver > > > > > > > > > > ######################################################################## > > > ### > > > > i2c-omap59xx > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for NETWORK driver > > > > > > > > > > ######################################################################## > > > ### > > > > io-pkt-v4 > > > > nicinfo > > > > ifconfig > > > > ping > > > > cat > > > > fs-nfs2 > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for USB driver > > > > > > > > > > ######################################################################## > > > ### > > > > io-usb > > > > omap2420sdp_usb_init > > > > usb > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## uncomment for Graphics driver > > > > > > > > > > ######################################################################## > > > ### > > > > vsync > > > > egl-gears-lite > > > > io-display > > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > > /etc/system/config/display.conf={ > > > > device \{ > > > > drivername=omap35xx > > > > vid=0 > > > > did=0 > > > > modeopts=/etc/system/config/omap35xx.conf > > > > display \{ > > > > xres=240 > > > > yres=320 > > > > refresh=60 > > > > pixel_format=rgb565 > > > > photon \{ > > > > enabled=1 > > > > xoffset=0 > > > > yoffset=0 > > > > cursor=software > > > > input_group=1 > > > > \} > > > > > > > > \} > > > > \} > > > > } > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## general commands > > > > > > > > > > ######################################################################## > > > ### > > > > ls > > > > ksh > > > > pipe > > > > pidin > > > > uname > > > > slogger > > > > sloginfo > > > > slay > > > > cp > > > > chmod > > > > waitfor > > > > shutdown > > > > > > > > ##i2c utility > > > > i2c-reg > > > > > > > > > > > > > > ######################################################################## > > > ### > > > > ## END OF BUILD SCRIPT > > > > > > > > > > ######################################################################## > > > ### > > > > > > > > ## GRAPHICS: > > > > ## example buildfile commands: > > > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > > > -pphoton > > > > ## > > > > ## > > > > ## required libraries: > > > > ## Please refer to the photon embedding documentation > > > > ## > > > > ## required binaries: > > > > ## Please refer to the photon embedding documentation > > > > ## > > > > ## > > > > > > > > > > ------------------------------------------------------------------------ > > > -- > > > > > Are you running the pterm in the background? pterm & > > > > > > > > > > -----Original Message----- > > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > > Sent: February 8, 2011 12:26 PM > > > > > To: advanced-graphics > > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > > > Thanks Derek for the reply. > > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > > > As I mentioned I am not populating the layer_flushrect(), but > you > > > are > > > > > right I could be getting the continuous calls because my cursor > is > > > > > blinking. > > > > > > > > > > You are absolutely right about "minicom". I am using a serial > > > terminal > > > > > to launch the Pterm utility. I am not sure on what priority my > > > serial > > > > > driver is running on. > > > > > > > > > > I would appreciate Derek if you could look at the attached files > > and > > > see > > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Advanced Graphics > > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post83023 > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83038 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83041 Thu, 10 Feb 2011 16:51:22 GMT http://community.qnx.com/sf/go/post83091 Raj Pandey 2011-02-10T16:51:22Z http://community.qnx.com/sf/go/post83071 Depends how soon you want it to come up ... do you want it immediate, or once io-display is running, or is it OK to wait until Photon is booted? Immediate is much more difficult. If once io-display is running, just run a GF application on a layer that is behind the layer that Photon will use (if you have more than one layer). You can slay it off later. If after Photon has booted, just run you Photon application before any other Photon applications. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 9, 2011 12:20 PM To: advanced-graphics Subject: Re: RE: RE: RE: RE: Display Hanging after Pterm Utility Thanks Again Derek for the reply. Appreciated it very much. I'll work on hybrid application tomorrow. Is there a way to display QNX homescreen like all the other OS does ,e.g Linux shows a "penguin" or WindowsCE/Mobile shows their logo during/after boot up? Regards, Raj > Ok, you will need to run it on a different layer than Photon, or turn > your application into a Photon/GF hybrid application. Examples of > hybrid applications can be found at: > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > ton.gf_ph_2d > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 9, 2011 11:37 AM > To: advanced-graphics > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > Thanks for the reply Derek. It is a GF application and not the Photon > one. > > > Is this rectangle application a GF or a Photon application? > > > > No, there is no need to run it from pterm. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 9, 2011 8:49 AM > > To: advanced-graphics > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > I got the Pterm working. I ran the Pterm in background and I could see > > the blinking cursor and I can type the commands in serial terminal. > > > > I created one simple app to draw a rectangle and I am trying to launch > > this app from the serial terminal and not the Pterm. I have put that > > application in /src/utils/ folder. The application is there in the > > image. > > > > I have two question regarding this. > > > > i) Do I need to launch the app from the Pterm? > > If yes, then I will need an input driver. > > > > ii) Can I launch that App from the serial terminal? > > > > I tried doing it but it doesn't draw the rectangle. > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > Does anybody know why I got this error? I would appreciate the reply. > > > > Note: > > I could draw the rectangle by typing following command on pterm "pterm > > -x10 -y10 -height100 -width100". > > > > One final question. Is there a way to display the QNX home screen on > the > > LCD panel? If yes, then how? > > > > Regards, > > > > > No Derek, it is running in foreground. > > > > > > > > > ######################################################################## > > ### > > > ## START OF BUILD SCRIPT > > > > > > ######################################################################## > > ### > > > > > > [image=0x80010000] > > > [+compress] > > > #[virtual=armle,binary] .bootstrap = { > > > [virtual=armle,raw] .bootstrap = { > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > ####################################################################### > > > ## PATH set here is the *safe* path for executables. > > > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > > > ## i.e. These are the paths searched by setuid/setgid > > binaries. > > > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > > > > > > ####################################################################### > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont > > procnto-v6 > > > } > > > [+script] .script = { > > > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > Instruments > > > OMAP2430SDP Board > > > > > > > > > ####################################################################### > > > ## SERIAL driver > > > > > > ####################################################################### > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > waitfor /dev/ser1 4 > > > reopen /dev/ser1 > > > > > > slogger > > > pipe > > > > > > > > > ####################################################################### > > > ## NAND_ETFS driver > > > > > > ####################################################################### > > > #display_msg Starting etfs driver... > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > ####################################################################### > > > ## NETWORK driver > > > > > > ####################################################################### > > > # > > > #display_msg Starting on-board ethernet with TCP/IP stack... > > > # > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > # > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > ####################################################################### > > > ## I2C driver > > > ## - Required for both USB and AUDIO > > > > > > ####################################################################### > > > display_msg Starting I2C driver... > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > waitfor /dev/i2c0 5 > > > > > > > > > ####################################################################### > > > ## USB driver > > > ## - Requires the I2C driver to be running > > > > > > ####################################################################### > > > #display_msg Starting USB stack... > > > > > > #omap2420sdp_usb_init > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > ####################################################################### > > > ## input > > > > > > ####################################################################### > > > #display_msg Starting Keypad driver... > > > > > > #devi-omap_keypad keypad > > > > > > > > > ####################################################################### > > > ## These env variables are inherited by all the programs which > > follow > > > > > > ####################################################################### > > > SYSNAME=nto > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > PHOTON_PATH=/usr/photon > > > PHOTON=/dev/photon > > > PHFONT=/dev/phfont > > > TERM=qansi > > > HOME=/ > > > > > > > > ###################################################################### > > > # > > > ## GRAPHICS > > > > > > ####################################################################### > > > display_msg Starting io-display... > > > > > > io-display -dvid=0,did=0 > > > waitfor /dev/io-display 10 > > > > > > > > > ####################################################################### > > > ## Photon and Phfont > > > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS > > driver > > > > > > ####################################################################### > > > display_msg Starting Photon... > > > Photon & > > > waitfor /dev/photon 10 > > > display_msg Starting Phfont... > > > Phfont & > > > waitfor /proc/boot/phfont 10 > > > display_msg Starting io-graphics... > > > io-graphics > > > display_msg Starting PWM... > > > pwm & > > > display_msg Starting DEVC-PTY... > > > devc-pty & > > > display_msg Starting PTERM... > > > pterm > > > display_msg Starting BKGDMGR... > > > bkgdmgr > > > sloginfo > > > > > > > > > ####################################################################### > > > ## input > > > > > > ####################################################################### > > > #display_msg Starting Keypad driver... > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > [+session] ksh & > > > } > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > [type=link] /dev/console=/dev/ser1 > > > [type=link] /tmp=/dev/shmem > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) > > > > > > > ######################################################################## > > ### > > > #libc.so.2 > > > > > > ######################################################################## > > ### > > > ## uncomment for standard libs > > > > > > ######################################################################## > > ### > > > libc.so > > > libm.so > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for photon libs (GRAPHICS) > > > > > > ######################################################################## > > ### > > > libph.so > > > libAp.so > > > libphexlib.so > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for GRAPHICS driver > > > > > > ######################################################################## > > ### > > > devg-omap35xx.so > > > libgf.so > > > libGLES_CM.so > > > libimg.so > > > gri-photon.so > > > libphrender.so > > > libgri.so > > > libdisputil.so > > > libffb.so > > > libgf.so.1 > > > libGLES_CL.so.1 > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > ttings > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > .pal > > > > > > > > > [data=c] > > > devc-seromap > > > > > > > > > > > > > > > ######################################################################## > > ## > > > ## font libs (GRAPHICS) > > > > > > ######################################################################## > > ## > > > devg-svga.so > > > /etc/system/config/omap35xx.conf = > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > /lib/dll/font/ttfFFcore.so = > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > /lib/dll/font/PHFcore.so = > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > libfontharnessutils.so > > > libfontutils.so > > > libblkcache.so > > > libFF-T2K.so > > > libFF-T2K-cache.so > > > libFF-T2K-fm.so > > > libfont.so > > > phfont.so > > > > > > > > > ######################################################################## > > ## > > > ## font config (GRAPHICS) > > > > > > ######################################################################## > > ## > > > /usr/photon/font_repository/tt2009m_.ttf = > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > /usr/photon/font_repository/phcursor.phf = > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > /usr/photon/font_repository/mappings = > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > /usr/photon/font_repository/fontopts = > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > /usr/photon/font_repository/fontkey = > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > /usr/photon/font_repository/fontdir = { > > > ; > > > ; fontdir config file > > > ; > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > BT,0,,0020-F002,f,79x170,109K > > > } > > > > > > /usr/photon/font_repository/fontext = { > > > ; > > > ; fontext config file > > > ; > > > +normal = primasansmonobts, phcursor > > > } > > > > > > /proc/boot/font_repository/fontdesc={ > > > [SANSERIF] > > > PrimaSansMono BT > > > } > > > > > > /usr/photon/font_repository/fontmap = { > > > ; > > > ; fontmap config file > > > ; > > > ? = primasansmonobts > > > } > > > > > > /usr/photon/config/wm/wm.menu={ > > > =Desktop Menu > > > Terminal T pterm > > > Calculator C phcalc_sm > > > } > > > > > > > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for NETWORK driver > > > > > > ######################################################################## > > ### > > > devn-smc9000.so > > > libsocket.so > > > devnp-shim.so > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for USB driver > > > > > > ######################################################################## > > ### > > > libusbdi.so > > > devu-ohci.so > > > > > > ##################################### > > > #input driver > > > ###################################### > > > devi-omap_keypad > > > > > > > > > ######################################################################## > > ### > > > ## Needed for Photon > > > > > > ######################################################################## > > ### > > > devc-pty > > > ksh > > > slogger > > > sloginfo > > > Photon > > > io-graphics > > > io-display > > > devi-hirun > > > phfont > > > pwm > > > # photon applications required to be unstriped by mkifs, hence these > > have > > > # +raw tag to tell mkifs not to strip them > > > [+raw] /usr/photon/bin/pterm = pterm > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > # allow pterm to save its configuration to RAM, if the user changes > > it. > > > [type=link] /.ph/pterm = /dev/shmem > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for etfs driver > > > > > > ######################################################################## > > ### > > > fs-etfs-omap2420 > > > etfsctl > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for I2C driver > > > > > > ######################################################################## > > ### > > > i2c-omap59xx > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for NETWORK driver > > > > > > ######################################################################## > > ### > > > io-pkt-v4 > > > nicinfo > > > ifconfig > > > ping > > > cat > > > fs-nfs2 > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for USB driver > > > > > > ######################################################################## > > ### > > > io-usb > > > omap2420sdp_usb_init > > > usb > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for Graphics driver > > > > > > ######################################################################## > > ### > > > vsync > > > egl-gears-lite > > > io-display > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > /etc/system/config/display.conf={ > > > device \{ > > > drivername=omap35xx > > > vid=0 > > > did=0 > > > modeopts=/etc/system/config/omap35xx.conf > > > display \{ > > > xres=240 > > > yres=320 > > > refresh=60 > > > pixel_format=rgb565 > > > photon \{ > > > enabled=1 > > > xoffset=0 > > > yoffset=0 > > > cursor=software > > > input_group=1 > > > \} > > > > > > \} > > > \} > > > } > > > > > > > > > ######################################################################## > > ### > > > ## general commands > > > > > > ######################################################################## > > ### > > > ls > > > ksh > > > pipe > > > pidin > > > uname > > > slogger > > > sloginfo > > > slay > > > cp > > > chmod > > > waitfor > > > shutdown > > > > > > ##i2c utility > > > i2c-reg > > > > > > > > > ######################################################################## > > ### > > > ## END OF BUILD SCRIPT > > > > > > ######################################################################## > > ### > > > > > > ## GRAPHICS: > > > ## example buildfile commands: > > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > > -pphoton > > > ## > > > ## > > > ## required libraries: > > > ## Please refer to the photon embedding documentation > > > ## > > > ## required binaries: > > > ## Please refer to the photon embedding documentation > > > ## > > > ## > > > > > > ------------------------------------------------------------------------ > > -- > > > > Are you running the pterm in the background? pterm & > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 8, 2011 12:26 PM > > > > To: advanced-graphics > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > Thanks Derek for the reply. > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > As I mentioned I am not populating the layer_flushrect(), but you > > are > > > > right I could be getting the continuous calls because my cursor is > > > > blinking. > > > > > > > > You are absolutely right about "minicom". I am using a serial > > terminal > > > > to launch the Pterm utility. I am not sure on what priority my > > serial > > > > driver is running on. > > > > > > > > I would appreciate Derek if you could look at the attached files > and > > see > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83023 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83038 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83041 Thu, 10 Feb 2011 13:22:56 GMT http://community.qnx.com/sf/go/post83071 Derek Leach 2011-02-10T13:22:56Z http://community.qnx.com/sf/go/post83041 Thanks Again Derek for the reply. Appreciated it very much. I'll work on hybrid application tomorrow. Is there a way to display QNX homescreen like all the other OS does ,e.g Linux shows a "penguin" or WindowsCE/Mobile shows their logo during/after boot up? Regards, Raj > Ok, you will need to run it on a different layer than Photon, or turn > your application into a Photon/GF hybrid application. Examples of > hybrid applications can be found at: > > http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho > ton.gf_ph_2d > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 9, 2011 11:37 AM > To: advanced-graphics > Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility > > Thanks for the reply Derek. It is a GF application and not the Photon > one. > > > Is this rectangle application a GF or a Photon application? > > > > No, there is no need to run it from pterm. > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 9, 2011 8:49 AM > > To: advanced-graphics > > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > > > I got the Pterm working. I ran the Pterm in background and I could see > > the blinking cursor and I can type the commands in serial terminal. > > > > I created one simple app to draw a rectangle and I am trying to launch > > this app from the serial terminal and not the Pterm. I have put that > > application in /src/utils/ folder. The application is there in the > > image. > > > > I have two question regarding this. > > > > i) Do I need to launch the app from the Pterm? > > If yes, then I will need an input driver. > > > > ii) Can I launch that App from the serial terminal? > > > > I tried doing it but it doesn't draw the rectangle. > > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > > > Does anybody know why I got this error? I would appreciate the reply. > > > > Note: > > I could draw the rectangle by typing following command on pterm "pterm > > -x10 -y10 -height100 -width100". > > > > One final question. Is there a way to display the QNX home screen on > the > > LCD panel? If yes, then how? > > > > Regards, > > > > > No Derek, it is running in foreground. > > > > > > > > > ######################################################################## > > ### > > > ## START OF BUILD SCRIPT > > > > > > ######################################################################## > > ### > > > > > > [image=0x80010000] > > > [+compress] > > > #[virtual=armle,binary] .bootstrap = { > > > [virtual=armle,raw] .bootstrap = { > > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > > > > ####################################################################### > > > ## PATH set here is the *safe* path for executables. > > > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > > > ## i.e. These are the paths searched by setuid/setgid > > binaries. > > > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > > > > > > ####################################################################### > > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont > > procnto-v6 > > > } > > > [+script] .script = { > > > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > > Instruments > > > OMAP2430SDP Board > > > > > > > > > ####################################################################### > > > ## SERIAL driver > > > > > > ####################################################################### > > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > > waitfor /dev/ser1 4 > > > reopen /dev/ser1 > > > > > > slogger > > > pipe > > > > > > > > > ####################################################################### > > > ## NAND_ETFS driver > > > > > > ####################################################################### > > > #display_msg Starting etfs driver... > > > > > > #fs-etfs-omap2420 -r4096 > > > > > > > > > ####################################################################### > > > ## NETWORK driver > > > > > > ####################################################################### > > > # > > > #display_msg Starting on-board ethernet with TCP/IP stack... > > > # > > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > > # > > > #waitfor /dev/io-net/en0 4 > > > > > > > > > ####################################################################### > > > ## I2C driver > > > ## - Required for both USB and AUDIO > > > > > > ####################################################################### > > > display_msg Starting I2C driver... > > > > > > i2c-omap59xx -p0x48072000 -i56 > > > waitfor /dev/i2c0 5 > > > > > > > > > ####################################################################### > > > ## USB driver > > > ## - Requires the I2C driver to be running > > > > > > ####################################################################### > > > #display_msg Starting USB stack... > > > > > > #omap2420sdp_usb_init > > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > > > > > ####################################################################### > > > ## input > > > > > > ####################################################################### > > > #display_msg Starting Keypad driver... > > > > > > #devi-omap_keypad keypad > > > > > > > > > ####################################################################### > > > ## These env variables are inherited by all the programs which > > follow > > > > > > ####################################################################### > > > SYSNAME=nto > > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > > PHOTON_PATH=/usr/photon > > > PHOTON=/dev/photon > > > PHFONT=/dev/phfont > > > TERM=qansi > > > HOME=/ > > > > > > > > ###################################################################### > > > # > > > ## GRAPHICS > > > > > > ####################################################################### > > > display_msg Starting io-display... > > > > > > io-display -dvid=0,did=0 > > > waitfor /dev/io-display 10 > > > > > > > > > ####################################################################### > > > ## Photon and Phfont > > > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS > > driver > > > > > > ####################################################################### > > > display_msg Starting Photon... > > > Photon & > > > waitfor /dev/photon 10 > > > display_msg Starting Phfont... > > > Phfont & > > > waitfor /proc/boot/phfont 10 > > > display_msg Starting io-graphics... > > > io-graphics > > > display_msg Starting PWM... > > > pwm & > > > display_msg Starting DEVC-PTY... > > > devc-pty & > > > display_msg Starting PTERM... > > > pterm > > > display_msg Starting BKGDMGR... > > > bkgdmgr > > > sloginfo > > > > > > > > > ####################################################################### > > > ## input > > > > > > ####################################################################### > > > #display_msg Starting Keypad driver... > > > > > > #devi-omap_keypad keypad > > > > > > > > > > > > > > > [+session] ksh & > > > } > > > > > > [type=link] /bin/sh=/proc/boot/ksh > > > [type=link] /dev/console=/dev/ser1 > > > [type=link] /tmp=/dev/shmem > > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) > > > > > > > ######################################################################## > > ### > > > #libc.so.2 > > > > > > ######################################################################## > > ### > > > ## uncomment for standard libs > > > > > > ######################################################################## > > ### > > > libc.so > > > libm.so > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for photon libs (GRAPHICS) > > > > > > ######################################################################## > > ### > > > libph.so > > > libAp.so > > > libphexlib.so > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for GRAPHICS driver > > > > > > ######################################################################## > > ### > > > devg-omap35xx.so > > > libgf.so > > > libGLES_CM.so > > > libimg.so > > > gri-photon.so > > > libphrender.so > > > libgri.so > > > libdisputil.so > > > libffb.so > > > libgf.so.1 > > > libGLES_CL.so.1 > > > > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > > ttings > > > > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > > .pal > > > > > > > > > [data=c] > > > devc-seromap > > > > > > > > > > > > > > > ######################################################################## > > ## > > > ## font libs (GRAPHICS) > > > > > > ######################################################################## > > ## > > > devg-svga.so > > > /etc/system/config/omap35xx.conf = > > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > > /lib/dll/font/ttfFFcore.so = > > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > > /lib/dll/font/PHFcore.so = > ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > > /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > > libfontharnessutils.so > > > libfontutils.so > > > libblkcache.so > > > libFF-T2K.so > > > libFF-T2K-cache.so > > > libFF-T2K-fm.so > > > libfont.so > > > phfont.so > > > > > > > > > ######################################################################## > > ## > > > ## font config (GRAPHICS) > > > > > > ######################################################################## > > ## > > > /usr/photon/font_repository/tt2009m_.ttf = > > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > > /usr/photon/font_repository/phcursor.phf = > > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > > /usr/photon/font_repository/mappings = > > ${QNX_TARGET}/usr/photon/font_repository/mappings > > > /usr/photon/font_repository/fontopts = > > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > > /usr/photon/font_repository/fontkey = > > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > > > /usr/photon/font_repository/fontdir = { > > > ; > > > ; fontdir config file > > > ; > > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > > BT,0,,0020-F002,f,79x170,109K > > > } > > > > > > /usr/photon/font_repository/fontext = { > > > ; > > > ; fontext config file > > > ; > > > +normal = primasansmonobts, phcursor > > > } > > > > > > /proc/boot/font_repository/fontdesc={ > > > [SANSERIF] > > > PrimaSansMono BT > > > } > > > > > > /usr/photon/font_repository/fontmap = { > > > ; > > > ; fontmap config file > > > ; > > > ? = primasansmonobts > > > } > > > > > > /usr/photon/config/wm/wm.menu={ > > > =Desktop Menu > > > Terminal T pterm > > > Calculator C phcalc_sm > > > } > > > > > > > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for NETWORK driver > > > > > > ######################################################################## > > ### > > > devn-smc9000.so > > > libsocket.so > > > devnp-shim.so > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for USB driver > > > > > > ######################################################################## > > ### > > > libusbdi.so > > > devu-ohci.so > > > > > > ##################################### > > > #input driver > > > ###################################### > > > devi-omap_keypad > > > > > > > > > ######################################################################## > > ### > > > ## Needed for Photon > > > > > > ######################################################################## > > ### > > > devc-pty > > > ksh > > > slogger > > > sloginfo > > > Photon > > > io-graphics > > > io-display > > > devi-hirun > > > phfont > > > pwm > > > # photon applications required to be unstriped by mkifs, hence these > > have > > > # +raw tag to tell mkifs not to strip them > > > [+raw] /usr/photon/bin/pterm = pterm > > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > > > # allow pterm to save its configuration to RAM, if the user changes > > it. > > > [type=link] /.ph/pterm = /dev/shmem > > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for etfs driver > > > > > > ######################################################################## > > ### > > > fs-etfs-omap2420 > > > etfsctl > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for I2C driver > > > > > > ######################################################################## > > ### > > > i2c-omap59xx > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for NETWORK driver > > > > > > ######################################################################## > > ### > > > io-pkt-v4 > > > nicinfo > > > ifconfig > > > ping > > > cat > > > fs-nfs2 > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for USB driver > > > > > > ######################################################################## > > ### > > > io-usb > > > omap2420sdp_usb_init > > > usb > > > > > > > > > ######################################################################## > > ### > > > ## uncomment for Graphics driver > > > > > > ######################################################################## > > ### > > > vsync > > > egl-gears-lite > > > io-display > > > /etc/system/config/omap35xx.conf=omap35xx.conf > > > /etc/system/config/display.conf={ > > > device \{ > > > drivername=omap35xx > > > vid=0 > > > did=0 > > > modeopts=/etc/system/config/omap35xx.conf > > > display \{ > > > xres=240 > > > yres=320 > > > refresh=60 > > > pixel_format=rgb565 > > > photon \{ > > > enabled=1 > > > xoffset=0 > > > yoffset=0 > > > cursor=software > > > input_group=1 > > > \} > > > > > > \} > > > \} > > > } > > > > > > > > > ######################################################################## > > ### > > > ## general commands > > > > > > ######################################################################## > > ### > > > ls > > > ksh > > > pipe > > > pidin > > > uname > > > slogger > > > sloginfo > > > slay > > > cp > > > chmod > > > waitfor > > > shutdown > > > > > > ##i2c utility > > > i2c-reg > > > > > > > > > ######################################################################## > > ### > > > ## END OF BUILD SCRIPT > > > > > > ######################################################################## > > ### > > > > > > ## GRAPHICS: > > > ## example buildfile commands: > > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > > -pphoton > > > ## > > > ## > > > ## required libraries: > > > ## Please refer to the photon embedding documentation > > > ## > > > ## required binaries: > > > ## Please refer to the photon embedding documentation > > > ## > > > ## > > > > > > ------------------------------------------------------------------------ > > -- > > > > Are you running the pterm in the background? pterm & > > > > > > > > -----Original Message----- > > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > > Sent: February 8, 2011 12:26 PM > > > > To: advanced-graphics > > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > > > Thanks Derek for the reply. > > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > > > As I mentioned I am not populating the layer_flushrect(), but you > > are > > > > right I could be getting the continuous calls because my cursor is > > > > blinking. > > > > > > > > You are absolutely right about "minicom". I am using a serial > > terminal > > > > to launch the Pterm utility. I am not sure on what priority my > > serial > > > > driver is running on. > > > > > > > > I would appreciate Derek if you could look at the attached files > and > > see > > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Advanced Graphics > > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post83023 > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83038 Wed, 09 Feb 2011 17:20:01 GMT http://community.qnx.com/sf/go/post83041 Raj Pandey 2011-02-09T17:20:01Z http://community.qnx.com/sf/go/post83039 Ok, you will need to run it on a different layer than Photon, or turn your application into a Photon/GF hybrid application. Examples of hybrid applications can be found at: http://community.qnx.com/sf/frs/do/viewRelease/projects.graphics/frs.pho ton.gf_ph_2d -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 9, 2011 11:37 AM To: advanced-graphics Subject: Re: RE: RE: RE: Display Hanging after Pterm Utility Thanks for the reply Derek. It is a GF application and not the Photon one. > Is this rectangle application a GF or a Photon application? > > No, there is no need to run it from pterm. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 9, 2011 8:49 AM > To: advanced-graphics > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > I got the Pterm working. I ran the Pterm in background and I could see > the blinking cursor and I can type the commands in serial terminal. > > I created one simple app to draw a rectangle and I am trying to launch > this app from the serial terminal and not the Pterm. I have put that > application in /src/utils/ folder. The application is there in the > image. > > I have two question regarding this. > > i) Do I need to launch the app from the Pterm? > If yes, then I will need an input driver. > > ii) Can I launch that App from the serial terminal? > > I tried doing it but it doesn't draw the rectangle. > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > Does anybody know why I got this error? I would appreciate the reply. > > Note: > I could draw the rectangle by typing following command on pterm "pterm > -x10 -y10 -height100 -width100". > > One final question. Is there a way to display the QNX home screen on the > LCD panel? If yes, then how? > > Regards, > > > No Derek, it is running in foreground. > > > > > ######################################################################## > ### > > ## START OF BUILD SCRIPT > > > ######################################################################## > ### > > > > [image=0x80010000] > > [+compress] > > #[virtual=armle,binary] .bootstrap = { > > [virtual=armle,raw] .bootstrap = { > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > ####################################################################### > > ## PATH set here is the *safe* path for executables. > > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > > ## i.e. These are the paths searched by setuid/setgid > binaries. > > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > > > ####################################################################### > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont > procnto-v6 > > } > > [+script] .script = { > > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > Instruments > > OMAP2430SDP Board > > > > > ####################################################################### > > ## SERIAL driver > > > ####################################################################### > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > waitfor /dev/ser1 4 > > reopen /dev/ser1 > > > > slogger > > pipe > > > > > ####################################################################### > > ## NAND_ETFS driver > > > ####################################################################### > > #display_msg Starting etfs driver... > > > > #fs-etfs-omap2420 -r4096 > > > > > ####################################################################### > > ## NETWORK driver > > > ####################################################################### > > # > > #display_msg Starting on-board ethernet with TCP/IP stack... > > # > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > # > > #waitfor /dev/io-net/en0 4 > > > > > ####################################################################### > > ## I2C driver > > ## - Required for both USB and AUDIO > > > ####################################################################### > > display_msg Starting I2C driver... > > > > i2c-omap59xx -p0x48072000 -i56 > > waitfor /dev/i2c0 5 > > > > > ####################################################################### > > ## USB driver > > ## - Requires the I2C driver to be running > > > ####################################################################### > > #display_msg Starting USB stack... > > > > #omap2420sdp_usb_init > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > ####################################################################### > > ## input > > > ####################################################################### > > #display_msg Starting Keypad driver... > > > > #devi-omap_keypad keypad > > > > > ####################################################################### > > ## These env variables are inherited by all the programs which > follow > > > ####################################################################### > > SYSNAME=nto > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > PHOTON_PATH=/usr/photon > > PHOTON=/dev/photon > > PHFONT=/dev/phfont > > TERM=qansi > > HOME=/ > > > > > ###################################################################### > > # > > ## GRAPHICS > > > ####################################################################### > > display_msg Starting io-display... > > > > io-display -dvid=0,did=0 > > waitfor /dev/io-display 10 > > > > > ####################################################################### > > ## Photon and Phfont > > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS > driver > > > ####################################################################### > > display_msg Starting Photon... > > Photon & > > waitfor /dev/photon 10 > > display_msg Starting Phfont... > > Phfont & > > waitfor /proc/boot/phfont 10 > > display_msg Starting io-graphics... > > io-graphics > > display_msg Starting PWM... > > pwm & > > display_msg Starting DEVC-PTY... > > devc-pty & > > display_msg Starting PTERM... > > pterm > > display_msg Starting BKGDMGR... > > bkgdmgr > > sloginfo > > > > > ####################################################################### > > ## input > > > ####################################################################### > > #display_msg Starting Keypad driver... > > > > #devi-omap_keypad keypad > > > > > > > > > > [+session] ksh & > > } > > > > [type=link] /bin/sh=/proc/boot/ksh > > [type=link] /dev/console=/dev/ser1 > > [type=link] /tmp=/dev/shmem > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > ######################################################################## > ### > > ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) > > > ######################################################################## > ### > > #libc.so.2 > > > ######################################################################## > ### > > ## uncomment for standard libs > > > ######################################################################## > ### > > libc.so > > libm.so > > > > > ######################################################################## > ### > > ## uncomment for photon libs (GRAPHICS) > > > ######################################################################## > ### > > libph.so > > libAp.so > > libphexlib.so > > > > > ######################################################################## > ### > > ## uncomment for GRAPHICS driver > > > ######################################################################## > ### > > devg-omap35xx.so > > libgf.so > > libGLES_CM.so > > libimg.so > > gri-photon.so > > libphrender.so > > libgri.so > > libdisputil.so > > libffb.so > > libgf.so.1 > > libGLES_CL.so.1 > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > ttings > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > .pal > > > > > > [data=c] > > devc-seromap > > > > > > > > > ######################################################################## > ## > > ## font libs (GRAPHICS) > > > ######################################################################## > ## > > devg-svga.so > > /etc/system/config/omap35xx.conf = > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > /lib/dll/font/ttfFFcore.so = > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > /lib/dll/font/PHFcore.so = ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > libfontharnessutils.so > > libfontutils.so > > libblkcache.so > > libFF-T2K.so > > libFF-T2K-cache.so > > libFF-T2K-fm.so > > libfont.so > > phfont.so > > > > > ######################################################################## > ## > > ## font config (GRAPHICS) > > > ######################################################################## > ## > > /usr/photon/font_repository/tt2009m_.ttf = > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > /usr/photon/font_repository/phcursor.phf = > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > /usr/photon/font_repository/mappings = > ${QNX_TARGET}/usr/photon/font_repository/mappings > > /usr/photon/font_repository/fontopts = > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > /usr/photon/font_repository/fontkey = > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > /usr/photon/font_repository/fontdir = { > > ; > > ; fontdir config file > > ; > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > BT,0,,0020-F002,f,79x170,109K > > } > > > > /usr/photon/font_repository/fontext = { > > ; > > ; fontext config file > > ; > > +normal = primasansmonobts, phcursor > > } > > > > /proc/boot/font_repository/fontdesc={ > > [SANSERIF] > > PrimaSansMono BT > > } > > > > /usr/photon/font_repository/fontmap = { > > ; > > ; fontmap config file > > ; > > ? = primasansmonobts > > } > > > > /usr/photon/config/wm/wm.menu={ > > =Desktop Menu > > Terminal T pterm > > Calculator C phcalc_sm > > } > > > > > > > > > ######################################################################## > ### > > ## uncomment for NETWORK driver > > > ######################################################################## > ### > > devn-smc9000.so > > libsocket.so > > devnp-shim.so > > > > > ######################################################################## > ### > > ## uncomment for USB driver > > > ######################################################################## > ### > > libusbdi.so > > devu-ohci.so > > > > ##################################### > > #input driver > > ###################################### > > devi-omap_keypad > > > > > ######################################################################## > ### > > ## Needed for Photon > > > ######################################################################## > ### > > devc-pty > > ksh > > slogger > > sloginfo > > Photon > > io-graphics > > io-display > > devi-hirun > > phfont > > pwm > > # photon applications required to be unstriped by mkifs, hence these > have > > # +raw tag to tell mkifs not to strip them > > [+raw] /usr/photon/bin/pterm = pterm > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > # allow pterm to save its configuration to RAM, if the user changes > it. > > [type=link] /.ph/pterm = /dev/shmem > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > ######################################################################## > ### > > ## uncomment for etfs driver > > > ######################################################################## > ### > > fs-etfs-omap2420 > > etfsctl > > > > > ######################################################################## > ### > > ## uncomment for I2C driver > > > ######################################################################## > ### > > i2c-omap59xx > > > > > ######################################################################## > ### > > ## uncomment for NETWORK driver > > > ######################################################################## > ### > > io-pkt-v4 > > nicinfo > > ifconfig > > ping > > cat > > fs-nfs2 > > > > > ######################################################################## > ### > > ## uncomment for USB driver > > > ######################################################################## > ### > > io-usb > > omap2420sdp_usb_init > > usb > > > > > ######################################################################## > ### > > ## uncomment for Graphics driver > > > ######################################################################## > ### > > vsync > > egl-gears-lite > > io-display > > /etc/system/config/omap35xx.conf=omap35xx.conf > > /etc/system/config/display.conf={ > > device \{ > > drivername=omap35xx > > vid=0 > > did=0 > > modeopts=/etc/system/config/omap35xx.conf > > display \{ > > xres=240 > > yres=320 > > refresh=60 > > pixel_format=rgb565 > > photon \{ > > enabled=1 > > xoffset=0 > > yoffset=0 > > cursor=software > > input_group=1 > > \} > > > > \} > > \} > > } > > > > > ######################################################################## > ### > > ## general commands > > > ######################################################################## > ### > > ls > > ksh > > pipe > > pidin > > uname > > slogger > > sloginfo > > slay > > cp > > chmod > > waitfor > > shutdown > > > > ##i2c utility > > i2c-reg > > > > > ######################################################################## > ### > > ## END OF BUILD SCRIPT > > > ######################################################################## > ### > > > > ## GRAPHICS: > > ## example buildfile commands: > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > -pphoton > > ## > > ## > > ## required libraries: > > ## Please refer to the photon embedding documentation > > ## > > ## required binaries: > > ## Please refer to the photon embedding documentation > > ## > > ## > > > ------------------------------------------------------------------------ > -- > > > Are you running the pterm in the background? pterm & > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 8, 2011 12:26 PM > > > To: advanced-graphics > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > Thanks Derek for the reply. > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > As I mentioned I am not populating the layer_flushrect(), but you > are > > > right I could be getting the continuous calls because my cursor is > > > blinking. > > > > > > You are absolutely right about "minicom". I am using a serial > terminal > > > to launch the Pterm utility. I am not sure on what priority my > serial > > > driver is running on. > > > > > > I would appreciate Derek if you could look at the attached files and > see > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83023 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83038 Wed, 09 Feb 2011 17:07:14 GMT http://community.qnx.com/sf/go/post83039 Derek Leach 2011-02-09T17:07:14Z http://community.qnx.com/sf/go/post83038 Thanks for the reply Derek. It is a GF application and not the Photon one. > Is this rectangle application a GF or a Photon application? > > No, there is no need to run it from pterm. > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 9, 2011 8:49 AM > To: advanced-graphics > Subject: Re: RE: RE: Display Hanging after Pterm Utility > > I got the Pterm working. I ran the Pterm in background and I could see > the blinking cursor and I can type the commands in serial terminal. > > I created one simple app to draw a rectangle and I am trying to launch > this app from the serial terminal and not the Pterm. I have put that > application in /src/utils/ folder. The application is there in the > image. > > I have two question regarding this. > > i) Do I need to launch the app from the Pterm? > If yes, then I will need an input driver. > > ii) Can I launch that App from the serial terminal? > > I tried doing it but it doesn't draw the rectangle. > The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. > > Does anybody know why I got this error? I would appreciate the reply. > > Note: > I could draw the rectangle by typing following command on pterm "pterm > -x10 -y10 -height100 -width100". > > One final question. Is there a way to display the QNX home screen on the > LCD panel? If yes, then how? > > Regards, > > > No Derek, it is running in foreground. > > > > > ######################################################################## > ### > > ## START OF BUILD SCRIPT > > > ######################################################################## > ### > > > > [image=0x80010000] > > [+compress] > > #[virtual=armle,binary] .bootstrap = { > > [virtual=armle,raw] .bootstrap = { > > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > > > ####################################################################### > > ## PATH set here is the *safe* path for executables. > > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > > ## i.e. These are the paths searched by setuid/setgid > binaries. > > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > > > ####################################################################### > > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont > procnto-v6 > > } > > [+script] .script = { > > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > > > display_msg Welcome to QNX Neutrino Trunk on the Texas > Instruments > > OMAP2430SDP Board > > > > > ####################################################################### > > ## SERIAL driver > > > ####################################################################### > > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > > waitfor /dev/ser1 4 > > reopen /dev/ser1 > > > > slogger > > pipe > > > > > ####################################################################### > > ## NAND_ETFS driver > > > ####################################################################### > > #display_msg Starting etfs driver... > > > > #fs-etfs-omap2420 -r4096 > > > > > ####################################################################### > > ## NETWORK driver > > > ####################################################################### > > # > > #display_msg Starting on-board ethernet with TCP/IP stack... > > # > > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > > # > > #waitfor /dev/io-net/en0 4 > > > > > ####################################################################### > > ## I2C driver > > ## - Required for both USB and AUDIO > > > ####################################################################### > > display_msg Starting I2C driver... > > > > i2c-omap59xx -p0x48072000 -i56 > > waitfor /dev/i2c0 5 > > > > > ####################################################################### > > ## USB driver > > ## - Requires the I2C driver to be running > > > ####################################################################### > > #display_msg Starting USB stack... > > > > #omap2420sdp_usb_init > > #io-usb -dohci ioport=0x4805e000,irq=78 > > > > > ####################################################################### > > ## input > > > ####################################################################### > > #display_msg Starting Keypad driver... > > > > #devi-omap_keypad keypad > > > > > ####################################################################### > > ## These env variables are inherited by all the programs which > follow > > > ####################################################################### > > SYSNAME=nto > > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > > PHOTON_PATH=/usr/photon > > PHOTON=/dev/photon > > PHFONT=/dev/phfont > > TERM=qansi > > HOME=/ > > > > > ###################################################################### > > # > > ## GRAPHICS > > > ####################################################################### > > display_msg Starting io-display... > > > > io-display -dvid=0,did=0 > > waitfor /dev/io-display 10 > > > > > ####################################################################### > > ## Photon and Phfont > > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS > driver > > > ####################################################################### > > display_msg Starting Photon... > > Photon & > > waitfor /dev/photon 10 > > display_msg Starting Phfont... > > Phfont & > > waitfor /proc/boot/phfont 10 > > display_msg Starting io-graphics... > > io-graphics > > display_msg Starting PWM... > > pwm & > > display_msg Starting DEVC-PTY... > > devc-pty & > > display_msg Starting PTERM... > > pterm > > display_msg Starting BKGDMGR... > > bkgdmgr > > sloginfo > > > > > ####################################################################### > > ## input > > > ####################################################################### > > #display_msg Starting Keypad driver... > > > > #devi-omap_keypad keypad > > > > > > > > > > [+session] ksh & > > } > > > > [type=link] /bin/sh=/proc/boot/ksh > > [type=link] /dev/console=/dev/ser1 > > [type=link] /tmp=/dev/shmem > > [type=link] /proc/boot/font_repository=/proc/boot > > > > > > > ######################################################################## > ### > > ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) > > > ######################################################################## > ### > > #libc.so.2 > > > ######################################################################## > ### > > ## uncomment for standard libs > > > ######################################################################## > ### > > libc.so > > libm.so > > > > > ######################################################################## > ### > > ## uncomment for photon libs (GRAPHICS) > > > ######################################################################## > ### > > libph.so > > libAp.so > > libphexlib.so > > > > > ######################################################################## > ### > > ## uncomment for GRAPHICS driver > > > ######################################################################## > ### > > devg-omap35xx.so > > libgf.so > > libGLES_CM.so > > libimg.so > > gri-photon.so > > libphrender.so > > libgri.so > > libdisputil.so > > libffb.so > > libgf.so.1 > > libGLES_CL.so.1 > > > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se > ttings > > > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default > .pal > > > > > > [data=c] > > devc-seromap > > > > > > > > > ######################################################################## > ## > > ## font libs (GRAPHICS) > > > ######################################################################## > ## > > devg-svga.so > > /etc/system/config/omap35xx.conf = > ${QNX_TARGET}/etc/system/config/omap35xx.conf > > /lib/dll/font/ttfFFcore.so = > ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > > /lib/dll/font/PHFcore.so = ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > > /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > > libfontharnessutils.so > > libfontutils.so > > libblkcache.so > > libFF-T2K.so > > libFF-T2K-cache.so > > libFF-T2K-fm.so > > libfont.so > > phfont.so > > > > > ######################################################################## > ## > > ## font config (GRAPHICS) > > > ######################################################################## > ## > > /usr/photon/font_repository/tt2009m_.ttf = > ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > > /usr/photon/font_repository/phcursor.phf = > ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > > /usr/photon/font_repository/mappings = > ${QNX_TARGET}/usr/photon/font_repository/mappings > > /usr/photon/font_repository/fontopts = > ${QNX_TARGET}/usr/photon/font_repository/fontopts > > /usr/photon/font_repository/fontkey = > ${QNX_TARGET}/usr/photon/font_repository/fontkey > > > > /usr/photon/font_repository/fontdir = { > > ; > > ; fontdir config file > > ; > > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono > BT,0,,0020-F002,f,79x170,109K > > } > > > > /usr/photon/font_repository/fontext = { > > ; > > ; fontext config file > > ; > > +normal = primasansmonobts, phcursor > > } > > > > /proc/boot/font_repository/fontdesc={ > > [SANSERIF] > > PrimaSansMono BT > > } > > > > /usr/photon/font_repository/fontmap = { > > ; > > ; fontmap config file > > ; > > ? = primasansmonobts > > } > > > > /usr/photon/config/wm/wm.menu={ > > =Desktop Menu > > Terminal T pterm > > Calculator C phcalc_sm > > } > > > > > > > > > ######################################################################## > ### > > ## uncomment for NETWORK driver > > > ######################################################################## > ### > > devn-smc9000.so > > libsocket.so > > devnp-shim.so > > > > > ######################################################################## > ### > > ## uncomment for USB driver > > > ######################################################################## > ### > > libusbdi.so > > devu-ohci.so > > > > ##################################### > > #input driver > > ###################################### > > devi-omap_keypad > > > > > ######################################################################## > ### > > ## Needed for Photon > > > ######################################################################## > ### > > devc-pty > > ksh > > slogger > > sloginfo > > Photon > > io-graphics > > io-display > > devi-hirun > > phfont > > pwm > > # photon applications required to be unstriped by mkifs, hence these > have > > # +raw tag to tell mkifs not to strip them > > [+raw] /usr/photon/bin/pterm = pterm > > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > > > # allow pterm to save its configuration to RAM, if the user changes > it. > > [type=link] /.ph/pterm = /dev/shmem > > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > > > > > ######################################################################## > ### > > ## uncomment for etfs driver > > > ######################################################################## > ### > > fs-etfs-omap2420 > > etfsctl > > > > > ######################################################################## > ### > > ## uncomment for I2C driver > > > ######################################################################## > ### > > i2c-omap59xx > > > > > ######################################################################## > ### > > ## uncomment for NETWORK driver > > > ######################################################################## > ### > > io-pkt-v4 > > nicinfo > > ifconfig > > ping > > cat > > fs-nfs2 > > > > > ######################################################################## > ### > > ## uncomment for USB driver > > > ######################################################################## > ### > > io-usb > > omap2420sdp_usb_init > > usb > > > > > ######################################################################## > ### > > ## uncomment for Graphics driver > > > ######################################################################## > ### > > vsync > > egl-gears-lite > > io-display > > /etc/system/config/omap35xx.conf=omap35xx.conf > > /etc/system/config/display.conf={ > > device \{ > > drivername=omap35xx > > vid=0 > > did=0 > > modeopts=/etc/system/config/omap35xx.conf > > display \{ > > xres=240 > > yres=320 > > refresh=60 > > pixel_format=rgb565 > > photon \{ > > enabled=1 > > xoffset=0 > > yoffset=0 > > cursor=software > > input_group=1 > > \} > > > > \} > > \} > > } > > > > > ######################################################################## > ### > > ## general commands > > > ######################################################################## > ### > > ls > > ksh > > pipe > > pidin > > uname > > slogger > > sloginfo > > slay > > cp > > chmod > > waitfor > > shutdown > > > > ##i2c utility > > i2c-reg > > > > > ######################################################################## > ### > > ## END OF BUILD SCRIPT > > > ######################################################################## > ### > > > > ## GRAPHICS: > > ## example buildfile commands: > > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon > -pphoton > > ## > > ## > > ## required libraries: > > ## Please refer to the photon embedding documentation > > ## > > ## required binaries: > > ## Please refer to the photon embedding documentation > > ## > > ## > > > ------------------------------------------------------------------------ > -- > > > Are you running the pterm in the background? pterm & > > > > > > -----Original Message----- > > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > > Sent: February 8, 2011 12:26 PM > > > To: advanced-graphics > > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > > > Thanks Derek for the reply. > > > Sorry for not mentioning the OS version. I am running 6.5. > > > > > > As I mentioned I am not populating the layer_flushrect(), but you > are > > > right I could be getting the continuous calls because my cursor is > > > blinking. > > > > > > You are absolutely right about "minicom". I am using a serial > terminal > > > to launch the Pterm utility. I am not sure on what priority my > serial > > > driver is running on. > > > > > > I would appreciate Derek if you could look at the attached files and > see > > > if there is something wrong in that. > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Advanced Graphics > > > http://community.qnx.com/sf/go/post82996 > > > > > > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post83023 Wed, 09 Feb 2011 16:36:53 GMT http://community.qnx.com/sf/go/post83038 Raj Pandey 2011-02-09T16:36:53Z http://community.qnx.com/sf/go/post83025 Is this rectangle application a GF or a Photon application? No, there is no need to run it from pterm. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 9, 2011 8:49 AM To: advanced-graphics Subject: Re: RE: RE: Display Hanging after Pterm Utility I got the Pterm working. I ran the Pterm in background and I could see the blinking cursor and I can type the commands in serial terminal. I created one simple app to draw a rectangle and I am trying to launch this app from the serial terminal and not the Pterm. I have put that application in /src/utils/ folder. The application is there in the image. I have two question regarding this. i) Do I need to launch the app from the Pterm? If yes, then I will need an input driver. ii) Can I launch that App from the serial terminal? I tried doing it but it doesn't draw the rectangle. The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. Does anybody know why I got this error? I would appreciate the reply. Note: I could draw the rectangle by typing following command on pterm "pterm -x10 -y10 -height100 -width100". One final question. Is there a way to display the QNX home screen on the LCD panel? If yes, then how? Regards, > No Derek, it is running in foreground. > > ######################################################################## ### > ## START OF BUILD SCRIPT > ######################################################################## ### > > [image=0x80010000] > [+compress] > #[virtual=armle,binary] .bootstrap = { > [virtual=armle,raw] .bootstrap = { > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > ####################################################################### > ## PATH set here is the *safe* path for executables. > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > ## i.e. These are the paths searched by setuid/setgid binaries. > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > ####################################################################### > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont procnto-v6 > } > [+script] .script = { > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > display_msg Welcome to QNX Neutrino Trunk on the Texas Instruments > OMAP2430SDP Board > > ####################################################################### > ## SERIAL driver > ####################################################################### > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > waitfor /dev/ser1 4 > reopen /dev/ser1 > > slogger > pipe > > ####################################################################### > ## NAND_ETFS driver > ####################################################################### > #display_msg Starting etfs driver... > > #fs-etfs-omap2420 -r4096 > > ####################################################################### > ## NETWORK driver > ####################################################################### > # > #display_msg Starting on-board ethernet with TCP/IP stack... > # > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > # > #waitfor /dev/io-net/en0 4 > > ####################################################################### > ## I2C driver > ## - Required for both USB and AUDIO > ####################################################################### > display_msg Starting I2C driver... > > i2c-omap59xx -p0x48072000 -i56 > waitfor /dev/i2c0 5 > > ####################################################################### > ## USB driver > ## - Requires the I2C driver to be running > ####################################################################### > #display_msg Starting USB stack... > > #omap2420sdp_usb_init > #io-usb -dohci ioport=0x4805e000,irq=78 > > ####################################################################### > ## input > ####################################################################### > #display_msg Starting Keypad driver... > > #devi-omap_keypad keypad > > ####################################################################### > ## These env variables are inherited by all the programs which follow > ####################################################################### > SYSNAME=nto > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > PHOTON_PATH=/usr/photon > PHOTON=/dev/photon > PHFONT=/dev/phfont > TERM=qansi > HOME=/ > > ###################################################################### > # > ## GRAPHICS > ####################################################################### > display_msg Starting io-display... > > io-display -dvid=0,did=0 > waitfor /dev/io-display 10 > > ####################################################################### > ## Photon and Phfont > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS driver > ####################################################################### > display_msg Starting Photon... > Photon & > waitfor /dev/photon 10 > display_msg Starting Phfont... > Phfont & > waitfor /proc/boot/phfont 10 > display_msg Starting io-graphics... > io-graphics > display_msg Starting PWM... > pwm & > display_msg Starting DEVC-PTY... > devc-pty & > display_msg Starting PTERM... > pterm > display_msg Starting BKGDMGR... > bkgdmgr > sloginfo > > ####################################################################### > ## input > ####################################################################### > #display_msg Starting Keypad driver... > > #devi-omap_keypad keypad > > > > > [+session] ksh & > } > > [type=link] /bin/sh=/proc/boot/ksh > [type=link] /dev/console=/dev/ser1 > [type=link] /tmp=/dev/shmem > [type=link] /proc/boot/font_repository=/proc/boot > > > ######################################################################## ### > ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) > ######################################################################## ### > #libc.so.2 > ######################################################################## ### > ## uncomment for standard libs > ######################################################################## ### > libc.so > libm.so > > ######################################################################## ### > ## uncomment for photon libs (GRAPHICS) > ######################################################################## ### > libph.so > libAp.so > libphexlib.so > > ######################################################################## ### > ## uncomment for GRAPHICS driver > ######################################################################## ### > devg-omap35xx.so > libgf.so > libGLES_CM.so > libimg.so > gri-photon.so > libphrender.so > libgri.so > libdisputil.so > libffb.so > libgf.so.1 > libGLES_CL.so.1 > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se ttings > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default .pal > > > [data=c] > devc-seromap > > > > ######################################################################## ## > ## font libs (GRAPHICS) > ######################################################################## ## > devg-svga.so > /etc/system/config/omap35xx.conf = ${QNX_TARGET}/etc/system/config/omap35xx.conf > /lib/dll/font/ttfFFcore.so = ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > /lib/dll/font/PHFcore.so = ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > libfontharnessutils.so > libfontutils.so > libblkcache.so > libFF-T2K.so > libFF-T2K-cache.so > libFF-T2K-fm.so > libfont.so > phfont.so > > ######################################################################## ## > ## font config (GRAPHICS) > ######################################################################## ## > /usr/photon/font_repository/tt2009m_.ttf = ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > /usr/photon/font_repository/phcursor.phf = ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > /usr/photon/font_repository/mappings = ${QNX_TARGET}/usr/photon/font_repository/mappings > /usr/photon/font_repository/fontopts = ${QNX_TARGET}/usr/photon/font_repository/fontopts > /usr/photon/font_repository/fontkey = ${QNX_TARGET}/usr/photon/font_repository/fontkey > > /usr/photon/font_repository/fontdir = { > ; > ; fontdir config file > ; > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono BT,0,,0020-F002,f,79x170,109K > } > > /usr/photon/font_repository/fontext = { > ; > ; fontext config file > ; > +normal = primasansmonobts, phcursor > } > > /proc/boot/font_repository/fontdesc={ > [SANSERIF] > PrimaSansMono BT > } > > /usr/photon/font_repository/fontmap = { > ; > ; fontmap config file > ; > ? = primasansmonobts > } > > /usr/photon/config/wm/wm.menu={ > =Desktop Menu > Terminal T pterm > Calculator C phcalc_sm > } > > > > ######################################################################## ### > ## uncomment for NETWORK driver > ######################################################################## ### > devn-smc9000.so > libsocket.so > devnp-shim.so > > ######################################################################## ### > ## uncomment for USB driver > ######################################################################## ### > libusbdi.so > devu-ohci.so > > ##################################### > #input driver > ###################################### > devi-omap_keypad > > ######################################################################## ### > ## Needed for Photon > ######################################################################## ### > devc-pty > ksh > slogger > sloginfo > Photon > io-graphics > io-display > devi-hirun > phfont > pwm > # photon applications required to be unstriped by mkifs, hence these have > # +raw tag to tell mkifs not to strip them > [+raw] /usr/photon/bin/pterm = pterm > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > # allow pterm to save its configuration to RAM, if the user changes it. > [type=link] /.ph/pterm = /dev/shmem > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > ######################################################################## ### > ## uncomment for etfs driver > ######################################################################## ### > fs-etfs-omap2420 > etfsctl > > ######################################################################## ### > ## uncomment for I2C driver > ######################################################################## ### > i2c-omap59xx > > ######################################################################## ### > ## uncomment for NETWORK driver > ######################################################################## ### > io-pkt-v4 > nicinfo > ifconfig > ping > cat > fs-nfs2 > > ######################################################################## ### > ## uncomment for USB driver > ######################################################################## ### > io-usb > omap2420sdp_usb_init > usb > > ######################################################################## ### > ## uncomment for Graphics driver > ######################################################################## ### > vsync > egl-gears-lite > io-display > /etc/system/config/omap35xx.conf=omap35xx.conf > /etc/system/config/display.conf={ > device \{ > drivername=omap35xx > vid=0 > did=0 > modeopts=/etc/system/config/omap35xx.conf > display \{ > xres=240 > yres=320 > refresh=60 > pixel_format=rgb565 > photon \{ > enabled=1 > xoffset=0 > yoffset=0 > cursor=software > input_group=1 > \} > > \} > \} > } > > ######################################################################## ### > ## general commands > ######################################################################## ### > ls > ksh > pipe > pidin > uname > slogger > sloginfo > slay > cp > chmod > waitfor > shutdown > > ##i2c utility > i2c-reg > > ######################################################################## ### > ## END OF BUILD SCRIPT > ######################################################################## ### > > ## GRAPHICS: > ## example buildfile commands: > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon -pphoton > ## > ## > ## required libraries: > ## Please refer to the photon embedding documentation > ## > ## required binaries: > ## Please refer to the photon embedding documentation > ## > ## > ------------------------------------------------------------------------ -- > > Are you running the pterm in the background? pterm & > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 8, 2011 12:26 PM > > To: advanced-graphics > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > Thanks Derek for the reply. > > Sorry for not mentioning the OS version. I am running 6.5. > > > > As I mentioned I am not populating the layer_flushrect(), but you are > > right I could be getting the continuous calls because my cursor is > > blinking. > > > > You are absolutely right about "minicom". I am using a serial terminal > > to launch the Pterm utility. I am not sure on what priority my serial > > driver is running on. > > > > I would appreciate Derek if you could look at the attached files and see > > if there is something wrong in that. > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post82996 > > _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83023 Wed, 09 Feb 2011 13:51:27 GMT http://community.qnx.com/sf/go/post83025 Derek Leach 2011-02-09T13:51:27Z http://community.qnx.com/sf/go/post83023 I got the Pterm working. I ran the Pterm in background and I could see the blinking cursor and I can type the commands in serial terminal. I created one simple app to draw a rectangle and I am trying to launch this app from the serial terminal and not the Pterm. I have put that application in /src/utils/ folder. The application is there in the image. I have two question regarding this. i) Do I need to launch the app from the Pterm? If yes, then I will need an input driver. ii) Can I launch that App from the serial terminal? I tried doing it but it doesn't draw the rectangle. The "Sloginfo" says that gf_draw_begin() failed with gf_errno 1. Does anybody know why I got this error? I would appreciate the reply. Note: I could draw the rectangle by typing following command on pterm "pterm -x10 -y10 -height100 -width100". One final question. Is there a way to display the QNX home screen on the LCD panel? If yes, then how? Regards, > No Derek, it is running in foreground. > > ########################################################################### > ## START OF BUILD SCRIPT > ########################################################################### > > [image=0x80010000] > [+compress] > #[virtual=armle,binary] .bootstrap = { > [virtual=armle,raw] .bootstrap = { > startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 > ####################################################################### > ## PATH set here is the *safe* path for executables. > ## LD_LIBRARY_PATH set here is the *safe* path for libraries. > ## i.e. These are the paths searched by setuid/setgid binaries. > ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) > ####################################################################### > PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ > PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont procnto-v6 > } > [+script] .script = { > procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 > > display_msg Welcome to QNX Neutrino Trunk on the Texas Instruments > OMAP2430SDP Board > > ####################################################################### > ## SERIAL driver > ####################################################################### > devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 > waitfor /dev/ser1 4 > reopen /dev/ser1 > > slogger > pipe > > ####################################################################### > ## NAND_ETFS driver > ####################################################################### > #display_msg Starting etfs driver... > > #fs-etfs-omap2420 -r4096 > > ####################################################################### > ## NETWORK driver > ####################################################################### > # > #display_msg Starting on-board ethernet with TCP/IP stack... > # > #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip > # > #waitfor /dev/io-net/en0 4 > > ####################################################################### > ## I2C driver > ## - Required for both USB and AUDIO > ####################################################################### > display_msg Starting I2C driver... > > i2c-omap59xx -p0x48072000 -i56 > waitfor /dev/i2c0 5 > > ####################################################################### > ## USB driver > ## - Requires the I2C driver to be running > ####################################################################### > #display_msg Starting USB stack... > > #omap2420sdp_usb_init > #io-usb -dohci ioport=0x4805e000,irq=78 > > ####################################################################### > ## input > ####################################################################### > #display_msg Starting Keypad driver... > > #devi-omap_keypad keypad > > ####################################################################### > ## These env variables are inherited by all the programs which follow > ####################################################################### > SYSNAME=nto > PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin > LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll > PHOTON_PATH=/usr/photon > PHOTON=/dev/photon > PHFONT=/dev/phfont > TERM=qansi > HOME=/ > > ###################################################################### > # > ## GRAPHICS > ####################################################################### > display_msg Starting io-display... > > io-display -dvid=0,did=0 > waitfor /dev/io-display 10 > > ####################################################################### > ## Photon and Phfont > ## - NOTE: Photon and phfont MUST be started before the GRAPHICS driver > ####################################################################### > display_msg Starting Photon... > Photon & > waitfor /dev/photon 10 > display_msg Starting Phfont... > Phfont & > waitfor /proc/boot/phfont 10 > display_msg Starting io-graphics... > io-graphics > display_msg Starting PWM... > pwm & > display_msg Starting DEVC-PTY... > devc-pty & > display_msg Starting PTERM... > pterm > display_msg Starting BKGDMGR... > bkgdmgr > sloginfo > > ####################################################################### > ## input > ####################################################################### > #display_msg Starting Keypad driver... > > #devi-omap_keypad keypad > > > > > [+session] ksh & > } > > [type=link] /bin/sh=/proc/boot/ksh > [type=link] /dev/console=/dev/ser1 > [type=link] /tmp=/dev/shmem > [type=link] /proc/boot/font_repository=/proc/boot > > > ########################################################################### > ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) > ########################################################################### > #libc.so.2 > ########################################################################### > ## uncomment for standard libs > ########################################################################### > libc.so > libm.so > > ########################################################################### > ## uncomment for photon libs (GRAPHICS) > ########################################################################### > libph.so > libAp.so > libphexlib.so > > ########################################################################### > ## uncomment for GRAPHICS driver > ########################################################################### > devg-omap35xx.so > libgf.so > libGLES_CM.so > libimg.so > gri-photon.so > libphrender.so > libgri.so > libdisputil.so > libffb.so > libgf.so.1 > libGLES_CL.so.1 > /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-settings > /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default.pal > > > [data=c] > devc-seromap > > > > ########################################################################## > ## font libs (GRAPHICS) > ########################################################################## > devg-svga.so > /etc/system/config/omap35xx.conf = ${QNX_TARGET}/etc/system/config/omap35xx.conf > /lib/dll/font/ttfFFcore.so = ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so > /lib/dll/font/PHFcore.so = ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so > /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so > libfontharnessutils.so > libfontutils.so > libblkcache.so > libFF-T2K.so > libFF-T2K-cache.so > libFF-T2K-fm.so > libfont.so > phfont.so > > ########################################################################## > ## font config (GRAPHICS) > ########################################################################## > /usr/photon/font_repository/tt2009m_.ttf = ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf > /usr/photon/font_repository/phcursor.phf = ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf > /usr/photon/font_repository/mappings = ${QNX_TARGET}/usr/photon/font_repository/mappings > /usr/photon/font_repository/fontopts = ${QNX_TARGET}/usr/photon/font_repository/fontopts > /usr/photon/font_repository/fontkey = ${QNX_TARGET}/usr/photon/font_repository/fontkey > > /usr/photon/font_repository/fontdir = { > ; > ; fontdir config file > ; > phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K > primasansmonobts,0@tt2009m_.ttf,PrimaSansMono BT,0,,0020-F002,f,79x170,109K > } > > /usr/photon/font_repository/fontext = { > ; > ; fontext config file > ; > +normal = primasansmonobts, phcursor > } > > /proc/boot/font_repository/fontdesc={ > [SANSERIF] > PrimaSansMono BT > } > > /usr/photon/font_repository/fontmap = { > ; > ; fontmap config file > ; > ? = primasansmonobts > } > > /usr/photon/config/wm/wm.menu={ > =Desktop Menu > Terminal T pterm > Calculator C phcalc_sm > } > > > > ########################################################################### > ## uncomment for NETWORK driver > ########################################################################### > devn-smc9000.so > libsocket.so > devnp-shim.so > > ########################################################################### > ## uncomment for USB driver > ########################################################################### > libusbdi.so > devu-ohci.so > > ##################################### > #input driver > ###################################### > devi-omap_keypad > > ########################################################################### > ## Needed for Photon > ########################################################################### > devc-pty > ksh > slogger > sloginfo > Photon > io-graphics > io-display > devi-hirun > phfont > pwm > # photon applications required to be unstriped by mkifs, hence these have > # +raw tag to tell mkifs not to strip them > [+raw] /usr/photon/bin/pterm = pterm > [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm > > # allow pterm to save its configuration to RAM, if the user changes it. > [type=link] /.ph/pterm = /dev/shmem > [type=link] /.ph/wm/wm.cfg = /dev/shmem > > > ########################################################################### > ## uncomment for etfs driver > ########################################################################### > fs-etfs-omap2420 > etfsctl > > ########################################################################### > ## uncomment for I2C driver > ########################################################################### > i2c-omap59xx > > ########################################################################### > ## uncomment for NETWORK driver > ########################################################################### > io-pkt-v4 > nicinfo > ifconfig > ping > cat > fs-nfs2 > > ########################################################################### > ## uncomment for USB driver > ########################################################################### > io-usb > omap2420sdp_usb_init > usb > > ########################################################################### > ## uncomment for Graphics driver > ########################################################################### > vsync > egl-gears-lite > io-display > /etc/system/config/omap35xx.conf=omap35xx.conf > /etc/system/config/display.conf={ > device \{ > drivername=omap35xx > vid=0 > did=0 > modeopts=/etc/system/config/omap35xx.conf > display \{ > xres=240 > yres=320 > refresh=60 > pixel_format=rgb565 > photon \{ > enabled=1 > xoffset=0 > yoffset=0 > cursor=software > input_group=1 > \} > > \} > \} > } > > ########################################################################### > ## general commands > ########################################################################### > ls > ksh > pipe > pidin > uname > slogger > sloginfo > slay > cp > chmod > waitfor > shutdown > > ##i2c utility > i2c-reg > > ########################################################################### > ## END OF BUILD SCRIPT > ########################################################################### > > ## GRAPHICS: > ## example buildfile commands: > ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon -pphoton > ## > ## > ## required libraries: > ## Please refer to the photon embedding documentation > ## > ## required binaries: > ## Please refer to the photon embedding documentation > ## > ## > -------------------------------------------------------------------------- > > Are you running the pterm in the background? pterm & > > > > -----Original Message----- > > From: Raj Pandey [mailto:community-noreply@qnx.com] > > Sent: February 8, 2011 12:26 PM > > To: advanced-graphics > > Subject: Re: RE: Display Hanging after Pterm Utility > > > > Thanks Derek for the reply. > > Sorry for not mentioning the OS version. I am running 6.5. > > > > As I mentioned I am not populating the layer_flushrect(), but you are > > right I could be getting the continuous calls because my cursor is > > blinking. > > > > You are absolutely right about "minicom". I am using a serial terminal > > to launch the Pterm utility. I am not sure on what priority my serial > > driver is running on. > > > > I would appreciate Derek if you could look at the attached files and see > > if there is something wrong in that. > > > > > > > > > > > > _______________________________________________ > > > > Advanced Graphics > > http://community.qnx.com/sf/go/post82996 > > Wed, 09 Feb 2011 13:49:07 GMT http://community.qnx.com/sf/go/post83023 Raj Pandey 2011-02-09T13:49:07Z http://community.qnx.com/sf/go/post83022 Maybe I misunderstand, but how do you expect to type on the serial console, if pterm is running in the foreground on the console? pterm does not daemonize itself. I am not even sure that bkgdmgr daemonizes itself either ... add a & to the end of those lines. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 8, 2011 9:32 PM To: advanced-graphics Subject: Re: RE: RE: Display Hanging after Pterm Utility No Derek, it is running in foreground. ######################################################################## ### ## START OF BUILD SCRIPT ######################################################################## ### [image=0x80010000] [+compress] #[virtual=armle,binary] .bootstrap = { [virtual=armle,raw] .bootstrap = { startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 ####################################################################### ## PATH set here is the *safe* path for executables. ## LD_LIBRARY_PATH set here is the *safe* path for libraries. ## i.e. These are the paths searched by setuid/setgid binaries. ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) ####################################################################### PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont procnto-v6 } [+script] .script = { procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 display_msg Welcome to QNX Neutrino Trunk on the Texas Instruments OMAP2430SDP Board ####################################################################### ## SERIAL driver ####################################################################### devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 waitfor /dev/ser1 4 reopen /dev/ser1 slogger pipe ####################################################################### ## NAND_ETFS driver ####################################################################### #display_msg Starting etfs driver... #fs-etfs-omap2420 -r4096 ####################################################################### ## NETWORK driver ####################################################################### # #display_msg Starting on-board ethernet with TCP/IP stack... # #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip # #waitfor /dev/io-net/en0 4 ####################################################################### ## I2C driver ## - Required for both USB and AUDIO ####################################################################### display_msg Starting I2C driver... i2c-omap59xx -p0x48072000 -i56 waitfor /dev/i2c0 5 ####################################################################### ## USB driver ## - Requires the I2C driver to be running ####################################################################### #display_msg Starting USB stack... #omap2420sdp_usb_init #io-usb -dohci ioport=0x4805e000,irq=78 ####################################################################### ## input ####################################################################### #display_msg Starting Keypad driver... #devi-omap_keypad keypad ####################################################################### ## These env variables are inherited by all the programs which follow ####################################################################### SYSNAME=nto PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont TERM=qansi HOME=/ ####################################################################### ## GRAPHICS ####################################################################### display_msg Starting io-display... io-display -dvid=0,did=0 waitfor /dev/io-display 10 ####################################################################### ## Photon and Phfont ## - NOTE: Photon and phfont MUST be started before the GRAPHICS driver ####################################################################### display_msg Starting Photon... Photon & waitfor /dev/photon 10 display_msg Starting Phfont... Phfont & waitfor /proc/boot/phfont 10 display_msg Starting io-graphics... io-graphics display_msg Starting PWM... pwm & display_msg Starting DEVC-PTY... devc-pty & display_msg Starting PTERM... pterm display_msg Starting BKGDMGR... bkgdmgr sloginfo ####################################################################### ## input ####################################################################### #display_msg Starting Keypad driver... #devi-omap_keypad keypad [+session] ksh & } [type=link] /bin/sh=/proc/boot/ksh [type=link] /dev/console=/dev/ser1 [type=link] /tmp=/dev/shmem [type=link] /proc/boot/font_repository=/proc/boot ######################################################################## ### ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) ######################################################################## ### #libc.so.2 ######################################################################## ### ## uncomment for standard libs ######################################################################## ### libc.so libm.so ######################################################################## ### ## uncomment for photon libs (GRAPHICS) ######################################################################## ### libph.so libAp.so libphexlib.so ######################################################################## ### ## uncomment for GRAPHICS driver ######################################################################## ### devg-omap35xx.so libgf.so libGLES_CM.so libimg.so gri-photon.so libphrender.so libgri.so libdisputil.so libffb.so libgf.so.1 libGLES_CL.so.1 /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-se ttings /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default .pal [data=c] devc-seromap ######################################################################## ## ## font libs (GRAPHICS) ######################################################################## ## devg-svga.so /etc/system/config/omap35xx.conf = ${QNX_TARGET}/etc/system/config/omap35xx.conf /lib/dll/font/ttfFFcore.so = ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so /lib/dll/font/PHFcore.so = ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so libfontharnessutils.so libfontutils.so libblkcache.so libFF-T2K.so libFF-T2K-cache.so libFF-T2K-fm.so libfont.so phfont.so ######################################################################## ## ## font config (GRAPHICS) ######################################################################## ## /usr/photon/font_repository/tt2009m_.ttf = ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf /usr/photon/font_repository/phcursor.phf = ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf /usr/photon/font_repository/mappings = ${QNX_TARGET}/usr/photon/font_repository/mappings /usr/photon/font_repository/fontopts = ${QNX_TARGET}/usr/photon/font_repository/fontopts /usr/photon/font_repository/fontkey = ${QNX_TARGET}/usr/photon/font_repository/fontkey /usr/photon/font_repository/fontdir = { ; ; fontdir config file ; phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K primasansmonobts,0@tt2009m_.ttf,PrimaSansMono BT,0,,0020-F002,f,79x170,109K } /usr/photon/font_repository/fontext = { ; ; fontext config file ; +normal = primasansmonobts, phcursor } /proc/boot/font_repository/fontdesc={ [SANSERIF] PrimaSansMono BT } /usr/photon/font_repository/fontmap = { ; ; fontmap config file ; ? = primasansmonobts } /usr/photon/config/wm/wm.menu={ =Desktop Menu Terminal T pterm Calculator C phcalc_sm } ######################################################################## ### ## uncomment for NETWORK driver ######################################################################## ### devn-smc9000.so libsocket.so devnp-shim.so ######################################################################## ### ## uncomment for USB driver ######################################################################## ### libusbdi.so devu-ohci.so ##################################### #input driver ###################################### devi-omap_keypad ######################################################################## ### ## Needed for Photon ######################################################################## ### devc-pty ksh slogger sloginfo Photon io-graphics io-display devi-hirun phfont pwm # photon applications required to be unstriped by mkifs, hence these have # +raw tag to tell mkifs not to strip them [+raw] /usr/photon/bin/pterm = pterm [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm # allow pterm to save its configuration to RAM, if the user changes it. [type=link] /.ph/pterm = /dev/shmem [type=link] /.ph/wm/wm.cfg = /dev/shmem ######################################################################## ### ## uncomment for etfs driver ######################################################################## ### fs-etfs-omap2420 etfsctl ######################################################################## ### ## uncomment for I2C driver ######################################################################## ### i2c-omap59xx ######################################################################## ### ## uncomment for NETWORK driver ######################################################################## ### io-pkt-v4 nicinfo ifconfig ping cat fs-nfs2 ######################################################################## ### ## uncomment for USB driver ######################################################################## ### io-usb omap2420sdp_usb_init usb ######################################################################## ### ## uncomment for Graphics driver ######################################################################## ### vsync egl-gears-lite io-display /etc/system/config/omap35xx.conf=omap35xx.conf /etc/system/config/display.conf={ device \{ drivername=omap35xx vid=0 did=0 modeopts=/etc/system/config/omap35xx.conf display \{ xres=240 yres=320 refresh=60 pixel_format=rgb565 photon \{ enabled=1 xoffset=0 yoffset=0 cursor=software input_group=1 \} \} \} } ######################################################################## ### ## general commands ######################################################################## ### ls ksh pipe pidin uname slogger sloginfo slay cp chmod waitfor shutdown ##i2c utility i2c-reg ######################################################################## ### ## END OF BUILD SCRIPT ######################################################################## ### ## GRAPHICS: ## example buildfile commands: ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon -pphoton ## ## ## required libraries: ## Please refer to the photon embedding documentation ## ## required binaries: ## Please refer to the photon embedding documentation ## ## ------------------------------------------------------------------------ -- > Are you running the pterm in the background? pterm & > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 8, 2011 12:26 PM > To: advanced-graphics > Subject: Re: RE: Display Hanging after Pterm Utility > > Thanks Derek for the reply. > Sorry for not mentioning the OS version. I am running 6.5. > > As I mentioned I am not populating the layer_flushrect(), but you are > right I could be getting the continuous calls because my cursor is > blinking. > > You are absolutely right about "minicom". I am using a serial terminal > to launch the Pterm utility. I am not sure on what priority my serial > driver is running on. > > I would appreciate Derek if you could look at the attached files and see > if there is something wrong in that. > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post82996 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post83011 Wed, 09 Feb 2011 13:48:20 GMT http://community.qnx.com/sf/go/post83022 Derek Leach 2011-02-09T13:48:20Z http://community.qnx.com/sf/go/post83011 No Derek, it is running in foreground. ########################################################################### ## START OF BUILD SCRIPT ########################################################################### [image=0x80010000] [+compress] #[virtual=armle,binary] .bootstrap = { [virtual=armle,raw] .bootstrap = { startup-omap2420sdp -L -v -U1 -le 0xA1F00000 0x01000000 ####################################################################### ## PATH set here is the *safe* path for executables. ## LD_LIBRARY_PATH set here is the *safe* path for libraries. ## i.e. These are the paths searched by setuid/setgid binaries. ## (confstr(_CS_PATH...) and confstr(_CS_LIBPATH...)) ####################################################################### PATH=:/proc/boot:/bin:/usr/bin:/bin:/usr/photon/bin LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll \ PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont procnto-v6 } [+script] .script = { procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2 display_msg Welcome to QNX Neutrino Trunk on the Texas Instruments OMAP2430SDP Board ####################################################################### ## SERIAL driver ####################################################################### devc-seromap -e -F -b57600 -c48000000/16 0x4806A000^2,72 waitfor /dev/ser1 4 reopen /dev/ser1 slogger pipe ####################################################################### ## NAND_ETFS driver ####################################################################### #display_msg Starting etfs driver... #fs-etfs-omap2420 -r4096 ####################################################################### ## NETWORK driver ####################################################################### # #display_msg Starting on-board ethernet with TCP/IP stack... # #io-pkt-v4 -dsmc9000 ioport=0x08000300,irq=188 -ptcpip # #waitfor /dev/io-net/en0 4 ####################################################################### ## I2C driver ## - Required for both USB and AUDIO ####################################################################### display_msg Starting I2C driver... i2c-omap59xx -p0x48072000 -i56 waitfor /dev/i2c0 5 ####################################################################### ## USB driver ## - Requires the I2C driver to be running ####################################################################### #display_msg Starting USB stack... #omap2420sdp_usb_init #io-usb -dohci ioport=0x4805e000,irq=78 ####################################################################### ## input ####################################################################### #display_msg Starting Keypad driver... #devi-omap_keypad keypad ####################################################################### ## These env variables are inherited by all the programs which follow ####################################################################### SYSNAME=nto PATH=:/proc/boot:/bin:/usr/bin:/opt/bin:/usr/photon/bin LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll PHOTON_PATH=/usr/photon PHOTON=/dev/photon PHFONT=/dev/phfont TERM=qansi HOME=/ ####################################################################### ## GRAPHICS ####################################################################### display_msg Starting io-display... io-display -dvid=0,did=0 waitfor /dev/io-display 10 ####################################################################### ## Photon and Phfont ## - NOTE: Photon and phfont MUST be started before the GRAPHICS driver ####################################################################### display_msg Starting Photon... Photon & waitfor /dev/photon 10 display_msg Starting Phfont... Phfont & waitfor /proc/boot/phfont 10 display_msg Starting io-graphics... io-graphics display_msg Starting PWM... pwm & display_msg Starting DEVC-PTY... devc-pty & display_msg Starting PTERM... pterm display_msg Starting BKGDMGR... bkgdmgr sloginfo ####################################################################### ## input ####################################################################### #display_msg Starting Keypad driver... #devi-omap_keypad keypad [+session] ksh & } [type=link] /bin/sh=/proc/boot/ksh [type=link] /dev/console=/dev/ser1 [type=link] /tmp=/dev/shmem [type=link] /proc/boot/font_repository=/proc/boot ########################################################################### ## uncomment for legacy binary support (Momentics 6.3.2 and earlier) ########################################################################### #libc.so.2 ########################################################################### ## uncomment for standard libs ########################################################################### libc.so libm.so ########################################################################### ## uncomment for photon libs (GRAPHICS) ########################################################################### libph.so libAp.so libphexlib.so ########################################################################### ## uncomment for GRAPHICS driver ########################################################################### devg-omap35xx.so libgf.so libGLES_CM.so libimg.so gri-photon.so libphrender.so libgri.so libdisputil.so libffb.so libgf.so.1 libGLES_CL.so.1 /etc/system/config/crtc-settings=${QNX_TARGET}/usr/photon/config/crtc-settings /usr/photon/palette/default.pal=${QNX_TARGET}/usr/photon/palette/default.pal [data=c] devc-seromap ########################################################################## ## font libs (GRAPHICS) ########################################################################## devg-svga.so /etc/system/config/omap35xx.conf = ${QNX_TARGET}/etc/system/config/omap35xx.conf /lib/dll/font/ttfFFcore.so = ${QNX_TARGET}/armle/lib/dll/font/ttfFFcore.so /lib/dll/font/PHFcore.so = ${QNX_TARGET}/armle/lib/dll/font/PHFcore.so /lib/dll/font/FCcore.so = ${QNX_TARGET}/armle/lib/dll/font/FCcore.so libfontharnessutils.so libfontutils.so libblkcache.so libFF-T2K.so libFF-T2K-cache.so libFF-T2K-fm.so libfont.so phfont.so ########################################################################## ## font config (GRAPHICS) ########################################################################## /usr/photon/font_repository/tt2009m_.ttf = ${QNX_TARGET}/usr/photon/font_repository/tt2009m_.ttf /usr/photon/font_repository/phcursor.phf = ${QNX_TARGET}/usr/photon/font_repository/phcursor.phf /usr/photon/font_repository/mappings = ${QNX_TARGET}/usr/photon/font_repository/mappings /usr/photon/font_repository/fontopts = ${QNX_TARGET}/usr/photon/font_repository/fontopts /usr/photon/font_repository/fontkey = ${QNX_TARGET}/usr/photon/font_repository/fontkey /usr/photon/font_repository/fontdir = { ; ; fontdir config file ; phcursor,.phf,Photon Cursor,0,,E900-E921,Np,32x32,3K primasansmonobts,0@tt2009m_.ttf,PrimaSansMono BT,0,,0020-F002,f,79x170,109K } /usr/photon/font_repository/fontext = { ; ; fontext config file ; +normal = primasansmonobts, phcursor } /proc/boot/font_repository/fontdesc={ [SANSERIF] PrimaSansMono BT } /usr/photon/font_repository/fontmap = { ; ; fontmap config file ; ? = primasansmonobts } /usr/photon/config/wm/wm.menu={ =Desktop Menu Terminal T pterm Calculator C phcalc_sm } ########################################################################### ## uncomment for NETWORK driver ########################################################################### devn-smc9000.so libsocket.so devnp-shim.so ########################################################################### ## uncomment for USB driver ########################################################################### libusbdi.so devu-ohci.so ##################################### #input driver ###################################### devi-omap_keypad ########################################################################### ## Needed for Photon ########################################################################### devc-pty ksh slogger sloginfo Photon io-graphics io-display devi-hirun phfont pwm # photon applications required to be unstriped by mkifs, hence these have # +raw tag to tell mkifs not to strip them [+raw] /usr/photon/bin/pterm = pterm [+raw] /usr/photon/bin/phcalc_sm = phcalc_sm # allow pterm to save its configuration to RAM, if the user changes it. [type=link] /.ph/pterm = /dev/shmem [type=link] /.ph/wm/wm.cfg = /dev/shmem ########################################################################### ## uncomment for etfs driver ########################################################################### fs-etfs-omap2420 etfsctl ########################################################################### ## uncomment for I2C driver ########################################################################### i2c-omap59xx ########################################################################### ## uncomment for NETWORK driver ########################################################################### io-pkt-v4 nicinfo ifconfig ping cat fs-nfs2 ########################################################################### ## uncomment for USB driver ########################################################################### io-usb omap2420sdp_usb_init usb ########################################################################### ## uncomment for Graphics driver ########################################################################### vsync egl-gears-lite io-display /etc/system/config/omap35xx.conf=omap35xx.conf /etc/system/config/display.conf={ device \{ drivername=omap35xx vid=0 did=0 modeopts=/etc/system/config/omap35xx.conf display \{ xres=240 yres=320 refresh=60 pixel_format=rgb565 photon \{ enabled=1 xoffset=0 yoffset=0 cursor=software input_group=1 \} \} \} } ########################################################################### ## general commands ########################################################################### ls ksh pipe pidin uname slogger sloginfo slay cp chmod waitfor shutdown ##i2c utility i2c-reg ########################################################################### ## END OF BUILD SCRIPT ########################################################################### ## GRAPHICS: ## example buildfile commands: ## io-graphics -domap2420 xres=240,yres=320,bitpp=16,photon -pphoton ## ## ## required libraries: ## Please refer to the photon embedding documentation ## ## required binaries: ## Please refer to the photon embedding documentation ## ## -------------------------------------------------------------------------- > Are you running the pterm in the background? pterm & > > -----Original Message----- > From: Raj Pandey [mailto:community-noreply@qnx.com] > Sent: February 8, 2011 12:26 PM > To: advanced-graphics > Subject: Re: RE: Display Hanging after Pterm Utility > > Thanks Derek for the reply. > Sorry for not mentioning the OS version. I am running 6.5. > > As I mentioned I am not populating the layer_flushrect(), but you are > right I could be getting the continuous calls because my cursor is > blinking. > > You are absolutely right about "minicom". I am using a serial terminal > to launch the Pterm utility. I am not sure on what priority my serial > driver is running on. > > I would appreciate Derek if you could look at the attached files and see > if there is something wrong in that. > > > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post82996 Wed, 09 Feb 2011 02:32:05 GMT http://community.qnx.com/sf/go/post83011 Raj Pandey 2011-02-09T02:32:05Z http://community.qnx.com/sf/go/post82997 Are you running the pterm in the background? pterm & -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 8, 2011 12:26 PM To: advanced-graphics Subject: Re: RE: Display Hanging after Pterm Utility Thanks Derek for the reply. Sorry for not mentioning the OS version. I am running 6.5. As I mentioned I am not populating the layer_flushrect(), but you are right I could be getting the continuous calls because my cursor is blinking. You are absolutely right about "minicom". I am using a serial terminal to launch the Pterm utility. I am not sure on what priority my serial driver is running on. I would appreciate Derek if you could look at the attached files and see if there is something wrong in that. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post82996 Tue, 08 Feb 2011 17:26:48 GMT http://community.qnx.com/sf/go/post82997 Derek Leach 2011-02-08T17:26:48Z http://community.qnx.com/sf/go/post82996 Thanks Derek for the reply. Sorry for not mentioning the OS version. I am running 6.5. As I mentioned I am not populating the layer_flushrect(), but you are right I could be getting the continuous calls because my cursor is blinking. You are absolutely right about "minicom". I am using a serial terminal to launch the Pterm utility. I am not sure on what priority my serial driver is running on. I would appreciate Derek if you could look at the attached files and see if there is something wrong in that. Tue, 08 Feb 2011 17:25:49 GMT http://community.qnx.com/sf/go/post82996 Raj Pandey 2011-02-08T17:25:49Z http://community.qnx.com/sf/go/post82980 What version of the OS are you running on? layer_flushrect() is basically a "hack" for drivers that have virtual layers, and or an optimization for layers if their GPU can be fine tuned that way. It is not necessary, and you should not populate the callout. Input is not required, but you would need it to type into a pterm. btw, you would see this being called continually if you had a blinking cursor. I am not sure what you mean by minicom, I assume you mean a terminal connected to the serial port? Maybe something is running ready? Run you terminal at a higher priority, and check the state of the system. If it is a serial terminal, you will need to run the serial driver at a higher priority as well. -----Original Message----- From: Raj Pandey [mailto:community-noreply@qnx.com] Sent: February 8, 2011 5:34 AM To: advanced-graphics Subject: Display Hanging after Pterm Utility Dear All, I am trying to port display driver on QNX for OMAP2430 hardware. I have configured LCD controller, Framebuffer etc. I am seeing PTERM windows on the LCD panel and the cursor blinking but thats it. I cannot type any commands in "minicom" neither in pterm window(needless to say there is no input driver running). Is Photon expecting an input driver? If it is, then display driver is depending upon the input driver. One more thing I read on QNX website that don't use "layer_flushrect()" API. I was seeing this API being called continuously, so I commented this API. May I know what does this API do? Is it the same as "blitting"? I have attached the relevant files for your kind reference. I would appreciate the help very much. _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post82973 Tue, 08 Feb 2011 14:15:09 GMT http://community.qnx.com/sf/go/post82980 Derek Leach 2011-02-08T14:15:09Z http://community.qnx.com/sf/go/post82973 Dear All, I am trying to port display driver on QNX for OMAP2430 hardware. I have configured LCD controller, Framebuffer etc. I am seeing PTERM windows on the LCD panel and the cursor blinking but thats it. I cannot type any commands in "minicom" neither in pterm window(needless to say there is no input driver running). Is Photon expecting an input driver? If it is, then display driver is depending upon the input driver. One more thing I read on QNX website that don't use "layer_flushrect()" API. I was seeing this API being called continuously, so I commented this API. May I know what does this API do? Is it the same as "blitting"? I have attached the relevant files for your kind reference. I would appreciate the help very much. Tue, 08 Feb 2011 10:33:31 GMT http://community.qnx.com/sf/go/post82973 Raj Pandey 2011-02-08T10:33:31Z http://community.qnx.com/sf/go/post82879 Derek - It seems like you've done this before. Do you have some time to assist? If so, can you e-mail me directly at michael.briggs@harman.com. Thanks. -----Original Message----- From: Derek Leach [mailto:community-noreply@qnx.com] Sent: Thursday, February 03, 2011 2:04 PM To: advanced-graphics Subject: RE: Convert GIF to PNG using the IMG library img_write_file() 8888/32-bit is a good place to start. -----Original Message----- From: Michael Briggs [mailto:community-noreply@qnx.com] Sent: February 3, 2011 2:02 PM To: advanced-graphics Subject: Convert GIF to PNG using the IMG library I've got a task that does image scaling and one road block I've run into is the fact that the IMG library can't write GIF files. Today, it was decided that converting to PNG during the scaling process is an acceptable solution. img_format_t seems to enumerate out a good collection of formats. I THINK I can work out how to use the img_load_file or img_write_file to force a format conversion to another format. So, my question is, of the small ton of formats in img_format_t, which one is "PNG" ? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post82872 _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post82873 Thu, 03 Feb 2011 20:06:28 GMT http://community.qnx.com/sf/go/post82879 Michael Briggs 2011-02-03T20:06:28Z http://community.qnx.com/sf/go/post82873 img_write_file() 8888/32-bit is a good place to start. -----Original Message----- From: Michael Briggs [mailto:community-noreply@qnx.com] Sent: February 3, 2011 2:02 PM To: advanced-graphics Subject: Convert GIF to PNG using the IMG library I've got a task that does image scaling and one road block I've run into is the fact that the IMG library can't write GIF files. Today, it was decided that converting to PNG during the scaling process is an acceptable solution. img_format_t seems to enumerate out a good collection of formats. I THINK I can work out how to use the img_load_file or img_write_file to force a format conversion to another format. So, my question is, of the small ton of formats in img_format_t, which one is "PNG" ? _______________________________________________ Advanced Graphics http://community.qnx.com/sf/go/post82872 Thu, 03 Feb 2011 19:03:45 GMT http://community.qnx.com/sf/go/post82873 Derek Leach 2011-02-03T19:03:45Z http://community.qnx.com/sf/go/post82872 I've got a task that does image scaling and one road block I've run into is the fact that the IMG library can't write GIF files. Today, it was decided that converting to PNG during the scaling process is an acceptable solution. img_format_t seems to enumerate out a good collection of formats. I THINK I can work out how to use the img_load_file or img_write_file to force a format conversion to another format. So, my question is, of the small ton of formats in img_format_t, which one is "PNG" ? Thu, 03 Feb 2011 19:01:49 GMT http://community.qnx.com/sf/go/post82872 Michael Briggs 2011-02-03T19:01:49Z http://community.qnx.com/sf/go/post81202 I was under the impression that QNX 6.5 HMI Technology provided the ability to execute FlashLite 4. I believe the following link advertises this: http://www.qnx.com/products/hmi/hmi.html I have developed some entertainment applications in AS2 that run in the 6.4 environment and I'm considering developing in AS3 for 6.5. When can I expect 6.5 to support Flash AS3 based applications? Will support be released as a patch to 6.5 or will it be rolled out in a future version of QNX? Wed, 05 Jan 2011 15:20:59 GMT http://community.qnx.com/sf/go/post81202 Ralph Canapa 2011-01-05T15:20:59Z http://community.qnx.com/sf/go/post81181 I am assuming you are running a version of HMI Suite/Player on QNX 6.5. The Player is is only FlashLite 3 which means you can only run ActionScript 2 SWFs. What can you tell me about your project? We have new technology incubating that will allow you to run ActionScript 3 SWFs. Thanks, Jason On 11-01-05 9:11 AM, "Ralph Canapa" <community-noreply@qnx.com> wrote: > I am not able to successfully execute a FlashLite 4 SWF on the VMware image on > the QNX Neutrino 6.5.0 Runtime environment. > > I am also not able to successfully execute the file on an installation of the > QNX RTOS 6.5. > > I have successfully run FlashLite3/AS2 files on QNX-CAR/QNX 6.4. > > Where can I find the the Flash player for QNX 6.5 that will successfully > execute FlashLite 4/Actionscript 3 content? > > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post81176 > > Wed, 05 Jan 2011 14:26:30 GMT http://community.qnx.com/sf/go/post81181 Jason Mawdsley 2011-01-05T14:26:30Z http://community.qnx.com/sf/go/post81176 I am not able to successfully execute a FlashLite 4 SWF on the VMware image on the QNX Neutrino 6.5.0 Runtime environment. I am also not able to successfully execute the file on an installation of the QNX RTOS 6.5. I have successfully run FlashLite3/AS2 files on QNX-CAR/QNX 6.4. Where can I find the the Flash player for QNX 6.5 that will successfully execute FlashLite 4/Actionscript 3 content? Wed, 05 Jan 2011 14:11:57 GMT http://community.qnx.com/sf/go/post81176 Ralph Canapa 2011-01-05T14:11:57Z http://community.qnx.com/sf/go/post80592 are we able to allocate 3 surfaces for YUV and display it on the layer without the SDL framework? I don't want to make it complex.. Wed, 29 Dec 2010 02:23:56 GMT http://community.qnx.com/sf/go/post80592 Yanfei Sun 2010-12-29T02:23:56Z http://community.qnx.com/sf/go/post80404 Yanfei Sun wrote: > As the user guide described,"Planar YUV is a video display format. The GF library doesn't support rendering to planar YUV; however, you can display planar YUV data that's already been rendered by another application." is it available to display an yuv image directly? It's probably easier to integrate a SDL window with YUV support. http://community.qnx.com/sf/projects/qnx_community_sdl_project --Armin http://www.steinhoff-automation.com > > > _______________________________________________ > > Advanced Graphics > http://community.qnx.com/sf/go/post80403 > > Mon, 27 Dec 2010 08:54:16 GMT http://community.qnx.com/sf/go/post80404 Armin Steinhoff 2010-12-27T08:54:16Z http://community.qnx.com/sf/go/post80403 As the user guide described,"Planar YUV is a video display format. The GF library doesn't support rendering to planar YUV; however, you can display planar YUV data that's already been rendered by another application." is it available to display an yuv image directly? Mon, 27 Dec 2010 08:02:30 GMT http://community.qnx.com/sf/go/post80403 Yanfei Sun 2010-12-27T08:02:30Z http://community.qnx.com/sf/go/post80392 Hi All, I want to display a planar YUV image on a RGB display device. So I allocate three surfaces for the layer and want to know how to configure the context of each surface and show the image, can anyone provide a demo code or some sugguestions? Thanks, Ray Mon, 27 Dec 2010 03:22:08 GMT http://community.qnx.com/sf/go/post80392 Yanfei Sun 2010-12-27T03:22:08Z http://community.qnx.com/sf/go/post80070 I am trying to use the devi drivers in raw mode "-r". I can get events from the device but I would like to determine which type of device I am dealing with when I get a path. I have tried using the _INTERACTTYPE devctl on a device such as "/dev/devi/mouse0" or "/dev/devi/keyboard0". However the type field always comes back as 0. So how should one determine whether a devi entry is a mouse/keyboard/touchscreen in order to properly read from the device and parse the packets. This is using 6.4.1. Thanks, Brian Wed, 22 Dec 2010 20:06:07 GMT http://community.qnx.com/sf/go/post80070 Brian Edmond 2010-12-22T20:06:07Z http://community.qnx.com/sf/go/post77060 Hi, Thanks for your answer Brian. I will check on Photon, because if we should add the price of licensing to Aviage in order to test Flash, I don't think it will be ok. I'll try to develop a quick test and come back if I need any help, Cheers, Paul Fri, 03 Dec 2010 14:20:07 GMT http://community.qnx.com/sf/go/post77060 Thilloy Paul 2010-12-03T14:20:07Z http://community.qnx.com/sf/go/post77049 Hi, You have a few options, as you mention. Photon is one, it is a traditional GUI with widgets (buttons, sliders, etc). You can use the Photon Application Builder in order to create an interface as you mentioned in the post. Flash would be another option, I can't really comment on examples or how you would create what you describe. Using the GF library is another option. It is a raw graphics library which you can render 2D content (or integrate OpenGL ES also). There are no GUI constructs so you end up coding things yourself, you have to create a button for example. http://www.qnx.com/developers/docs/6.4.0/gf/dev_guide/gf-base.html You could also use Crank's Storyboard. This is a Eclipse based user interface development tool and runtime. The tool can run on your host (windows/linux) and then simulate/test your design. Then you can run the same application on the QNX target system with no changes. You should quickly be able to build an interface as you describe. http://www.cranksoftware.com/products/crank_storyboard_suite.php Cheers, Brian Fri, 03 Dec 2010 13:37:16 GMT http://community.qnx.com/sf/go/post77049 Brian Edmond 2010-12-03T13:37:16Z http://community.qnx.com/sf/go/post77036 Hello, I'm totally new to Qnx. I'm trying in order to start, to develop a simple test application...let's stay modest at the beginning ! I want to implement a simple User Interface So for example, just a simple window with one button...you press it, it for example adds one to a counter or whatever operation and displays something back in the window ...label or I don't know... What should I use to do this ? Photon ? (it seems to be heavy for a simple purpose non ?) Flash (I could not find any example of such a simple app) ? Thanks for any of your advice, and sorry if I seems to be such a newbie :) Paul Fri, 03 Dec 2010 10:37:53 GMT http://community.qnx.com/sf/go/post77036 Thilloy Paul 2010-12-03T10:37:53Z