[GitHub] [incubator-nuttx] yukihiratype2 opened a new pull request #22: Add FMC SDRAM for STM32H7x3 chip

2020-01-01 Thread GitBox
yukihiratype2 opened a new pull request #22: Add FMC SDRAM for STM32H7x3 chip URL: https://github.com/apache/incubator-nuttx/pull/22 The STM32H7 chip's FMC is different from F7 or F4. H7 doesn't have BUSY register, instead, H7 requires set FMCEN on FMC_BCR1 after configured FMC registers.

Re: nxstyle (Was Re: Working Effectively (was Point of Order))

2020-01-01 Thread Haitao Liu
Yes, nxstyle check script comes at first. After it can check the PR patch, then I'll jump into the build stage including CI setup, autobuild. As to apache build, ZhangDuo or David may help in the process since they are familiar with apache infra and github integration. Gregory Nutt 于2020年1月2日周四 上

Re: End-of-year Clean-up

2020-01-01 Thread Nathan Hartman
On Wed, Jan 1, 2020 at 7:27 PM Alan Carvalho de Assis wrote: > HI Nathan, > > On 1/1/20, Nathan Hartman wrote: > > On Wed, Jan 1, 2020 at 1:14 PM Alan Carvalho de Assis > > > wrote: > >> On 1/1/20, Gregory Nutt wrote: > >> > * Brennan has done the Confluence pages, investigated Jira, create

Re: nxstyle (Was Re: Working Effectively (was Point of Order))

2020-01-01 Thread Gregory Nutt
Thanks your detailed explanation to nxstyle. I'll try my best to update nxstyle step by step. You also have other responsibilities with the tooling for the workflow, correct?  If you need any help with nxstyle, I can also work with it.  Let me know if you need anything.

Re: nxstyle (Was Re: Working Effectively (was Point of Order))

2020-01-01 Thread Haitao Liu
Thanks your detailed explanation to nxstyle. I'll try my best to update nxstyle step by step. Gregory Nutt 于2020年1月1日周三 上午4:42写道: > > > For (1) false negatives, I just create a few simple test files and > > verify that nxstyle detects the error. Pretty easy. > > > > For (2) false positives, it i

[MENTORS] Report formatting issues

2020-01-01 Thread Justin Mclean
Hi, We had a large number of reports that needed manual editing to fix formatting issues this month. Podlings that required to most changes have been BCCed. Please try and follow teh instructions at the top of the page and and keep the formatting consistent. II’s best to follow what is below:

Re: End-of-year Clean-up

2020-01-01 Thread Alan Carvalho de Assis
HI Nathan, On 1/1/20, Nathan Hartman wrote: > On Wed, Jan 1, 2020 at 1:14 PM Alan Carvalho de Assis > wrote: >> On 1/1/20, Gregory Nutt wrote: >> > * Brennan has done the Confluence pages, investigated Jira, create >> > the >> > initial workflow page >> > * Nathan have been staying busy

[GitHub] [incubator-nuttx-website] btashton commented on issue #6: publish the website

2020-01-01 Thread GitBox
btashton commented on issue #6: publish the website URL: https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570095220 I'll take a look tonight, but this does not look right to me. If we are manually generating the site branch content then I would think it should only be

[GitHub] [incubator-nuttx-website] Ouss4 commented on issue #6: publish the website

2020-01-01 Thread GitBox
Ouss4 commented on issue #6: publish the website URL: https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-570094059 As far as publishing the website, the change looks good. This is an automated message from

Re: End-of-year Clean-up

2020-01-01 Thread Nathan Hartman
On Wed, Jan 1, 2020 at 1:14 PM Alan Carvalho de Assis wrote: > On 1/1/20, Gregory Nutt wrote: > > * Brennan has done the Confluence pages, investigated Jira, create the > > initial workflow page > > * Nathan have been staying busy with the workflow > > * Abdelatif has been working a lot

