[GitHub] [incubator-nuttx] yukihiratype2 opened a new pull request #22: Add FMC SDRAM for STM32H7x3 chip
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. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: nxstyle (Was Re: Working Effectively (was Point of Order))
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日周四 上午10:25写道： > > > 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: End-of-year Clean-up
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 > >> > the > >> > initial workflow page > >> > * Nathan have been staying busy with the workflow > >> > * Abdelatif has been working a lot with PPMC/committer membership, > >> > monthly status report > >> > * I have been doing all of the commits. > >> > > >> > What about the remaining seven people? Is there no one who wants to > >> > get > >> > their feet wet? If we are going survive the next months, we all have > >> > to > >> > pitch in and work together. > >> > > >> > >> I want to help reviewing the patches and be guided by you to do it well. > >> > >> In this mean time I took a look at the Workflow page > >> ( > https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton > ) > >> and I think it is not describing the Process, so I will try to get > >> your suggested steps and include it there. > >> > >> We could use the Mynewt page as reference: > >> > >> > https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests > >> > >> Not their process, but their structure more direct to the goal. > > > > Thank you Alan. > > > > I will greatly appreciate help in getting the workflow complete. > > > > Feel free to edit and reorganize anything in that document to help > > make it more readable and helpful. > > > > Please keep in mind that our document addresses more things that > > aren't discussed in MYNEWT's workflow: > > > > Yes, it is true. > > After comparing things I think the "NuttX Workflow" will be to much > for a newcomer read if he/she just want to submit a patch/PR. > > I think we could have the Workflow document (mostly focused on > Committer) and a document simpler to explain how to submit patches/PR. > We could recommend reading but Workflow, but it could be optional. Perhaps there will be numerous subjects (for example we didn't discuss release process yet) and especially after we fill in a lot of details, it will be even longer. So maybe there should be a landing page with links to separate pages for each subject. Nathan
Re: nxstyle (Was Re: Working Effectively (was Point of Order))
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))
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 is a little more difficult. I use > > nuttx/sched to do these because it probably follows the coding > > standard the best. ... > > > There is another test that is needed. When we add a new test to > nxstyle.c, we may often break other logic that detects different coding > standard violations. The above do not address that. > > I think we would need to collect a directory full of code with known > coding standard violations and run and modified nxstyle against those to > to assure that we have not broken other detection logic. > > The code in nxstyle is not pretty. It uses many booleans and line > number varialbes to detect problems through some really rather crude > heuristics (it knows nothing about C syntax). Since it is convoluted, > unexpected side effects and unexpected breakage is really common. > > Greg > > > >
[MENTORS] Report formatting issues
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: • Do not change existing formatting. • Keep all lines under 76 characters long. • All content under the ### headings should be indented by two spaces. Do not use tabs. • Please don't change the text in the headings or add new ones. • Include a space after a bullet point or full stop on a numbered list. • Use [X] (X and no spaces) to sign off reports. • Do not include long URLs and use apache URL shortener https://s.apache.org. Reflowing the text like below can fix some of the above issues but not all. fold -w 76 -s $1 | cat -s Thanks, Justin
Re: End-of-year Clean-up
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 with the workflow >> > * Abdelatif has been working a lot with PPMC/committer membership, >> > monthly status report >> > * I have been doing all of the commits. >> > >> > What about the remaining seven people? Is there no one who wants to >> > get >> > their feet wet? If we are going survive the next months, we all have >> > to >> > pitch in and work together. >> > >> >> I want to help reviewing the patches and be guided by you to do it well. >> >> In this mean time I took a look at the Workflow page >> (https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton) >> and I think it is not describing the Process, so I will try to get >> your suggested steps and include it there. >> >> We could use the Mynewt page as reference: >> >> https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests >> >> Not their process, but their structure more direct to the goal. > > Thank you Alan. > > I will greatly appreciate help in getting the workflow complete. > > Feel free to edit and reorganize anything in that document to help > make it more readable and helpful. > > Please keep in mind that our document addresses more things that > aren't discussed in MYNEWT's workflow: > Yes, it is true. After comparing things I think the "NuttX Workflow" will be to much for a newcomer read if he/she just want to submit a patch/PR. I think we could have the Workflow document (mostly focused on Committer) and a document simpler to explain how to submit patches/PR. We could recommend reading but Workflow, but it could be optional. > * Where is the code and how to get a copy of it > > * The workflow itself (currently lacks all details) > > * Criteria for acceptance, which currently is very basic and has no > details but it will gradually develop over time > > * A reference for us committers, to guide us in merging the > contributions safely to git without messing up the repositories > > Any area(s) where you can help, we'll all appreciate it very much. > Ok, I will keep getting feedbacks and editing it. Thank you very much! BR, Alan
[GitHub] [incubator-nuttx-website] btashton commented on issue #6: publish the website
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 the static content, none of the other stuff, but I want to make sure I understand it from the Apache side. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-nuttx-website] Ouss4 commented on issue #6: publish the website
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 the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: End-of-year Clean-up
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 with PPMC/committer membership, > > monthly status report > > * I have been doing all of the commits. > > > > What about the remaining seven people? Is there no one who wants to get > > their feet wet? If we are going survive the next months, we all have to > > pitch in and work together. > > > > I want to help reviewing the patches and be guided by you to do it well. > > In this mean time I took a look at the Workflow page > (https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton) > and I think it is not describing the Process, so I will try to get > your suggested steps and include it there. > > We could use the Mynewt page as reference: > > https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests > > Not their process, but their structure more direct to the goal. Thank you Alan. I will greatly appreciate help in getting the workflow complete. Feel free to edit and reorganize anything in that document to help make it more readable and helpful. Please keep in mind that our document addresses more things that aren't discussed in MYNEWT's workflow: * Where is the code and how to get a copy of it * The workflow itself (currently lacks all details) * Criteria for acceptance, which currently is very basic and has no details but it will gradually develop over time * A reference for us committers, to guide us in merging the contributions safely to git without messing up the repositories Any area(s) where you can help, we'll all appreciate it very much. Thanks again, Nathan
[GitHub] [incubator-nuttx] acassis commented on issue #14: Fixed includes in arch/arm/src/stm32l4/hardware/.
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 registers definitions and the headers at base of stm324/ contains definitions that will be outside of arch/ dir i.e. inside boards/ . Also note that all arch follow this logic, if you want to change it you need to do it for all arch, not only for stm32l4. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: End-of-year Clean-up
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 the fully agreed to, automated work flow is in place. But we need to handle changes however we can until that day arrives. I think we could have work flow requirements in a 1-2 weeks and possibly some automation help a few weeks after that. Greg
Re: ILI9341 port to STM32F4
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 suitable for inclusion based on what you've already got. Regards Dave On Wed, 1 Jan 2020, 18:39 Gregory Nutt, wrote: > > > 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 (all ones?) but the backlight is on. > > ili9341_getplaneinfo: planeno: 0 bpp: 16 > bpp=16, certainly you are not using a colormap. > > * and if I start nxhello for the second time I get: * > > The example probably does not disconnect from NX. If it did disconnt, > the screen should go black you would see nothing. I think all of the > other nxhello examples run standalone (not sure). > > >
[GitHub] [incubator-nuttx] patacongo closed pull request #14: Fixed includes in arch/arm/src/stm32l4/hardware/.
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, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-nuttx] patacongo commented on issue #14: Fixed includes in arch/arm/src/stm32l4/hardware/.
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 compliant code and makes it inconsistent with everyother architecute. Consistency must be preserved. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: ILI9341 port to STM32F4
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/ca/f9/b4/ae/fc/4e/1e/DM00287603/files/DM00287603.pdf/jcr:content/translations/en.DM00287603.pdf And this is my datasheet for the ILI9341 and its a QVGA (320 x 240) https://cdn-shop.adafruit.com/datasheets/ILI9341.pdf The display: https://www.ebay.com/itm/3-2-inch-LCD-TFT-With-Resistive-Touch-Screen-ILI9341-Display-Module-320-240-/183001025101 When the memory regions are not correct defined I do get that I get hardfaults... but I am struggling with these definitions. CONFIG_STM32_DMA2D_FB_BASE=0xD07B5000 CONFIG_STM32_DMA2D_FB_SIZE=15 CONFIG_STM32_DMA2D_LAYER_PPLINE=240 CONFIG_STM32_DMA2D_NLAYERS=2 CONFIG_STM32_LTDC=y CONFIG_STM32_LTDC_FB_BASE=0xD076A000 CONFIG_STM32_LTDC_FB_SIZE=15 CONFIG_HEAP2_BASE=0xD000 CONFIG_HEAP2_SIZE=15 Op wo 1 jan. 2020 om 19:29 schreef 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 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); > > > > 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 > > > > stm32_ili93414ws_sendcmd: cmd=0029 > > > > stm32_spi2select: devid: 262144 CS: de-assert > > > > ili9341_getvideoinfo: fmt: 11 xres: 320 yres: 240 nplanes: 1 > > > > ili9341_getplaneinfo: planeno: 0 bpp: 16 > > > > > > * and if I start nxhello for the second time I get: * > > > > nsh> nxhello > > > > nxhello_initialize: nx_connect failed: 28 > > > > nxhello_main: NX handle=0 > > > > nxhello_main: Failed to get NX handle: 28 > > > > nsh> > > > > Somebody has an idea? > > > > Op wo 1 jan. 2020 om 13:06 schreef 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() &&m_widgetControl->doubleClick())DoubleClick has nothing to > do > >> with the ketboard. That is mouse codeAnd other problems. It seems I > have > >> to make changes in the NX side of Nuttxto get this going..?I don't > >> understand that. > > >
Re: ILI9341 port to STM32F4
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 (all ones?) but the backlight is on. ili9341_getplaneinfo: planeno: 0 bpp: 16 bpp=16, certainly you are not using a colormap. * and if I start nxhello for the second time I get: * The example probably does not disconnect from NX. If it did disconnt, the screen should go black you would see nothing. I think all of the other nxhello examples run standalone (not sure).
Re: ILI9341 port to STM32F4
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 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); 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 stm32_ili93414ws_sendcmd: cmd=0029 stm32_spi2select: devid: 262144 CS: de-assert ili9341_getvideoinfo: fmt: 11 xres: 320 yres: 240 nplanes: 1 ili9341_getplaneinfo: planeno: 0 bpp: 16 * and if I start nxhello for the second time I get: * nsh> nxhello nxhello_initialize: nx_connect failed: 28 nxhello_main: NX handle=0 nxhello_main: Failed to get NX handle: 28 nsh> Somebody has an idea? Op wo 1 jan. 2020 om 13:06 schreef 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() &&m_widgetControl->doubleClick())DoubleClick has nothing to do with the ketboard. That is mouse codeAnd other problems. It seems I have to make changes in the NX side of Nuttxto get this going..?I don't understand that.
Re: End-of-year Clean-up
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 transition period now? That is, > > > start a gradual move from the current state where Greg is reviewing > > > and merging all changes, toward the direction */where other > committers/* > > > */are reviewing/merging changes/*. Perhaps, for the next couple of > weeks, > > > Greg could continue reviewing and merging to the more finicky areas > > > like the build system, while /*other committers start getting their > feet*/ > > > */wet by reviewing and merging changes/* to areas less likely to bring > > > breakage? I think Greg should be mentoring us in the art of handling > > > contributions, instead of doing all the drudge work himself. > > > > That sounds like a good idea. Let me summarize what I do. This is > /*not*/ > > /*the official workflow*/! It is basically the/*legacy way*/ I have > been > > doing things translated in to this new environment. ... > > To that I got two responses critical the seat-of-the-pants workflow I am > using and on critical of me personally. Not helpful. > > We need to revisit. There are /eleven /people who have committed to > helping out as members of the PPMC or as commiters. > > * 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 with PPMC/committer membership, > monthly status report > * I have been doing all of the commits. > > What about the remaining seven people? Is there no one who wants to get > their feet wet? If we are going survive the next months, we all have to > pitch in and work together. > I want to help reviewing the patches and be guided by you to do it well. In this mean time I took a look at the Workflow page (https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton) and I think it is not describing the Process, so I will try to get your suggested steps and include it there. We could use the Mynewt page as reference: https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests Not their process, but their structure more direct to the goal. BR, Alan
Re: ILI9341 port to STM32F4
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); 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 stm32_ili93414ws_sendcmd: cmd=0029 stm32_spi2select: devid: 262144 CS: de-assert ili9341_getvideoinfo: fmt: 11 xres: 320 yres: 240 nplanes: 1 ili9341_getplaneinfo: planeno: 0 bpp: 16 * and if I start nxhello for the second time I get: * nsh> nxhello nxhello_initialize: nx_connect failed: 28 nxhello_main: NX handle=0 nxhello_main: Failed to get NX handle: 28 nsh> Somebody has an idea? Op wo 1 jan. 2020 om 13:06 schreef 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() &&m_widgetControl->doubleClick())DoubleClick has nothing to do > with the ketboard. That is mouse codeAnd other problems. It seems I have > to make changes in the NX side of Nuttxto get this going..?I don't > understand that.
Re: End-of-year Clean-up
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/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton I invite everyone to participate. Greg
[GitHub] [incubator-nuttx-apps] patacongo merged pull request #3: Add .updated target to handle the no builtin app case correctly
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 respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: End-of-year Clean-up
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 from the current state where Greg is reviewing > > and merging all changes, toward the direction */where other committers/* > > */are reviewing/merging changes/*. Perhaps, for the next couple of weeks, > > Greg could continue reviewing and merging to the more finicky areas > > like the build system, while /*other committers start getting their feet*/ > > */wet by reviewing and merging changes/* to areas less likely to bring > > breakage? I think Greg should be mentoring us in the art of handling > > contributions, instead of doing all the drudge work himself. > > That sounds like a good idea. Let me summarize what I do. This is /*not*/ > /*the official workflow*/! It is basically the/*legacy way*/ I have been > doing things translated in to this new environment. ... To that I got two responses critical the seat-of-the-pants workflow I am using and on critical of me personally. Not helpful. We need to revisit. There are /eleven /people who have committed to helping out as members of the PPMC or as commiters. * 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 with PPMC/committer membership, monthly status report * I have been doing all of the commits. What about the remaining seven people? Is there no one who wants to get their feet wet? If we are going survive the next months, we all have to pitch in and work together. Greg
Re: ILI9341 port to STM32F4
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() &&m_widgetControl->doubleClick())DoubleClick has nothing to do with the ketboard. That is mouse codeAnd other problems. It seems I have to make changes in the NX side of Nuttxto get this going..?I don't understand that.
Re: ILI9341 port to STM32F4
Looks fine to me. Same document is in nuttx/DocumentsSent from Samsung tablet. null
Re: ILI9341 port to STM32F4
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 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>:
>
>> 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 schreef Disruptive Solutions <
>> disruptivesolution...@gmail.com>:
>>
>>> 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 <
>>> bash...@brennanashton.com> het volgende geschreven:
>>> >
>>> > 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.
>>> >
>>> > --Brennan
>>> >
>>> >> On Wed, Jan 1, 2020, 1:38 AM Disruptive Solutions <
>>> >> disruptivesolution...@gmail.com> wrote:
>>> >>
>>> >> 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 seems to exclude on this criteria Visual Studio Code...
>>> that
>>> >> is a shame..?
>>> >>
>>> >> I have some NX questions and keep getting hardfaults the first
>>> >> hardfault I solved ;-) It was a too large FB size.
>>> >>
>>> >> It seems strange that by not selecting CONFIG_NX_KBD it stil is
>>> trying to
>>> >> compile stuff that has relations with this config?
>>> >>
>>> >> src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl'
>>> has no
>>> >> member named 'doubleClick'
>>> >> if (m_flags.doubleClickable && hasFocus() &&
>>> >> m_widgetControl->doubleClick())
>>> >>
>>> >> And other problems. It seems I have to make changes in the NX side of
>>> Nuttx
>>> >> to get this going..?
>>> >>
>>> >> Ben
>>> >>
>>> >> Op zo 29 dec. 2019 om 19:44 schreef Disruptive Solutions <
>>> >> disruptivesolution...@gmail.com>:
>>> >>
>>> >>> It looks like its happening here... (type previous mail: graphical)
>>> >>>
>>> >>> stm32_ltdc_lclear(overlay);
>>> >>>
>>> >>> /* Set layers framebuffer */
>>> >>>
>>> >>> stm32_ltdc_lframebuffer(layer); <---??
>>> >>>
>>> >>> Op zo 29 dec. 2019 om 19:39 schreef Disruptive Solutions <
>>> >>> disruptivesolution...@gmail.com>:
>>> >>>
>>> I have most of it done for porting the grapical TFT-LCD ILI9341
>>> through
>>> SPI...
>>>
>>> But I get a PANIC when it is trying to do:
>>> stm32_ltds_linit(LTDC_LAYER_L1); in stm32_ltdc.c
>>>
>>> Does someone know this?
>>>
>>> Ben
>>>
>>> /* Initialize ltdc layer */
>>>
>>> lcdinfo("Initialize ltdc layer\n");
>>> stm32_ltdc_linit(LTDC_LAYER_L1);
>>> #ifdef CONFIG_STM32_LTDC_L2
>>> stm32_ltdc_linit(LTDC_LAYER_L2);
>>> #endif
>>>
>>>
>>> >>
>>>
>>
Re: ILI9341 port to STM32F4
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>:
> 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 schreef Disruptive Solutions <
> disruptivesolution...@gmail.com>:
>
>> 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 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.
>> >
>> > --Brennan
>> >
>> >> On Wed, Jan 1, 2020, 1:38 AM Disruptive Solutions <
>> >> disruptivesolution...@gmail.com> wrote:
>> >>
>> >> 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 seems to exclude on this criteria Visual Studio Code...
>> that
>> >> is a shame..?
>> >>
>> >> I have some NX questions and keep getting hardfaults the first
>> >> hardfault I solved ;-) It was a too large FB size.
>> >>
>> >> It seems strange that by not selecting CONFIG_NX_KBD it stil is trying
>> to
>> >> compile stuff that has relations with this config?
>> >>
>> >> src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl' has
>> no
>> >> member named 'doubleClick'
>> >> if (m_flags.doubleClickable && hasFocus() &&
>> >> m_widgetControl->doubleClick())
>> >>
>> >> And other problems. It seems I have to make changes in the NX side of
>> Nuttx
>> >> to get this going..?
>> >>
>> >> Ben
>> >>
>> >> Op zo 29 dec. 2019 om 19:44 schreef Disruptive Solutions <
>> >> disruptivesolution...@gmail.com>:
>> >>
>> >>> It looks like its happening here... (type previous mail: graphical)
>> >>>
>> >>> stm32_ltdc_lclear(overlay);
>> >>>
>> >>> /* Set layers framebuffer */
>> >>>
>> >>> stm32_ltdc_lframebuffer(layer); <---??
>> >>>
>> >>> Op zo 29 dec. 2019 om 19:39 schreef Disruptive Solutions <
>> >>> disruptivesolution...@gmail.com>:
>> >>>
>> I have most of it done for porting the grapical TFT-LCD ILI9341
>> through
>> SPI...
>>
>> But I get a PANIC when it is trying to do:
>> stm32_ltds_linit(LTDC_LAYER_L1); in stm32_ltdc.c
>>
>> Does someone know this?
>>
>> Ben
>>
>> /* Initialize ltdc layer */
>>
>> lcdinfo("Initialize ltdc layer\n");
>> stm32_ltdc_linit(LTDC_LAYER_L1);
>> #ifdef CONFIG_STM32_LTDC_L2
>> stm32_ltdc_linit(LTDC_LAYER_L2);
>> #endif
>>
>>
>> >>
>>
>
Re: ILI9341 port to STM32F4
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 schreef Disruptive Solutions <
disruptivesolution...@gmail.com>:
> 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 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.
> >
> > --Brennan
> >
> >> On Wed, Jan 1, 2020, 1:38 AM Disruptive Solutions <
> >> disruptivesolution...@gmail.com> wrote:
> >>
> >> 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 seems to exclude on this criteria Visual Studio Code...
> that
> >> is a shame..?
> >>
> >> I have some NX questions and keep getting hardfaults the first
> >> hardfault I solved ;-) It was a too large FB size.
> >>
> >> It seems strange that by not selecting CONFIG_NX_KBD it stil is trying
> to
> >> compile stuff that has relations with this config?
> >>
> >> src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl' has
> no
> >> member named 'doubleClick'
> >> if (m_flags.doubleClickable && hasFocus() &&
> >> m_widgetControl->doubleClick())
> >>
> >> And other problems. It seems I have to make changes in the NX side of
> Nuttx
> >> to get this going..?
> >>
> >> Ben
> >>
> >> Op zo 29 dec. 2019 om 19:44 schreef Disruptive Solutions <
> >> disruptivesolution...@gmail.com>:
> >>
> >>> It looks like its happening here... (type previous mail: graphical)
> >>>
> >>> stm32_ltdc_lclear(overlay);
> >>>
> >>> /* Set layers framebuffer */
> >>>
> >>> stm32_ltdc_lframebuffer(layer); <---??
> >>>
> >>> Op zo 29 dec. 2019 om 19:39 schreef Disruptive Solutions <
> >>> disruptivesolution...@gmail.com>:
> >>>
> I have most of it done for porting the grapical TFT-LCD ILI9341
> through
> SPI...
>
> But I get a PANIC when it is trying to do:
> stm32_ltds_linit(LTDC_LAYER_L1); in stm32_ltdc.c
>
> Does someone know this?
>
> Ben
>
> /* Initialize ltdc layer */
>
> lcdinfo("Initialize ltdc layer\n");
> stm32_ltdc_linit(LTDC_LAYER_L1);
> #ifdef CONFIG_STM32_LTDC_L2
> stm32_ltdc_linit(LTDC_LAYER_L2);
> #endif
>
>
> >>
>
Re: Podling Nuttx Report Reminder - January 2020
> > 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 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 questions will be asked, and worse > case if you fail to report three or four times then it’s likely you’ll be > removed from the incubator. > > Thanks, > Justin
Re: ILI9341 port to STM32F4
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 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.
>
> --Brennan
>
>> On Wed, Jan 1, 2020, 1:38 AM Disruptive Solutions <
>> disruptivesolution...@gmail.com> wrote:
>>
>> 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 seems to exclude on this criteria Visual Studio Code... that
>> is a shame..?
>>
>> I have some NX questions and keep getting hardfaults the first
>> hardfault I solved ;-) It was a too large FB size.
>>
>> It seems strange that by not selecting CONFIG_NX_KBD it stil is trying to
>> compile stuff that has relations with this config?
>>
>> src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl' has no
>> member named 'doubleClick'
>> if (m_flags.doubleClickable && hasFocus() &&
>> m_widgetControl->doubleClick())
>>
>> And other problems. It seems I have to make changes in the NX side of Nuttx
>> to get this going..?
>>
>> Ben
>>
>> Op zo 29 dec. 2019 om 19:44 schreef Disruptive Solutions <
>> disruptivesolution...@gmail.com>:
>>
>>> It looks like its happening here... (type previous mail: graphical)
>>>
>>> stm32_ltdc_lclear(overlay);
>>>
>>> /* Set layers framebuffer */
>>>
>>> stm32_ltdc_lframebuffer(layer); <---??
>>>
>>> Op zo 29 dec. 2019 om 19:39 schreef Disruptive Solutions <
>>> disruptivesolution...@gmail.com>:
>>>
I have most of it done for porting the grapical TFT-LCD ILI9341 through
SPI...
But I get a PANIC when it is trying to do:
stm32_ltds_linit(LTDC_LAYER_L1); in stm32_ltdc.c
Does someone know this?
Ben
/* Initialize ltdc layer */
lcdinfo("Initialize ltdc layer\n");
stm32_ltdc_linit(LTDC_LAYER_L1);
#ifdef CONFIG_STM32_LTDC_L2
stm32_ltdc_linit(LTDC_LAYER_L2);
#endif
>>
Re: ILI9341 port to STM32F4
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.
--Brennan
On Wed, Jan 1, 2020, 1:38 AM Disruptive Solutions <
disruptivesolution...@gmail.com> wrote:
> 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 seems to exclude on this criteria Visual Studio Code... that
> is a shame..?
>
> I have some NX questions and keep getting hardfaults the first
> hardfault I solved ;-) It was a too large FB size.
>
> It seems strange that by not selecting CONFIG_NX_KBD it stil is trying to
> compile stuff that has relations with this config?
>
> src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl' has no
> member named 'doubleClick'
>if (m_flags.doubleClickable && hasFocus() &&
> m_widgetControl->doubleClick())
>
> And other problems. It seems I have to make changes in the NX side of Nuttx
> to get this going..?
>
> Ben
>
> Op zo 29 dec. 2019 om 19:44 schreef Disruptive Solutions <
> disruptivesolution...@gmail.com>:
>
> > It looks like its happening here... (type previous mail: graphical)
> >
> > stm32_ltdc_lclear(overlay);
> >
> > /* Set layers framebuffer */
> >
> > stm32_ltdc_lframebuffer(layer); <---??
> >
> > Op zo 29 dec. 2019 om 19:39 schreef Disruptive Solutions <
> > disruptivesolution...@gmail.com>:
> >
> >> I have most of it done for porting the grapical TFT-LCD ILI9341 through
> >> SPI...
> >>
> >> But I get a PANIC when it is trying to do:
> >> stm32_ltds_linit(LTDC_LAYER_L1); in stm32_ltdc.c
> >>
> >> Does someone know this?
> >>
> >> Ben
> >>
> >> /* Initialize ltdc layer */
> >>
> >> lcdinfo("Initialize ltdc layer\n");
> >> stm32_ltdc_linit(LTDC_LAYER_L1);
> >> #ifdef CONFIG_STM32_LTDC_L2
> >> stm32_ltdc_linit(LTDC_LAYER_L2);
> >> #endif
> >>
> >>
>
Re: ILI9341 port to STM32F4
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 seems to exclude on this criteria Visual Studio Code... that
is a shame..?
I have some NX questions and keep getting hardfaults the first
hardfault I solved ;-) It was a too large FB size.
It seems strange that by not selecting CONFIG_NX_KBD it stil is trying to
compile stuff that has relations with this config?
src/cnxwidget.cxx:691:65: error: 'class NXWidgets::CWidgetControl' has no
member named 'doubleClick'
if (m_flags.doubleClickable && hasFocus() &&
m_widgetControl->doubleClick())
And other problems. It seems I have to make changes in the NX side of Nuttx
to get this going..?
Ben
Op zo 29 dec. 2019 om 19:44 schreef Disruptive Solutions <
disruptivesolution...@gmail.com>:
> It looks like its happening here... (type previous mail: graphical)
>
> stm32_ltdc_lclear(overlay);
>
> /* Set layers framebuffer */
>
> stm32_ltdc_lframebuffer(layer); <---??
>
> Op zo 29 dec. 2019 om 19:39 schreef Disruptive Solutions <
> disruptivesolution...@gmail.com>:
>
>> I have most of it done for porting the grapical TFT-LCD ILI9341 through
>> SPI...
>>
>> But I get a PANIC when it is trying to do:
>> stm32_ltds_linit(LTDC_LAYER_L1); in stm32_ltdc.c
>>
>> Does someone know this?
>>
>> Ben
>>
>> /* Initialize ltdc layer */
>>
>> lcdinfo("Initialize ltdc layer\n");
>> stm32_ltdc_linit(LTDC_LAYER_L1);
>> #ifdef CONFIG_STM32_LTDC_L2
>> stm32_ltdc_linit(LTDC_LAYER_L2);
>> #endif
>>
>>
Re: Podling Nuttx Report Reminder - January 2020
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 questions will be asked, and worse case if you fail to report three or four times then it’s likely you’ll be removed from the incubator. Thanks, Justin
