Re: NX Graphics

2020-01-05 Thread Disruptive Solutions
ERROR: Failed to allocate frame buffer memory\n"); >> >> What am I overlooking here? Yes fbmem is 0... . >> >> Total; used; free; largest; >> Umem: 191920 7568 184352 124192 >> >> Be

Re: NX Graphics

2020-01-05 Thread Gregory Nutt
Total; used; free; largest; Umem: 191920 7568 184352 124192 Ben -Oorspronkelijk bericht- Van: Gregory Nutt Verzonden: zaterdag 4 januari 2020 22:39 Aan: dev@nuttx.apache.org Onderwerp: Re: NX Graphics Priv->fblen = 0 Trying to allocate a buffer of zero length will return the value NULL too.

RE: NX Graphics

2020-01-05 Thread disruptivesolutionsnl
Umem: 191920 7568 184352 124192 Ben -Oorspronkelijk bericht- Van: Gregory Nutt Verzonden: zaterdag 4 januari 2020 22:39 Aan: dev@nuttx.apache.org Onderwerp: Re: NX Graphics > Priv->fblen = 0 Trying to allocate a buffer of zero length will return the value NULL too.

Re: NX Graphics

2020-01-04 Thread Gregory Nutt
Priv->fblen = 0 Trying to allocate a buffer of zero length will return  the value NULL too.

RE: NX Graphics

2020-01-04 Thread disruptivesolutionsnl
Priv->fblen = 0 -Oorspronkelijk bericht- Van: Gregory Nutt Verzonden: zaterdag 4 januari 2020 21:02 Aan: dev@nuttx.apache.org Onderwerp: Re: NX Graphics > nsh> free > > procfs_open: Open 'meminfo' > > meminfo_open: Open 'meminfo' >

RE: NX Graphics

2020-01-04 Thread disruptivesolutionsnl
Ow and PS: With FSMC I could allocate the framebuffer tot he ILI9341??? -Oorspronkelijk bericht- Van: Gregory Nutt Verzonden: zaterdag 4 januari 2020 21:09 Aan: dev@nuttx.apache.org Onderwerp: Re: NX Graphics >> priv->fbmem = 0 > But what was priv->fblen? The size yo

RE: NX Graphics

2020-01-04 Thread disruptivesolutionsnl
Yes... but where does it get set? I tried the f429i and compared "free": (picture… hope it shows) -Oorspronkelijk bericht- Van: Gregory Nutt Verzonden: zaterdag 4 januari 2020 21:09 Aan: dev@nuttx.apache.org Onderwerp: Re: NX Graphics >> priv->fb

Re: NX Graphics

2020-01-04 Thread Gregory Nutt
priv->fbmem = 0 But what was priv->fblen?  The size you are trying to allocate? If it is greater then 124,848 then the allocation will fail. For 16-bit color and 320x240 LCD you would need to allocate 2*320*240 = 153,600 then I would expect priv->fblen to be 153,600 and I would expect the

Re: NX Graphics

2020-01-04 Thread Gregory Nutt
nsh> free procfs_open: Open 'meminfo' meminfo_open: Open 'meminfo' procfs_read: buffer=0x16d0 buflen=512 meminfo_read: buffer=0x16d0 buflen=512 total used freelargest Umem: 192576 7696 184880 124848 procfs_read: buffer=0x16d0

RE: NX Graphics

2020-01-04 Thread disruptivesolutionsnl
read: buffer=0x16d0 buflen=512 meminfo_read: buffer=0x16d0 buflen=512 nsh> priv->fbmem = 0 -Oorspronkelijk bericht- Van: Gregory Nutt Verzonden: zaterdag 4 januari 2020 19:38 Aan: dev@nuttx.apache.org Onderwerp: Re: NX Graphics Do you have enough memory to allocate the frame

Re: NX Graphics

2020-01-04 Thread Gregory Nutt
Do you have enough memory to allocate the framebuffer?  What is the value of priv->fblen?  What is the size of the allocated heap?  Try "nsh> free" On 1/4/2020 11:44 AM, disruptivesolution...@gmail.com wrote: priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen); if (priv->fbmem == NULL

RE: NX Graphics

2020-01-04 Thread disruptivesolutionsnl
priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen); if (priv->fbmem == NULL) { lcderr("ERROR: Failed to allocate frame buffer memory\n"); I dont seem to get fbmem filled. tried all config options, but it stays empty. I do not have NX(WM) activated. The framebuffer should be