[GitHub] [incubator-nuttx] acassis commented on issue #14: Fixed includes in arch/arm/src/stm32l4/hardware/.

2020-01-01 Thread GitBox
acassis commented on issue #14: Fixed includes in arch/arm/src/stm32l4/hardware/. URL: https://github.com/apache/incubator-nuttx/pull/14#issuecomment-570075877 Hi wingunder, please note that normally header files included inside stm32l4/hardware/ directory are mainly used for internal chip

Re: End-of-year Clean-up

2020-01-01 Thread Gregory Nutt
I want to help reviewing the patches and be guided by you to do it well. Thanks, Alan! Imagine if we all tried to dispose on one PR per day.  That would be eleven PRs per day, 77 PRs per week, week could keep up with things without stressing anyone. Of course, it will be even easier when

Re: ILI9341 port to STM32F4

2020-01-01 Thread Dave Marples
Ben, I have this up and running on an imxrt with a 'generic' spi driver (i.e.that should work with any spi device rather than the platform specific one that was previously in use). When I'm back at my desk this evening I'll send the files to you so you can compare and contrast to make something su

[GitHub] [incubator-nuttx] patacongo closed pull request #14: Fixed includes in arch/arm/src/stm32l4/hardware/.

2020-01-01 Thread GitBox
patacongo closed pull request #14: Fixed includes in arch/arm/src/stm32l4/hardware/. URL: https://github.com/apache/incubator-nuttx/pull/14 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [incubator-nuttx] patacongo commented on issue #14: Fixed includes in arch/arm/src/stm32l4/hardware/.

2020-01-01 Thread GitBox
patacongo commented on issue #14: Fixed includes in arch/arm/src/stm32l4/hardware/. URL: https://github.com/apache/incubator-nuttx/pull/14#issuecomment-570074562 I don't believe this change should be incorporated upstream. It does not handle the include paths and it takes perfectly compli

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
I am trying to put it all together, because I am not using the STM32F429i-disco with integrated TFT-LCD. But a ILI9431 Here I could find the Memory regions (also FMC and 3 memory regions [if I get it right...]) https://www.st.com/content/ccc/resource/technical/document/application_note/group0/25/c

Re: ILI9341 port to STM32F4

2020-01-01 Thread Gregory Nutt
Disabling the colormap config (CONFIG_STM32_FB_CMAP) it gives a white screen (no text "Hello World"), but no hardfault... and if I start nxhello for the second time I get: stm32_spi2select: devid: 262144 CS: assert White is probably better.  That just means that the data sent to the LCD is bad

Re: ILI9341 port to STM32F4

2020-01-01 Thread Gregory Nutt
Does that hardware support color mapping?  Normally that is used with 8-bit palette colors like old fashioned computers from the 80's.  You probably don't want it. On 1/1/2020 11:56 AM, Disruptive Solutions wrote: I am close, but looking in a loop? In ili9341_getvideoinfo the vinfo struct is

Re: End-of-year Clean-up

2020-01-01 Thread Alan Carvalho de Assis
Hi Greg, On 1/1/20, Gregory Nutt wrote: > We need to reset the conversation because it has gotten so far off track > that the point has been completely lost. We need to pay attention and > not get distracted by the shiny objects. > > Repeating: > > > > Would it make sense, then, to begin a tran

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
I am close, but looking in a loop? In ili9341_getvideoinfo the vinfo struct is filled correctly? fmt = 11 xres = 320 yres = 240 nplanes = 1 noverlays = 0 Is seems that the colormap is setting some problems in nxbe_colormap.c (lcd.h) /* Then set the color map */ ret = dev->putcmap(dev, &cmap);

Re: End-of-year Clean-up

2020-01-01 Thread Gregory Nutt
Sorry, I misunderstand that you suggest this will be the new workflow. Okay.  No problem.  Although I did feel like I was being attacked from all sides for just trying to make to progress. All discussion of the new workflow is happening here: https://cwiki.apache.org/confluence/display/NU

