2008-02-04 18:01:49     chaotic window behavior in nano-x

Document created by Aaronwu Employee on Aug 5, 2013
Version 1Show Document
  • View in full screen mode

2008-02-04 18:01:49     chaotic window behavior in nano-x

Bill Fassler (UNITED STATES)

Message: 50656    On our custom BF561 boards where we have the cypress sl811 USB chip and the LQ043 LCD. I have managed to get USB HID working and hubs, mouse, keyboard all seem to register OK.

 

When I try to actually test it in nano-X I get the launcher menu screen up beautifully but when I click on anything, even the clock, I get mega-multiple moving windows.

 

I know you guys aren't nano-x developers but I feel this problem is more likely related to frequency/clock settings or something.  I've had this all working on the BF537-STAMP and so I am fairly confident I am configuring things correctly.  I've tried different async bank values to no avail.  Someone here said that perhaps it was a cache issue.

 

Is there anything that you guys can think of that might be the problem?

 

Bill

QuoteReplyEditDelete

 

 

2008-02-05 03:38:01     Re: chaotic window behavior in nano-x

Michael Hennerich (GERMANY)

Message: 50672    Can you explain in more detail:

>I get mega-multiple moving windows

 

-Michael

QuoteReplyEditDelete

 

 

2008-02-05 16:42:17     Re: chaotic window behavior in nano-x

Bill Fassler (UNITED STATES)

Message: 50713    Hmm, basically it opens up an entire vertical row of identical windows and then appears to continue opening windows growing horizontally, and the opened windows appear transparent to some extent.

 

A picture is worth a thousand words:

 

Before:

http://www.vocal.com/downloads/nanox-1.jpg

After launching a window:

http://www.vocal.com/downloads/nanox-4.jpg

 

My first guess would be something with the frame buffer or perhaps vsync or hsync with the LCD.  However, I have played movies before through mplayer and they seem ok, and I have also viewed pictures through jpegview.

 

I suppose the USB and/or Mouse driver might be suspect since this is the first time I have got it working and tried to use it, but the event_test(s) seem to go well.....

 

I just thought I toss it out as I usually do, and hope you guys have seen it before and can save me time (as you usually do)  ;-)

 

Bill

QuoteReplyEditDelete

 

 

2008-02-05 17:18:15     Re: chaotic window behavior in nano-x

Bill Fassler (UNITED STATES)

Message: 50714    Mike H. - As an afterthought I suppose I should mention that I do not yet have console on frame buffer enabled.  Also if I do not use launcher and just use command line to launch nxeyes, or nxclock or nxmag or nxroach all seems to go without a problem.  nxterm will not launch because it:

"can't create try /dev/ptyp0

 

The problem I describe only occurs with launcher.

 

Bill

QuoteReplyEditDelete

 

 

2008-02-06 05:38:53     Re: chaotic window behavior in nano-x

Michael Hennerich (GERMANY)

Message: 50729    Bill,

 

can you capture a screenshot, using the instructions here:

http://docs.blackfin.uclinux.org/doku.php?id=framebuffer

 

In case the screenshot and the display looks the same - it's a bug in nano-x.

 

-Michael

QuoteReplyEditDelete

 

 

2008-02-06 15:30:07     Re: chaotic window behavior in nano-x

Bill Fassler (UNITED STATES)

Message: 50771    Mike - I tried a screen capture as you suggested. I have no trouble capturing the frame buffer as long as nothing is being displayed, but I have failures when microwindows or mplayer is being displayed: I.E.

 

BEFORE APP:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

root:/dev> cat /dev/fb0 > /var/screen.raw

 

########  OPEN - bf561_lq043 ###########

 

########  READ  ###########

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

AFTER APP:

root:/dev> nano-X &

166

root:/dev>

########  OPEN - bf561_lq043 ###########

 

root:/dev> cat /dev/fb0 > /var/screen.raw

 

########  OPEN - bf561_lq043 ###########

cat: /dev/fb0: Bad address

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

Could this be a problem with our driver?

 

I did however manage to identify this problem with microwindows, specifically with the launcher.cnf file.

Someone (I assume Sonic) made several improvements to the nano-X for blackfin app.  However one

of the (apparently) newer things was that launcher.cnf automatically launches nanowm for you.

 

I am used to launching nano-X (the server) and nanowm (windows manager) manually so I can launch

the individual applications via command line. However now with the new launcher.cnf I wind up with TWO

versions of the windows manager (nanowm) running, which caused the problem I saw with multiple and endless windows being drawn.

 

(I also believe your current documentation states to launch both nano-X and nanowm manually.)

 

Ideally nanowm could be modified to dynamically check to see if it is already running before it launches again, but I doubt you want to spend time on software that isn't your responsibility.  I perhaps someday may look into it however I don't have the time now.

 

Also, I have trouble with launcher if I am not in the root directory because all the paths seem to be listed

as bin/.... and I believe things would work better from any directory if that was changed to /bin/..... (in launcher.cnf)

 

Anyway, I don't think any of these necessarily qualify as a "bug", but it was problematic for me.  I should have identified this sooner.

 

Bill

Attachments

    Outcomes