[GitHub] [incubator-nuttx-apps] patacongo merged pull request #3: Add .updated target to handle the no builtin app case correctly

2020-01-01 Thread GitBox
patacongo merged pull request #3: Add .updated target to handle the no builtin app case correctly URL: https://github.com/apache/incubator-nuttx-apps/pull/3 This is an automated message from the Apache Git Service. To respon

Re: End-of-year Clean-up

2020-01-01 Thread Gregory Nutt
We need to reset the conversation because it has gotten so far off track that the point has been completely lost.  We need to pay attention and not get distracted by the shiny objects. Repeating: > > Would it make sense, then, to begin a transition period now? That is, > > start a gradual move

Re: ILI9341 port to STM32F4

2020-01-01 Thread spudaneco
Sent from Samsung tablet. It seems strange that by not selecting CONFIG_NX_KBD it stil is trying tocompile stuff that has relations with this config?src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl' has nomember named 'doubleClick'   if (m_flags.doubleClickable && hasFocus() &&

Re: ILI9341 port to STM32F4

2020-01-01 Thread spudaneco
Looks fine to me.  Same document is in nuttx/DocumentsSent from Samsung tablet. null

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
This has docu... http://nuttx.org/doku.php?id=documentation:nxgraphics --> Strange... sometimes its white? Op wo 1 jan. 2020 om 11:47 schreef Disruptive Solutions < disruptivesolution...@gmail.com>: > I wanted to use NX on the ILI9341... but is the documentation somewhere > filled? Or are there

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
I wanted to use NX on the ILI9341... but is the documentation somewhere filled? Or are there some examples how to configure this? https://nuttx.org/doku.php?id=documentation:nxgraphics --> Is empty? Ben Op wo 1 jan. 2020 om 11:31 schreef Disruptive Solutions < disruptivesolution...@gmail.com>:

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
I just checked your proposal Brennan. In my install base it's not doing it for me. Eclipse does. I already had this extension installed. To bad though. I really loved Visual Studio Code and I can use it for some coding... but for debugging I have to jump to Eclipse. Ben Op wo 1 jan. 2020 om 11:20

Re: Podling Nuttx Report Reminder - January 2020

2020-01-01 Thread Abdelatif Guettouche
> > Just a friendly reminder that this report is now due, can one of the PPMC > members please submit it. It's done. On Wed, Jan 1, 2020 at 8:24 AM Justin Mclean wrote: > Hi, > > Just a friendly reminder that this report is now due, can one of the PPMC > members please submit it. > > To set ex

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
In have Cortex-Debug but I have to look at this, maybe its a different version. In my version I could not Copy-Paste the LR register address in PC and then go from there Verstuurd vanaf mijn iPhone > Op 1 jan. 2020 om 10:50 heeft Brennan Ashton het > volgende geschreven: > > Ben, > If y

Re: ILI9341 port to STM32F4

2020-01-01 Thread Brennan Ashton
Ben, If you want to use vscode use this extension. https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug It gives you the debug functionality that you are asking about. There are also a lot of other powerful features if you dig into setting it up including ITM graphing. --Bren

Re: ILI9341 port to STM32F4

2020-01-01 Thread Disruptive Solutions
Thank you David! I do not need to make a new video, your video is very clear! And I always give credits to the people who deserve it ;-) The https://mcuoneclipse.com/2012/10/27/assembly-instruction-stepping/ is very useful and this seems to make Eclipse the only IDE that has this feature..? It see

Re: Podling Nuttx Report Reminder - January 2020

2020-01-01 Thread Justin Mclean
Hi, Just a friendly reminder that this report is now due, can one of the PPMC members please submit it. To set expectations: If you fail to report on time you will be ask to report next month, it’s not a big deal but it’s preferable that you report on time each time, miss two reports and quest