Re: Happy birthday Ann!
They say the first person who will live to 200 is already alive! Alan C On 12-Dec-22 04:55 PM, mike wilson wrote: That's my plan as well. My grandfather lived to 90 and my father is currently 96 not out, so just maybe there is a chance. On 12/12/2022 13:26 ann sanfedele wrote: Glad to see closed captions so I could get the info without the pain in my ears :-) it's just as awful as our Happy birthday song. but I appreciate the thought and yes, I shall live to 100 xx, ann On 12/12/2022 2:15 AM, Larry Colen wrote: On Dec 11, 2022, at 9:51 PM, mike wilson wrote: Here's the song to go with it. https://youtu.be/14kApBJuEN4 So that's where the city got its name. https://wiki.lspace.org/Sto_Lat -- Larry Colen l...@red4est.com. sent from Mirkwood -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Port to M5Stamp-C3U
Hi Sebastien, On 12/9/22, Sebastien Lorquet wrote: > Hi, > > As an introduction to the RISCV, I would like to use NuttX on my M5stamp > C3U, which I can get for 8 dollars at a local store. > > https://docs.m5stack.com/en/core/stamp_c3u > This M5stamp C3U uses that ESP32-C3 that is already completely supported on NuttX. So, if your plan was to do a port, you arrived too late in the party :-D > The module does not use a usb serial chip but direct USB connection > (there is a schematic in the bottom of the page). > The USB serial on ESP32-C3 is already support on NuttX mainline too. > I wonder how it works: Is serial on USB supported by an internal > bootloader or does this require firmware support that will disappear > after I flash this board for the first time? > It doesn't require a firmware and normally will not require a host driver because it is a generic USB CDC Serial internal. Espressif create a nice thing that all MCU should have: a USB Serial / JTAG internally integrated in the chip. So, you don't need an external programmer neither an external USB/Serial. Just a USB cable and you can program the chip and get a console interface. You can get more info about it reading the "USB Serial/JTAG Controller" chapter of the ESP32-C3 TRM. BR, Alan
Re: NuttX PTP Support
Hi Markus, I don't know if there is someone already using PTP with NuttX (probably since NuttX is used by many industrial automation companies). I think the first step should be add a PTP daemon for NuttX. The ptpd could be a good candidate: https://github.com/ptpd/ptpd BR, Alan On 12/5/22, Markus Noll wrote: > Dear all, > > I'm just investigating NuttX a bit as there is definitely more and more > momentum coming about it. > I was just wondering if PTP (IEEE1588) is supported or if this is planned > for the future? Currently, it doesn't look like this, however some Eth-MAC > drivers have at least some register-definitions for the > timestamping-module. > > Thanks in advance, > Markus >
Re: NUTTX definition
Hi Roberto, You can use __NuttX__ BR, Alan On 12/5/22, Roberto Bucher wrote: > Hi > > Which is the "#ifdef" that I can use to check if I've been compiling for > NuttX (like for example #ifdef _WIN32...)? > > Thanks in advance > > Roberto > >
Re: PESO, SIMBY
Interesting shots, Larry. Still a lot of green leaves though. Looks quite tropical actually. Alan C On 05-Dec-22 05:20 AM, Larry Colen wrote: On the positive I remembered that the fall colors in my back yard have been nice enough to take out my camera. On the not so positive I didn't remember until it was already getting dark. Maybe with luck I'll remember before heading off to work in the morning and will give it another go. https://www.flickr.com/photos/ellarsee/52543865830/in/album-72177720304216569/ Full set at: https://www.flickr.com/photos/ellarsee/albums/72177720304216569 And for those that are curious, SIMBY is my tag for "Shot In My Back Yard". -- Larry Colen l...@red4est.com. sent from Mirkwood -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Code donation
Hi Fotis, I think all the software you listed are interesting and are useful to the NuttX community. As suggestion I think you could put it available on github and help people to help clean it up and then submit a PR to NuttX. BR, Alan On 12/4/22, Fotis Panagiotopoulos wrote: > Hello everyone! > > Christmas arrived a bit earlier for NuttX as I would like to donate some of > my personal code to the community! > > A bit of context. > Over the years that I am working on embedded systems, I have developed lots > of software that I use in my projects. > Some of it is quite general-purpose, or useful for other applications, and > I have found my self reusing it > quite often. In fact, there are some things that I use in practically all > firmwares that I have developed over > the last years. > > I always wanted to open-source this software so other people can benefit > from it. > But I never managed to do so. Open-sourcing needs some effort, the software > needs maintenance, documentation > and support, and most importantly in most cases a "porting layer" needs to > be developed. > Last but not least, every project needs a bit of "marketing" and > "advertising" so others can learn about > your work and use it. > > For the last couple of years I have been using NuttX a lot, and I have > ported most of the aforementioned software > to NuttX. I believe that NuttX and its community are perfect for me to > publish my code, instead of creating > a ton of small repos, of questionable usefulness and increasing my workload > considerably. > > It is very important that I can get immediate feedback from the community, > learn what people are actually > interested in (instead of investing on software that no one needs), and > provide actual and *working* > samples of the code (as NuttX already supports a ton of different boards > and arches). > > Using POSIX as the porting layer is also awesome. > > That being said, my free time is still exceptionally limited and I cannot > do this myself. > I still need the help of the community, and most importantly I need to see > interest in a piece of > software before putting any work on it. > > So, what I offer: > * I offer various codes, fully featured, production ready and tested. > * All code will be offered for free (of course) and under Apache licensing. > * I will provide support to those working on these codes, to my best > ability. > * I will contribute to testing everything integrated to NuttX, as hardware > availability allows me. > * I will do some licensing check, to ensure code is 100% original and mine, > or state the licenses of the projects I borrowed code from. > > What I ask for: > I need people that are interested in each of these codes to integrate them > into NuttX apps. > You just have to pick what it is interesting to you, contact me to provide > you with the code, > and integrate it to NuttX. You will need to: > * Add the code into the NuttX apps repo, and ensure Kconfig and the build > system use the code properly (should be trivial). > * Adapt the file format and the coding style to the NuttX one (this may > need some work, but it can also be automated). > * Provide an example app, something that someone can run to use or demo the > new code. > * Test and verify the example app on actual hardware (I may be able to > cross-check it on my hardware too). > > The code that I offer (for the moment): > > > *** Lua v5.2.4 *** > I know that there is already a Lua app for NuttX. > But for anyone using it, it may be beneficial to use my work. > > First and foremost, I have ported the eLua LTR patch to Lua 5.2. This patch > dramatically reduces the memory usage of Lua. > In fact, I found out that it is crucial to have this patch enabled for any > actual real-life usage of Lua on any "normal" MCU. > > I have created a Kconfig for all Lua configurations, so it can integrate > with NuttX better. > > I have also made some other minor changes to the code that might be > interesting for you. > For example there is a simplistic sandboxing option. > > > *** MQTT Broker *** > Yes, a full-blown, spec-compliant MQTT Broker! > To my knowledge there is no other open-source and portable MQTT broker for > embedded systems. > > It follows the MQTT v3.1.1 specification as closely as possible. I think > there is only one violation, needed due to its embedded nature, > but in all practical cases you may consider it fully compliant. > > It has been tested with dozens of devices, and it performs greatly. > There are a couple of things that may need to be improved, but are trivial, > and will not affect the normal use of the software. > > I know that such a broker may not be your best option for a proper and > large installation of IoT devices, but it is exceptionally useful > for at least the following cases: > * You have only a few devices, isolated (no internet), that you need to > connect, and you want to avoid the cost (and maintenance) of a proper > broker (e.g. Raspberry Pi).
Re: Semi OT: History amplified
Rick In Mafikeng, I would say it was used to crush stone for building purposes (concrete). The SA Phosphate Co. was formed in 1953 to investigate the beneficiation of the mineral Pyroxenite (essentially Calcium Phosphate - abundant in the Phalaborwa area) to be used for the manufacture of Superphosphates & acquired the crusher for use in a small pilot plant. The position of the asymmetric driven cone in the middle of the crusher would have been adjusted to produce the required fineness & any screened oversize would have been recycled. The tests were successful and the SA Phosphate Co. became Foskor which has built a huge plant over the years, today producing about 3m tons of Pyroxenite Concentrate (containing about 36.5% P2O5) per annum. The antique crusher was "rescued" from the veld and re-located outside Foskor H/O (diagonally opposite the Police Station!) about 1985 by a former manager, Jan Scholtemeyer, who had a great interest in the history of Phalaborwa. The huge crushers in use today still work on exactly the same principle. Alan C On 01-Dec-22 05:15 AM, Rick Womer wrote: Alan, was that used for crushing coal, crushing ore, or something else? Rick On Nov 28, 2022, at 10:20 AM, Alan C wrote: You may recall this shot I posted in the October PUG? https://www.flickr.com/photos/wisselstroom/52528837587/ Well, I was looking for more details & found this copy of the 1900 NY Engineering & Mining Journal with a drawing of the exact crusher on p 17. Scroll R for the other. https://www.flickr.com/photos/wisselstroom/52529290826/ Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Semi OT: History amplified
You may recall this shot I posted in the October PUG? https://www.flickr.com/photos/wisselstroom/52528837587/ Well, I was looking for more details & found this copy of the 1900 NY Engineering & Mining Journal with a drawing of the exact crusher on p 17. Scroll R for the other. https://www.flickr.com/photos/wisselstroom/52529290826/ Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Article: Preparing a Pull Request for NuttX
Kudos Lup! Maybe we could mix it with our current documentation to create a better doc. BR, Alan On 11/28/22, Lee, Lup Yuen wrote: > This article explains how I prepared my Pull Requests for NuttX. I hope > this will be helpful for folks contributing to NuttX for the very first > time :-) > > https://lupyuen.github.io/articles/pr > > Lup >
Re: Apologies
This is a CI issue. We just need to restart it manually. Maybe we could add some tests to retry automatically when errors like this happen. On 11/26/22, TimH wrote: > Thanks for the support - another 2 PRs submitted now. > > But one failed tests with multiple instances of: > > " Error: Error response from daemon: login attempt to https://ghcr.io/v2/ > failed with status: 503 Service Unavailable" > > Do I need to do anything to get the tests to rerun and hopefully pass? > >>-Original Message- >>From: Tim Hardisty >>Sent: 25 November 2022 14:46 >>To: dev@nuttx.apache.org >>Subject: Apologies >> >>Some may have seen I've been attempting multiple times to submit PRs for 2 >>issues (SAMA5D2 related) and have closed/cancelled/retried numerous >>times. >> >>Bottom line - I am struggling with the whole rebase/squash/merge >> cycle...as >>I'm a complete numpty. Code I can mostly do, but this is the first time > working >>with a public repo not just my with own private code where I can do > whatever >>I want ;) >> >>I will fully "get it", eventually, but have now, at long last, had my >> first > actual >>code PR accepted and merged. Thank you for your understanding and >>patience! >> >>Regards, >> >>TimJTi >>--- >>PS I believe any email sent to the mail reflector that has been DKIM >> signed > will >>end up in recipients spam folder...hence sending this from a non-DKIM > signed >>email account to see what happens. > >
Re: PinePhone added to NuttX Mainline
Congratulations Lup, great achievement! BR, Alan On Friday, November 25, 2022, Lee, Lup Yuen wrote: > Pine64 PinePhone is now supported by NuttX Mainline! If you have a > PinePhone (and PinePhone Serial Debug Cable), you're welcome to try NuttX > on PinePhone... > > https://github.com/apache/nuttx/blob/master/Documentation/platforms/arm/ > a64/boards/pinephone/index.rst > > Please lemme know if you see any issues. Thanks! :-) > > Let's make NuttX the fun new way to teach the internals of Smartphone > Operating Systems! > > Lup >
Re: Apologies
Hi Tim, Don't worry, after you get used to it things become easier. If you have some ideas to improve the documentation to make it easier to the next "Tim", please don't hesitate to submit a PR :-D BR, Alan On Friday, November 25, 2022, TimH wrote: > Some may have seen I've been attempting multiple times to submit PRs for 2 > issues (SAMA5D2 related) and have closed/cancelled/retried numerous times. > > Bottom line - I am struggling with the whole rebase/squash/merge cycle.as > I'm a complete numpty. Code I can (mostly!) do, but this is the first time > working with a public repo rather than just my own private code, where I > can > do whatever I want ;) > > I will fully "get it", eventually, but have now, at long last, had my first > actual code PR accepted and merged. Thank you for your understanding and > patience! > > Regards, > > Tim > >
Re: Erwitt-style sequence
Yes. Your shots are indeed reminiscent of Erwitt's style - clever shots telling a story. A lost art? Street photography is probably about the closest one sees today. Alan C Did the link work when you’d removed the spaces? On 25 Nov 2022, at 13:05, ann sanfedele wrote: Made me look :-) ann On 11/25/2022 6:12 AM, Bob Pdml wrote: Hoping the PDML will accept this link to a short sequence I shot last week. Please remove spaces from the link. I put them there because the PDML always rejects posts I send which contain a link. No idea why. https :// adobe .ly /3ALD4Nb MX, M 120mm f2.8. Y1 filter. Ilford FP4+ -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- ann sanfedele photography https://annsan.smugmug.com https://www.cafepress.com/+ann-sanfedele+gifts https://www.lulu.com/spotlight/annsan https://www.createphotocalendars.com/Shop/annsanfedelecalendarsandbooks -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PESO: Waterless
Indubitably! Alan C On 24-Nov-22 06:28 PM, Ralf R Radermacher wrote: Am 24.11.22 um 17:14 schrieb Alan C: Easy marketing. You really need to open the encapsulation & plant in a pot them if you want them to survive. We have some which have been flowering annually for years. Could it be that the wax is just meant as some kind of transport packing? Ralf -- Ralf R. Radermacher - Köln/Cologne, Germany Blog : http://the-real-fotoralf.blogspot.com Audio : http://aporee.org/maps/projects/fotoralf Fotos : https://www.fotocommunity.de/user_photos/770012 -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PESO: Waterless
Easy marketing. You really need to open the encapsulation & plant in a pot them if you want them to survive. We have some which have been flowering annually for years. Alan C On 24-Nov-22 04:53 PM, Ralf R Radermacher wrote: Am 24.11.22 um 15:35 schrieb Daniel J. Matyola: My Thanksgiving guest gave me an unusual plant; a "waterless" Amaryllis. The bulb is coated in a waxy substance, and it grows and blooms without the need for water or fertilizer. It is also quite attractive: They're selling them all over the place over here, as well. Remains to be seen what will happen once it has consumed the water/nutrients in the bulb. Not for us, anyway, because they're highly poisonous for cats. Ralf -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: nsh_main cant running and print no output
Hi Mr. Wang,
Did you modify the driver to support both interrupts?
Also, do you have JTAG (OpenOCD) + GDB support to HDSC HC32 chips?
Using JTAG+GDB will be easier to track the root cause of the issue.
Seems like you are mixing the HDSC SDK code with NuttX code, it is
better to start a clean port to this new chip.
What board are you using? I didn't find a hc32f4a0 board at Aliexpress.
BR,
Alan
On 11/24/22, wanglingyu wrote:
> I attached more detail for the problem.
> hc32f4a0 is similar with stm32f407, but the serial irq is different with
> stm32f407,
> it includes rx and tx and error irq , but stm32f4 includes one irq including
> rx and tx.
> I uses UART6 as the console device and merge the relative register operation
> in hc32 sdk as serial output, the codes as below:
> void arm_lowputc(char ch)
> {
> while(Set != USART_GetStatus(DBG_UNIT, USART_FLAG_TXE));
> USART_SendData(DBG_UNIT, ch);
> }
> Using the function, I can observe the output by UART6. and like _info，syslog
> also can print something.
> For porting printf, I calls uart_register to register /dev/console with
> UART6,
> but "printf" can't output anything, any log can't appear. and nsh_main also
> seems not to be running.
> I make a test case in nuttx main under nx_start.
> fd = open(/dev/console, "0x6")
> write(fd, "test", 4)
> it is ok, "test" can print.
> but when I use printf, the system is suspend.
> By tracing the printf, I think the final operation of printf is operating
> /dev/console. so I don't know why
> the problem happend.
>
>
>
> attached .config and map file. thanks!!!
>
>
>
>
>
>
>
>
>
>
> At 2022-11-24 15:04:00, "wanglingyu" wrote:
>
> Hi,
>
>
> I have a problem about nuttx during moving a new chip with hc32.
> the board can output with lowputc, system can run, and gpio control is ok,
> but printf in libc can't output anything, and at same time, nsh_main also
> not running,
> it makes shell not being used. the codes is compiled and linked.
> Please give some advices for the problem. Thanks!!!
>
>
> Br,
> Wang Lingyu
Help to spread the news about NuttX
Dear NuttXers, We are asked some friends sites to post about the fact that NuttX became a Top Level Apache project. Today many sites expect some payment to publish the news. We want to thank CNX-Software for publishing about EsPiFF board and include the fact in the text: https://www.cnx-software.com/2022/11/23/espiff-esp32-wrover-rp2040-mcu-raspberry-pi-4/ Also Sony: https://developer.sony.com/develop/nuttx-rtos-on-spresense/news-and-articles So if you have some friend on some media site please ask them to publish about it too. It will help as to reach more people. BR, Alan
Re: New names of repositories
Ok! +1 On 11/22/22, Nathan Hartman wrote: > After hearing back from Infra about the repository naming convention, > all the recent feedback has been to stay with the default and just > remove "incubator-" from our repo names, giving: > > https://github.com/apache/nuttx > https://github.com/apache/nuttx-apps > > Shall I go ahead and open the Jira ticket to do that? > > Cheers, > Nathan >
Re: PESOs (5) - Minneapolis Foshay Tower
Impressive images, Rick. Mind you, I'm not particularly partial to all that glass. Foshay must have made an exceedingly huge fortune to be able to finance an edifice like that. The mind boggles. Alan C On 22-Nov-22 04:16 AM, Rick Womer wrote: Wilbur Foshay was a 1920s businessman who made his fortune buying and selling utility companies. He celebrated himself with the construction of this tower in 1929. It is the size and shape of the Washington Monument. Near the top Foshay had his name is chiseled into each side in 10-foot letters. He left Minneapolis for Salida, Colorado when the stock market crashed in 1929. Alas his gains were ill-gotten, as he had operated a pyramid scheme with his companies. He was tried in 1932, convicted, and sentenced to 15 years in Leavenworth. He only served three years, though, because Franklin Roosevelt commuted 10 years of his sentence, and he had two more years deducted for good behavior. He then settled in Colorado, where he continued a career as a shameless promoter until his death in 1957. His tower was the tallest building in Minneapolis until it was surpassed 1974. It now houses a posh hotel. $10 gets one a ticket to an observation deck, which disappoints my having only small square portholes for viewing. Here are views in each direction from the tower. I liked the reflections off the irregular glass tower across the street in the third photo. The last photo looks east—it’s pretty flat out there. https://rickwomer.smugmug.com/Oct2022/2022-10/Minneapolis-10-22/Foshay-Tower-View/ <https://rickwomer.smugmug.com/Oct2022/2022-10/Minneapolis-10-22/Foshay-Tower-View/> Comments always appreciated! Rick -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: New names of repositories
Hi Zou, You don't feel sorry, all suggestions are welcome. Since you aren't aware of that previous discussion it was a honest mistake! Initally NuttX didn't have an apps/ directory, it became part of NuttX when the support to build-in applications was included and in fact the initial apps/ repository was integrated inside the same repository (in Subversion) but as Mr. Greg explained apps/ is not necessary to have NuttX kernel, you can create you own application and just pass its entry point to be used by the kernel to start up. BR, Alan On 11/19/22, fft wrote: > sorry for mytentative idea! > > > BR, > > > > ---Original--- > From: "Gregory Nutt" Date: Sat, Nov 19, 2022 08:26 AM > To: "dev" Subject: Re: New names of repositories > > > Isn't it possible to merge the nuttx and apps into only one > repository？e.g: >|-rtos > |-apps > > We discussed this option a couple of years ago and decided against it. > I > was VERY strongly opposed to the idea then and I still am. > > - apps is NOT part of NuttX. It is an achitecturally unrelated, mish > mash > or useful applications for NuttX, but it is not NuttX. > - I consists of mostly 3rd party code and should not contaminate the clean > modularity of the OS. > > If we want to consider this kind of code change than I would insist on a > vote and I most certainly would vote -1. I don't care about care > about > hyphens or other cosmetics but I would not support any such corruption of > the modularity of the RTOS. > > This must never happen.
Re: PESO Horse
Perhaps the climate activists will paint it? Alan C On 19-Nov-22 09:30 AM, Toine wrote: More PESO's? Here is one: https://repiuk.nl/new/#pid=DSCN4630-DeNoiseAI.jpg No Pentax and no horse -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Halooooo.......?
PENTAX PHOTOGRAPHERS SOUTH AFRICA IS just the same. Too much going on around the world at the moment? Alan C On 19-Nov-22 01:33 AM, Rick Womer wrote: Where is everyone? Only sixteen posts in the past week, by my count. Only four of us have posted photos, and they’ve gotten very few comments. How about some pix and commentary, friends? Rick -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Downtown Minneapolis - Loring Park
No doubt you like this: https://www.google.co.za/search?tbm=vid=ALiCzsZh2B3Z5XRJGiYFUi3ETWlHjvDAIA:1668842449138=Listen+to+Chris+de+Burgh+The+lady+in+Red=X=2ahUKEwjBtPfK2rn7AhWUQUEAHZ87DjMQ1QJ6BAgUEAE=1366=635=1#fpstate=ive=cid:708571d4,vid:UL5lepmivW8 Alan C On 19-Nov-22 03:18 AM, Rick Womer wrote: Thanks, Ann! I regularly stalk the lady in the red coat, as she is my spouse. She often wears a red coat or jacket, but that’s a trivial detail overall. Rick On Fri, Nov 18, 2022 at 18:54 ann sanfedele wrote: Rick .. Interesting how few other people are there... I like the geometry and colors especially the 3rd and 4th photos. were you stalking the lady in the red coat? ann On 11/16/2022 9:17 PM, Rick Womer wrote: My wife had a conference at the Hyatt in Minneapolis, and I went along for fun. A short walk from the hotel is Loring Park, which is very pleasant and well-maintained. https://rickwomer.smugmug.com/Oct2022/2022-10/Minneapolis-10-22/Downtown-Minneapolis/ < https://rickwomer.smugmug.com/Oct2022/2022-10/Minneapolis-10-22/Downtown-Minneapolis/ (K-5, DA 17-70) Comments always appreciated. Rick -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- ann sanfedele photography https://annsan.smugmug.com https://www.cafepress.com/+ann-sanfedele+gifts https://www.lulu.com/spotlight/annsan https://www.createphotocalendars.com/Shop/annsanfedelecalendarsandbooks -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: New names of repositories
I like the second option: 2) nuttx_rtos and nuttx_apps It makes clear that it is a RTOS :-) BR, Alan On 11/17/22, Nathan Hartman wrote: > Hi all, > > As mentioned in the other thread, the repos need to be renamed to > remove "incubating". > > In the discussion from a few months ago [1] several reasons were given > why not to use hyphens in the names (they confuse some tools and > underscores are safer). > > Two possibilities for repo names were given: > > 1) nuttx and nuttx_apps > > or > > 2) nuttx_rtos and nuttx_apps > > Which do we want? > > Cheers, > Nathan > > [1] https://lists.apache.org/thread/8fn2m2v8qd3sl9r8jg4bs2f9xq7mwg85 >
Re: Post Graduation TO DO List
Congratulations to everybody who made it possible. I was worried about the project redirection after renaming, but it seems like Github will do it automatically for us: https://docs.github.com/en/repositories/creating-and-managing-repositories/renaming-a-repository So, the transition will be smooth! BR, Alan On 11/17/22, Nathan Hartman wrote: > Hi All, > > NuttX graduated from the Incubator! Kudos to the whole NuttX > community. Here's to a great continuation of this journey for many > years to come! > > Some post-graduation TODOs -- Help will be appreciated!! > > * Change NuttX and NuttX apps repo names > - Finalize new names > - Ask Infra to make the change > - Update all links inside our repos > - Announce the git incantations to update forks/clones > > * Remove DISCLAIMER from both repos > - See PR #7613 at NuttX repo > - See PR #1422 at NuttX apps repo > > * Update website: > - Change from Incubator to Top Level Project > - Update links to repos > > Cheers, > Nathan >
Re: Article: NuttX RTOS for PinePhone: Render Graphics in Zig
Very nice Lup! Another create article! On 11/15/22, Lee, Lup Yuen wrote: > Inside Pine64's PinePhone (Arm64) is the Allwinner A64 Display Engine that > renders graphics on the LCD Display. > > This article explains how we're building a NuttX Driver for the A64 Display > Engine, using the Zig Programming Language... > > https://lupyuen.github.io/articles/de2 > > Lup >
Re: OLED SSD1306 display issue
Hi Robert, I discovered that the issue is in the ESP32's I2C driver. First I tested in the BluePill (stm32f103-minimum) and the LCD worked fine. Editing the esp32_i2c.c and changing the FIFO from 255: #define I2C_FIFO_SIZE (32) fixed the error sendblk timeout. But the LCD image is not good as in STM32 board. We need to do more some investigation to know why it is happening. BR, Alan On 11/9/22, Robert Alexa wrote: > Hi Alan, > > I've modified my defconfig file so that it looks almost exactly the same as > the one you mentioned. I'm attaching it to this email so that you can have > a look at it. > > Regarding the I2C address, I've used i2ctool and confirmed that the OLED > display is discoverable and reachable at 0x3c. This is also consistent with > the behaviour I've experienced - the ssd1306_sendbyte commands do not fail, > it's only the block transfers that cause the issue. > > Thank you, > Robert > > On Wed, 9 Nov 2022 at 14:33, Alan C. Assis wrote: > >> Hi Robert, >> >> I suggest you to verify if all needed options for SSD1306 are met, you >> can compare with other boards, i.e.: >> >> arm/rp2040/raspberrypi-pico-w/configs/ssd1306/defconfig >> >> Also you can enable the i2ctool (CONFIG_SYSTEM_I2CTOOL) to scan your >> I2C bus to confirm the I2C OLED address. >> >> BR, >> >> Alan >> >> On 11/9/22, Robert Alexa wrote: >> > Hi, >> > >> > I'm trying to set up an OLED SSD1306 128x32 display with an >> > ESP32-Wrover >> > board. The display module is connected through I2C and has only 4 pins >> > exposed: SCL, SDA, VCC, GND. >> > >> > My custom config file starts from an esp32-wrover-kit:nsh to which I >> added: >> > CONFIG_LCD=y >> > CONFIG_LCD_DEV=y >> > CONFIG_LCD_SSD1306_CUSTOM=y >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_XRES=128 >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_YRES=32 >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_XOFFSET=0 >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_PAGES=4 >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_CMNPAD=2 >> > CONFIG_LCD_SSD1306=y >> > CONFIG_SSD1306_NUMDEVS=1 >> > >> > However, I'm encountering an issue at boot time regarding the I2C block >> > transfer. >> > ssd1306_setpower: power: 1 [0] >> > ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -116 >> > board_lcd_initialize: Bound I2C0 to OLED 0 >> > ssd1306_setpower: power: 1 [0] >> > ssd1306_getplaneinfo: planeno: 0 bpp: 1 >> > >> > Interesting enough, it seems like the single transfer >> > (ssd1306_sendbyte) >> is >> > working fine, the problem is only with the block transfer. Do you have >> any >> > ideas what might cause this? >> > >> > Regards, >> > Robert >> > >> >
OT: Interesting Story
Very early this morning my next-door neighbour disturbed two juvenile Leopards sleeping on his front stoep. They quickly slunk off in the half darkness. I can't say I am surprised because we have seen Leopard spoor at the Church & there have been other sightings of Leopards in town. No attacks yet. Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PWM fast stop operation
Hi Petro, Maybe instead of creating an override you can create a capability like exists for SDIO on NuttX. It could be used to control features/characteristics unique for some PWM controllers. Buf of course it will need some override/sync flag because some applications will prefer to wait up to the next cycle. BR, Alan On 11/12/22, Petro Karashchenko wrote: > Hello David, > > Thanks for your reply. I fully understand that. In my case I have the half > bridge schema of four pins and PWM frequency is very low. In case I need to > do immediate stop I need to stop pulse generation and short pin to the > ground. It is more because the overall half bridge solution is controlled > by 2 pins with PWM and other 2 pins are controlled as GPIOs. There where > the sync problems come in place. > > Best regards, > Petro > > On Sat, Nov 12, 2022, 9:34 AM David Sidrane > wrote: > >> Hi Petro, >> >> On the STM32 there are shadow registers that buffer the updated data to >> ensure that outputs are updated synchronously with the end of the period. >> There is a bit that can be set to force the update to the shadowed >> registers >> to be immediate, which will change the count of the current period in >> that >> period. This can be dangerous; in that it could extend a pulse and create >> an >> undesired position or speed. In the case of going to 0, this could create >> a >> runt pulse and also create an undesired position or a slow speed (not so >> bad), Because the update is asynchronous the pulse with the output, it is >> not deterministic. So synchronous updates are a good thing most times. >> >> David >> >> >> -Original Message- >> From: Petro Karashchenko >> Sent: Friday, November 11, 2022 6:50 PM >> To: dev@nuttx.apache.org >> Subject: PWM fast stop operation >> >> Hello team, >> >> Recently I had a project where I had to control a motor using PWM. In >> general things worked pretty well, but I've met an issue when I need to >> stop >> PWM as soon as possible. My custom board is based on SAMv7 and uses the >> standard NuttX PWM driver. The issue with the SAMv7 PWM peripheral is >> that >> when a PWM stop is issued the PWM generation is not stopped immediately, >> but >> waits at the end of the current cycle. I'm not sure if that is unique to >> SAMv7, so maybe you can give feedback about the other platforms. >> Initially >> I >> tried to replace stop by keeping PWM running and updating config to have >> 0% >> duty cycle, but that still waits till the end of the current cycle to >> apply. >> The SAMv7 PWM has a signal override capabilities, so I used that instead >> of >> stopping the PWM. I've extended the "struct pwm_info_s" structure and >> included an override field there, but feel that it might not be the best >> approach. >> >> I would appreciate your advices on what is the best way to integrate >> output >> override feature into existing PWM driver. >> >> Best regards, >> Petro >> >
Re: What is this and why is it so special
I use to have one of those. Yellow colour caused by ThO2 so not all that dangerous. https://www.flickr.com/photos/wisselstroom/52491228768/ Alan C On 10-Nov-22 03:37 PM, Henk Terhell wrote: Perhaps somebody eagerly wants a radioactive lens, noting the yellowish cast? Henk Op do 10 nov. 2022 om 08:50 schreef Bob Pdml : 1958/59 Pentax S with probably its original Takumar 55/2.2 lens. There’s a write-up and a couple of reviews on Pentaxforums. On 9 Nov 2022, at 17:50, coll...@brendemuehl.net wrote: https://shopgoodwill.com/item/154526031 I’m guessing the collectors will know. -- -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: OLED SSD1306 display issue
I attached, but our infra email server remove it
I renamed it to .txt, let's try again.
BR,
Alan
On 11/10/22, Robert Alexa wrote:
> Hi Alan,
>
> I think you forgot to attach the config file or am I missing something?
>
> On Thu, 10 Nov 2022 at 15:07, Alan C. Assis wrote:
>
>> Hi Robert,
>>
>> I confirmed your issue:
>>
>> nsh> nxhello
>> nxmu_start: Starting server task
>> ssd1306_setpower: power: 1 [0]
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> board_lcd_initialize: Bound I2C0 to OLED 0
>> ssd1306_setpower: power: 1 [0]
>> ssd1306_setpower: power: 1 [1]
>> ssd1306_getvideoinfo: fmt: 0 xres: 128 yres: 32 nplanes: 1
>> ssd1306_getplaneinfo: planeno: 0 bpp: 1
>> nx_runinstance: Received opcode=8 nbytes=8
>> nx_runinstance: Received opcode=3 nbytes=20
>> nx_runinstance: Re-draw background rect={(0,0),(127,31)}
>> ssd1306_putrun: row: 0 col: 0 npixels: 128
>> nx_eventhandler: Received msgid=1
>> nxhello_main: NX handle=0x3ffaff40
>> nxhello_main: Set background color=0
>> nxhello_listener: Connected
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> ssd1306_putrun: row: 1 col: 0 npixels: 128
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> ssd1306_putrun: row: 2 col: 0 npixels: 128
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> ssd1306_putrun: row: 3 col: 0 npixels: 128
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> ssd1306_putrun: row: 4 col: 0 npixels: 128
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> ssd1306_putrun: row: 5 col: 0 npixels: 128
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>> ssd1306_putrun: row: 6 col: 0 npixels: 128
>> ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
>>
>> Probably someone broke something on ESP32 I2C.
>>
>> I suggest you to try on Raspberry Pi Pico to confirm it still working
>> there, if everything works there then it will confirm that the issue
>> is only on ESP32.
>>
>> I'm sending my config for reference.
>>
>> BR,
>>
>> Alan
>>
>> On 11/9/22, Robert Alexa wrote:
>> > Hi Alan,
>> >
>> > I've modified my defconfig file so that it looks almost exactly the
>> > same
>> as
>> > the one you mentioned. I'm attaching it to this email so that you can
>> have
>> > a look at it.
>> >
>> > Regarding the I2C address, I've used i2ctool and confirmed that the
>> > OLED
>> > display is discoverable and reachable at 0x3c. This is also consistent
>> with
>> > the behaviour I've experienced - the ssd1306_sendbyte commands do not
>> fail,
>> > it's only the block transfers that cause the issue.
>> >
>> > Thank you,
>> > Robert
>> >
>> > On Wed, 9 Nov 2022 at 14:33, Alan C. Assis wrote:
>> >
>> >> Hi Robert,
>> >>
>> >> I suggest you to verify if all needed options for SSD1306 are met, you
>> >> can compare with other boards, i.e.:
>> >>
>> >> arm/rp2040/raspberrypi-pico-w/configs/ssd1306/defconfig
>> >>
>> >> Also you can enable the i2ctool (CONFIG_SYSTEM_I2CTOOL) to scan your
>> >> I2C bus to confirm the I2C OLED address.
>> >>
>> >> BR,
>> >>
>> >> Alan
>> >>
>> >> On 11/9/22, Robert Alexa wrote:
>> >> > Hi,
>> >> >
>> >> > I'm trying to set up an OLED SSD1306 128x32 display with an
>> >> > ESP32-Wrover
>> >> > board. The display module is connected through I2C and has only 4
>> >> > pins
>> >> > exposed: SCL, SDA, VCC, GND.
>> >> >
>> >> > My custom config file starts from an esp32-wrover-kit:nsh to which I
>> >> added:
>> >> > CONFIG_LCD=y
>> >> > CONFIG_LCD_DEV=y
>> >> > CONFIG_LCD_SSD1306_CUSTOM=y
>> >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_XRES=128
>> >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_YRES=32
>> >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_XOFFSET=0
>> >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_PAGES=4
>> >> > CONFIG_LCD_SSD1306_CUSTOM_DEV_CMNPAD=2
>> >> > CONFIG_LCD_SSD1306=y
>> >> > CONFIG_SSD1306_NUMDEVS=1
>> >> >
>> >> > However, I'm encountering an issue at boot time regarding the I2C
>> block
>> >> > transfer.
>> >> > ssd1306_setpower: power: 1 [0]
>> >> > ssd1306_sendblk: ERR
Re: OLED SSD1306 display issue
Hi Robert,
I confirmed your issue:
nsh> nxhello
nxmu_start: Starting server task
ssd1306_setpower: power: 1 [0]
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
board_lcd_initialize: Bound I2C0 to OLED 0
ssd1306_setpower: power: 1 [0]
ssd1306_setpower: power: 1 [1]
ssd1306_getvideoinfo: fmt: 0 xres: 128 yres: 32 nplanes: 1
ssd1306_getplaneinfo: planeno: 0 bpp: 1
nx_runinstance: Received opcode=8 nbytes=8
nx_runinstance: Received opcode=3 nbytes=20
nx_runinstance: Re-draw background rect={(0,0),(127,31)}
ssd1306_putrun: row: 0 col: 0 npixels: 128
nx_eventhandler: Received msgid=1
nxhello_main: NX handle=0x3ffaff40
nxhello_main: Set background color=0
nxhello_listener: Connected
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
ssd1306_putrun: row: 1 col: 0 npixels: 128
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
ssd1306_putrun: row: 2 col: 0 npixels: 128
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
ssd1306_putrun: row: 3 col: 0 npixels: 128
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
ssd1306_putrun: row: 4 col: 0 npixels: 128
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
ssd1306_putrun: row: 5 col: 0 npixels: 128
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
ssd1306_putrun: row: 6 col: 0 npixels: 128
ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -110
Probably someone broke something on ESP32 I2C.
I suggest you to try on Raspberry Pi Pico to confirm it still working
there, if everything works there then it will confirm that the issue
is only on ESP32.
I'm sending my config for reference.
BR,
Alan
On 11/9/22, Robert Alexa wrote:
> Hi Alan,
>
> I've modified my defconfig file so that it looks almost exactly the same as
> the one you mentioned. I'm attaching it to this email so that you can have
> a look at it.
>
> Regarding the I2C address, I've used i2ctool and confirmed that the OLED
> display is discoverable and reachable at 0x3c. This is also consistent with
> the behaviour I've experienced - the ssd1306_sendbyte commands do not fail,
> it's only the block transfers that cause the issue.
>
> Thank you,
> Robert
>
> On Wed, 9 Nov 2022 at 14:33, Alan C. Assis wrote:
>
>> Hi Robert,
>>
>> I suggest you to verify if all needed options for SSD1306 are met, you
>> can compare with other boards, i.e.:
>>
>> arm/rp2040/raspberrypi-pico-w/configs/ssd1306/defconfig
>>
>> Also you can enable the i2ctool (CONFIG_SYSTEM_I2CTOOL) to scan your
>> I2C bus to confirm the I2C OLED address.
>>
>> BR,
>>
>> Alan
>>
>> On 11/9/22, Robert Alexa wrote:
>> > Hi,
>> >
>> > I'm trying to set up an OLED SSD1306 128x32 display with an
>> > ESP32-Wrover
>> > board. The display module is connected through I2C and has only 4 pins
>> > exposed: SCL, SDA, VCC, GND.
>> >
>> > My custom config file starts from an esp32-wrover-kit:nsh to which I
>> added:
>> > CONFIG_LCD=y
>> > CONFIG_LCD_DEV=y
>> > CONFIG_LCD_SSD1306_CUSTOM=y
>> > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_XRES=128
>> > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_YRES=32
>> > CONFIG_LCD_SSD1306_CUSTOM_DEV_XOFFSET=0
>> > CONFIG_LCD_SSD1306_CUSTOM_DEV_PAGES=4
>> > CONFIG_LCD_SSD1306_CUSTOM_DEV_CMNPAD=2
>> > CONFIG_LCD_SSD1306=y
>> > CONFIG_SSD1306_NUMDEVS=1
>> >
>> > However, I'm encountering an issue at boot time regarding the I2C block
>> > transfer.
>> > ssd1306_setpower: power: 1 [0]
>> > ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -116
>> > board_lcd_initialize: Bound I2C0 to OLED 0
>> > ssd1306_setpower: power: 1 [0]
>> > ssd1306_getplaneinfo: planeno: 0 bpp: 1
>> >
>> > Interesting enough, it seems like the single transfer
>> > (ssd1306_sendbyte)
>> is
>> > working fine, the problem is only with the block transfer. Do you have
>> any
>> > ideas what might cause this?
>> >
>> > Regards,
>> > Robert
>> >
>>
>
Re: OLED SSD1306 display issue
Hi Robert, I suggest you to verify if all needed options for SSD1306 are met, you can compare with other boards, i.e.: arm/rp2040/raspberrypi-pico-w/configs/ssd1306/defconfig Also you can enable the i2ctool (CONFIG_SYSTEM_I2CTOOL) to scan your I2C bus to confirm the I2C OLED address. BR, Alan On 11/9/22, Robert Alexa wrote: > Hi, > > I'm trying to set up an OLED SSD1306 128x32 display with an ESP32-Wrover > board. The display module is connected through I2C and has only 4 pins > exposed: SCL, SDA, VCC, GND. > > My custom config file starts from an esp32-wrover-kit:nsh to which I added: > CONFIG_LCD=y > CONFIG_LCD_DEV=y > CONFIG_LCD_SSD1306_CUSTOM=y > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_XRES=128 > CONFIG_LCD_SSD1306_CUSTOM_DEV_NATIVE_YRES=32 > CONFIG_LCD_SSD1306_CUSTOM_DEV_XOFFSET=0 > CONFIG_LCD_SSD1306_CUSTOM_DEV_PAGES=4 > CONFIG_LCD_SSD1306_CUSTOM_DEV_CMNPAD=2 > CONFIG_LCD_SSD1306=y > CONFIG_SSD1306_NUMDEVS=1 > > However, I'm encountering an issue at boot time regarding the I2C block > transfer. > ssd1306_setpower: power: 1 [0] > ssd1306_sendblk: ERROR: I2C_TRANSFER failed: -116 > board_lcd_initialize: Bound I2C0 to OLED 0 > ssd1306_setpower: power: 1 [0] > ssd1306_getplaneinfo: planeno: 0 bpp: 1 > > Interesting enough, it seems like the single transfer (ssd1306_sendbyte) is > working fine, the problem is only with the block transfer. Do you have any > ideas what might cause this? > > Regards, > Robert >
Re: PANO: Green Canyon but away
Thanks, Ann. Alan C From: *ann sanfedele* Date: Tue, Nov 8, 2022 at 3:51 AM Subject: Re: PANO: Green Canyon but away To: I like it a lot , too Alan - very serene looking ann -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
PANO: Green Canyon but away
Our time at the Crystal Springs Mountain Resort has been somewhat compromised by the weather. Almighty thunderstorms overnight. Nevertheless, we have still enjoyed our Getaway - the Cricket T20 World Cup on TV has proved a welcome distraction. Anyway, back to photography. I had hoped to take a few Astro's away from city lights but the clouds put paid to that. Sadly, the roads in the Game Park are too slushy for Sedans. Even the 4x4 guys seem to be reluctant! The sun burst out this morning so I took this 11 frame portrait Pano from the verandah of our chalet. The Blyde River in this Green Canyon winds it's through the Eastern Escarpment eventually dropping down to the Lowveld & joining the mighty Olifants River some 50km away. https://www.flickr.com/photos/wisselstroom/52480330366/ K5 & HD 55-300 @ 55mm, f8, 1/500sec, ISO 250. Here is a link to an old post so you can see what the Canyon looks like at the other end: https://www.flickr.com/photos/wisselstroom/39110586230/ And now it's off to Pilgrim's Rest for lunch. Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: ARM -m startup does not check for idle thread stack space
On 11/4/22, Nathan Hartman wrote: > On Fri, Nov 4, 2022 at 4:32 PM Alan C. Assis wrote: > >> Hi Nathan, >> >> Do you have some other idea? >> >> "Just add another symbol" is not a good idea. >> >> We are going to pass Linux kernel Kconfig is one day or two :-) >> >> I think we need to simplify our Kconfig, not to make each more complex >> every single day. > > > > Could make it automatic? If linker script exists in board subdirectory we > use it. If not, we use default linker script of that arch. > > This means the linker scripts have to be named consistently, since the > build system will look for the script by name. > Yes, this could work. BR, Alan
Re: ARM -m startup does not check for idle thread stack space
Hi Nathan, Do you have some other idea? "Just add another symbol" is not a good idea. We are going to pass Linux kernel Kconfig is one day or two :-) I think we need to simplify our Kconfig, not to make each more complex every single day. BR, Alan On 11/4/22, Nathan Hartman wrote: > On Fri, Nov 4, 2022 at 4:06 PM Nathan Hartman > wrote: > >> On Fri, Nov 4, 2022 at 2:12 PM Carlos Sanchez >> wrote: >> >>> It is exactly the same issue, I should have checked there, apologies for >>> duplicating. Shall we continue the discussion there? >>> >>> In any case, I do not think it is such an uncommon scenario... We have >>> hit >>> it in our application (that is why we saw it). I mostly agree with the >>> OP >>> of the original bug report, this is memory space and as such should be >>> allocated somewhere in the memory map instead of assuming there is free >>> space after BSS. >>> >>> I *can* easily produce a patch for armv[678]-m (I have it already >>> implemented as a local patch in my Nuttx copy) and I have updated my >>> linker >>> script (same way as I updated QEMU test one). I can also patch all the >>> obvious ld files for other armv[678]-m targets. But I cannot test those >>> (I >>> do not have the HW) and I might miss some ld file... and the problem is >>> that would render the build unusable (strictly speaking, a linker script >>> change should not be necessary as the stack can be anywhere in the >>> memory, >>> but in other places of ARM-specific code it is assumed stack is >>> contiguous >>> to heap space). >>> >>> Shall I still prepare the patch? (Alan I know you already said but it >>> will >>> take a bit of time to go through all the ld files so I want to confirm >>> before getting to it). >> >> >> >> I think this makes sense. Build-time is a much better time to discover >> that your image won't fit than wondering why the board won't boot and >> then >> wasting time with debugging. >> >> It is even more important to detect things like this at build time >> because >> of automated testing like the pre-checks that run when PRs are opened. >> >> Please feel free to ping me when the PR is opened and I'll help >> review/test it. >> > > > I just had a thought. The linker scripts really should be per-arch, not > per-board, right? > > Then again, a particular board might have a special requirement that needs > a custom linker script just for that board. > > So maybe it would make more sense to migrate all the linker scripts to be > per-arch and add a Kconfig, e.g., a bool CONFIG_BOARD_LINKER_SCRIPT. If > true, then the board needs to provide its own ld.script; if false, we use > the default per-arch ld.script, and for most boards that should be > adequate. > > If this is done, then fixes like Carlos is discussing would take much less > work. > > Thoughts? > > Cheers > Nathan >
Re: [VOTE] Graduate Apache NuttX to TLP
+1 On 11/4/22, Nathan Hartman wrote: > Dear Apache Incubator Community, > > I would like to call a VOTE to graduate Apache NuttX from the > Incubator to the status of Top-Level-Project (TLP). > > The NuttX PPMC has held a community vote to graduate [1] and the vote > passed [2]. Following a community discussion [3] to draft our > resolution (see below) and secure a volunteer for Vice President of > Apache NuttX, and the gentle nudges we've been getting from our > mentors and the Incubator community to take this important step, > > I am pleased to call this VOTE: > > [ ] +1 Yes, Apache NuttX (Incubating) is ready to graduate from the > Apache Incubator to the status of Top Level Project. > > [ ] +0 No opinion. > > [ ] -1 No, Apache NuttX (Incubating) is NOT ready to graduate (please > state reason(s)). > > This vote will remain open for at least 72 hours. > > Some project highlights since incubation: > * Incubating for over 1000 days (since 2019-12-09) > * Website migrated to nuttx.apache.org > * Shipped 9 releases under the ASF Incubator > * Merged 8000 PRs across incubator-nuttx and incubator-nuttx-apps > * More than 1000 stars on GitHub > * More than 500 forks on GitHub > * More than 250 subscribers to d...@nuttx.apache.org > * In Top 10 Apache projects of 2021 by number of commits [4] > * 5 mentors > * 18 PPMC members > * 26 committers > * 75 ICLAs > * 2 CCLAs > * 21 SGAs > * 2 release managers > * 3 NuttX online workshops > * And much, much more > > Resolution: > > [[[ > > Establish the Apache NuttX Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to > establish a Project Management Committee charged with the creation and > maintenance of open-source software, for distribution at no charge to > the public, related to a mature, real-time embedded operating system > (RTOS). > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache NuttX Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache NuttX Project be and hereby is responsible > for the creation and maintenance of software related to a mature, real- > time embedded operating system (RTOS); and be it further > > RESOLVED, that the office of "Vice President, Apache NuttX" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache NuttX > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache NuttX > Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache NuttX Project: > > * Abdelatif Guettouche > * Alan Carvalho de Assis > * Alin Jerpelea > * Anthony Merlino > * Brennan Ashton > * David Sidrane > * Duo Zhang > * Flavio Paiva Junqueira > * Gregory Nutt > * Gustavo Henrique Nihei > * Junping Du > * Justin Mclean > * Lup Yuen Lee > * Masayuki Ishikawa > * Mohammad Asif Siddiqui > * Nathan Hartman > * Sara Monteiro > * Xiang Xiao > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alin Jerpelea be > appointed to the office of Vice President, Apache NuttX, to serve in > accordance with and subject to the direction of the Board of Directors > and the Bylaws of the Foundation until death, resignation, retirement, > removal or disqualification, or until a successor is appointed; and be > it further > > RESOLVED, that the Apache NuttX Project be and hereby is tasked with > the migration and rationalization of the Apache Incubator NuttX > podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > NuttX podling encumbered upon the Apache Incubator PMC are hereafter > discharged. > > ]]] > > Meanwhile, let me express a big ***THANK YOU*** to everyone involved > for helping us get this far! > > References: > > [1] [VOTE] Apache NuttX Community Graduation > https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4 > > [2] [RESULT][VOTE] Apache NuttX Community Graduation > https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2 > > [3] [DISCUSS] NuttX graduation: Draft Resolution > https://lists.apache.org/thread/f07lsqfhb9zc5cwbzw1ds4ltbxftsk7f > > [4] > https://thestack.technology/top-apache-projects-in-2021-from-superset-to-nuttx/ > > Thanks to everyone! > > Cheers, > Nathan > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To
Re: OT Geso PAEC
Question. Why are Swans tagged? Licence? Alan C On 02-Nov-22 11:22 PM, Toine wrote: The tags on your swans are really big. On our swans they even put tags on their necks. It doesn't hurt or hinder the birds but it sure looks funny (not). Toine On Wed, 2 Nov 2022 at 22:12, David J Brooks wrote: -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: ARM -m startup does not check for idle thread stack space
Hi Carlos,
I tested and confirmed the issue:
$ patch -p1 <
~/Desktop/0001-Changes-to-force-fill-bss-section-causing-sp-past-th.patch
patching file arch/arm/src/armv7-m/arm_vectors.c
$ ./tools/configure.sh lm3s6965-ek:qemu-flat
$ make -j8
$ qemu-system-arm -semihosting \
-M lm3s6965evb \
-device loader,file=nuttx.bin,addr=0x \
-netdev user,id=user0 \
-nic user,id=user0 \
-serial mon:stdio -nographic
$ qemu-system-arm -semihosting -M lm3s6965evb -device
loader,file=nuttx.bin,addr=0x -netdev user,id=user0 -nic
user,id=user0 -serial mon:stdio -nographic
qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
R00= R01= R02=40025000 R03=0004
R04= R05=2000c620 R06=0003 R07=
R08= R09= R10= R11=
R12= R13=200101e8 R14=0b7b R15=
XPSR=0003 A handler
FPSCR:
Aborted (core dumped)
Please submit the PR and includer for v6/8 too.
BR,
Alan
On 11/3/22, Carlos Sanchez wrote:
> Hi all,
>
> I have detected the armv{6,7,8}-m/arm_vectors.c assigns the initial
> stack pointer value (using the first entry at the exception vectors
> table) just to _ebss + CONFIG_IDLETHREAD_STACKSIZE, without further
> checking. This can yield to an unusable binary if .data or .bss
> sections grow too much.
>
> To test, use the attached patch 0001 and ./tools/configure.sh
> lm3s6965-ek:qemu-flat
>
> (Note with stacks just below SRAM limit the NSH prompt will still not
> be visible because booting will fail during heap allocation, but still
> the "ABCDF" booting markers will be shown; when the stack starting
> point is past the SRAM end, booting fails immediately and those
> markers are not shown).
>
> There are multiple ways to fix (= detect this at build time) this
> problem. The best IMHO is to make the stack space appear at the memory
> map and be allocated. This will cause a region overflow error during
> linking when the initial stack overflows SRAM (as intended). For a
> demo of this fix (for lm3s6965-ek:qemu-flat only) see attached patch
> 0002.
>
> Unfortunately, this requires linker script changes for most platforms.
> Without the changes, the initial stack would be correctly allocated
> (ld would just map ".stack" section to any writable memory region) but
> several other parts of the code assume the heap to be just after the
> idle thread stack, which cannot be guaranteed without the
> aforementioned linker script changes.
>
> So I want to ask here for opinion before progressing further, as a
> change this deep would affect a lot of platforms which I do not have
> the means to test.
>
> WDYT?
>
> Carlos
>
Re: libpq and libscpi: how to start
Hi Sebastien, Good question, AFAIK there is not yet a command to just download the necessary tar balls and keep them in a downloaded area to use later. If I remember correctly some build systems like Buildroot and Yocto has this option. BR, Alan On 11/3/22, Sebastien Lorquet wrote: > Hi, > > littlefs too. > > This raises an important question for me: how do I handle such a build > in a self-contained, "airgapped" machine? > > Are there provisions to use a pre-downloaded tarball for external projects? > > Sebastien > > Le 28/10/2022 à 18:30, Alan C. Assis a écrit : >> Hi Sebastien, >> >> AFAIK there is not such directive, although it is always need to add >> support to NuttX on external projects. >> >> External projects needs to be integrated to be downloaded and compiled >> dynamically, once again like LVGL. >> >> BR, >> >> Alan >> >> On 10/28/22, Sebastien Lorquet wrote: >>> IIRC the idea was that we dont integrate code fom externally maintained >>> projects? >>> >>> Also IIRC the acceptable method is a specific makefile that downloads >>> code and patch/builds it. >>> >>> I agree that such libs go into apps. >>> >>> Sebastien >>> >>> Le 27/10/2022 à 19:28, Nathan Hartman a écrit : >>>> On Thu, Oct 27, 2022 at 12:19 PM Alan C. Assis >>>> wrote: >>>> >>>>> Hi Michael, >>>>> >>>>> I think someone else told some time ago that he used a similar lib for >>>>> mysql, I think it was Ivan. >>>>> >>>>> Those libs inside nuttx/libs/ are libs used by the kernel and apps, >>>>> but in this case the lib should be put inside apps/databases/postgres >>>>> for example. It should be a lib just like apps/graphics/lvgl and many >>>>> others. >>>> I agree with that; nothing prevents applications from using the libs >>>> under >>>> apps. >>>> >>>> If they require kernel support then that might be another thing. >>>> >>>> Cheers >>>> Nathan >>>> >
Re: Native Windows build
Hi Zouboan, Unfortunately there is nobody working with Windows Native Environment and some time ago someone reported it was delaying about 10 minutes to compile NuttX. So I think it is not an issue with your tools, but with NuttX Building System. My suggestion is if someone fixes it we add Windows Native Environment build in our CI to avoid breaking it again. BR, Alan On 11/2/22, fft wrote: > Dear all, > > > A few years ago, I successfully configure and build NuttX-8.2 in a native > Windows environment (the toolchains is GNU-Win32 + > kconfig-frontends-win32-3.12.1 + MinGW, and the host OS is both XP and Win7 > ) , I can even debug NuttX through Code::Blocks IDE under Windows. But now i > find the NuttX can not build in native Windows environment anymore, the > environment and toolchains is exactly what i had configured a few years ago, > but now it failed at configure stage, I tried to fix the configure, but i > found there's too many changes involved. So I have to ask, is there anybody > build NuttX in native Windows environment recently? or is the issues of my > toolchains? > > > regards, > Zouboan
Re: Bluetooth+WiFi+NuttX
Hi Tim, Probably you saw that you will need to use some external clock. You can try to use the ESP32 generated clock CLOCKOUT (ideally you can add a 0R option option to use CLOCKOUT180 instead) and connect it to GTXCK. Case it doesn't work you will need an external 50MHz oscillator. BR, Alan On 10/29/22, TimH wrote: > I meant esp32 not esr32. The naming is too similar lol > >> On 29 Oct 2022, at 15:51, Tim Hardisty wrote: >> >> Thanks Alan! SAMA5D2 has RMII so definitely a possibility. EFR32 is a >> much better value device compared to SiLabs Bluetooth 5 module currently >> used, and has WiFi as a bonus - so I will investigate it's IDE and see how >> easy it is to implement a GATT-based solution, or to load HCI firmware so >> I can be reasonably confident I'm not digging a big hole for myself if I >> make this change. >> >> >> On 29/10/2022, 13:23, "Alan C. Assis" wrote: >> >>More info here: >> >> >> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/366759/am335x-rmii-direct-connection-between-two-devices >> >>Same TI guy who said it was impossible latter talk internally and >>discovered that there was a customer already using it. >> >>BTW, you will need to have RMII supported by both MCUs (yes, ESP32 has >> RMII). >> >>BR, >> >>Alan >> >>>On 10/29/22, Alan C. Assis wrote: >>> Hi Tim, >>> >>> I just searched if it was possible to connect two Ethernet MAC >>> directly without using PHY and it is possible, so it will not involve >>> cost for you: >>> >>> https://stackoverflow.com/questions/39503466/can-two-ethernet-mac-chips-be-connected-directly-without-going-thru-phy >>> >>> BR, >>> >>> Alan >>> >>>> On 10/29/22, Tim Hardisty wrote: >>>> Thanks for your clarifications Alan - I have messaged Espressif (your >>>> reply >>>> ended up in SPAM otherwise I might not have needed to) so I guess I'll >>>> get >>>> a >>>> similar answer. >>>> >>>> There is HCI (RCP) firmware for the SiLabs module so I can try that - >>>> it's >>>> the £7 per module saving of Espressif vs. SiLabs, plus getting WiFi for >>>> free >>>> that appeals. SAMA5D2 has Ethernet - unused on my board so it is not an >>>> idea >>>> that is completely out of the question: writing USRSOCK for the >>>> Espressif >>>> module is probably beyond me at this time! >>>> >>>> On 29/10/2022, 00:20, "Alan C. Assis" wrote: >>>> >>>>Hi Tim, >>>> >>>>On 10/28/22, Tim Hardisty wrote: >>>>> Bit of a tangential question this, but I know there are folk on >>>> here >>>> who >>>>> are much more conversant with the way NuttX can be used with WiFi >>>> and >>>>> Bluetooth modules than I am. >>>>> >>>> >>>>I think these are important questions and other people could face >>>>similar issues in the future. >>>> >>>>> I may have an opportunity forced on me to have to respin my custom >>>> board >>>>> which currently has a SiLabs Bluetooth SoC as well as the main >>>> SAMA5D2 >>>>> processor. I used that module as I already have experience of it - >>>> but >>>> that >>>>> predates my NuttX journey. >>>>> >>>>> I see there are some very good value combined WiFi + Bluetooth >>>> modules >>>> now >>>>> (Espressif for example...and I know there's a well-known proponent >>>> of >>>> those >>>>> devices here lol) and, having seen a few other questions here, I am >>>> thinking >>>>> that I can go the HCI route and make use of the Bluetooth Stack in >>>> NuttX: >>>>> and add WiFi capability to my board at the same time. Winner! >>>>> >>>> >>>>First let me explain the differences: >>>> >>>>Espressif modules are not used as external modules on NuttX, >>>>everything is integrated inside the chip. >>>> >>>>During the WildernessLab's presentation on NuttX Workshop their team >>>>shown an ESP32 solution sharing WiFi as an external module. >>>>But they didn't use the default USRSOCK
Re: Bluetooth+WiFi+NuttX
More info here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/366759/am335x-rmii-direct-connection-between-two-devices Same TI guy who said it was impossible latter talk internally and discovered that there was a customer already using it. BTW, you will need to have RMII supported by both MCUs (yes, ESP32 has RMII). BR, Alan On 10/29/22, Alan C. Assis wrote: > Hi Tim, > > I just searched if it was possible to connect two Ethernet MAC > directly without using PHY and it is possible, so it will not involve > cost for you: > > https://stackoverflow.com/questions/39503466/can-two-ethernet-mac-chips-be-connected-directly-without-going-thru-phy > > BR, > > Alan > > On 10/29/22, Tim Hardisty wrote: >> Thanks for your clarifications Alan - I have messaged Espressif (your >> reply >> ended up in SPAM otherwise I might not have needed to) so I guess I'll get >> a >> similar answer. >> >> There is HCI (RCP) firmware for the SiLabs module so I can try that - >> it's >> the £7 per module saving of Espressif vs. SiLabs, plus getting WiFi for >> free >> that appeals. SAMA5D2 has Ethernet - unused on my board so it is not an >> idea >> that is completely out of the question: writing USRSOCK for the >> Espressif >> module is probably beyond me at this time! >> >> On 29/10/2022, 00:20, "Alan C. Assis" wrote: >> >> Hi Tim, >> >> On 10/28/22, Tim Hardisty wrote: >> > Bit of a tangential question this, but I know there are folk on >> here >> who >> > are much more conversant with the way NuttX can be used with WiFi >> and >> > Bluetooth modules than I am. >> > >> >> I think these are important questions and other people could face >> similar issues in the future. >> >> > I may have an opportunity forced on me to have to respin my custom >> board >> > which currently has a SiLabs Bluetooth SoC as well as the main >> SAMA5D2 >> > processor. I used that module as I already have experience of it - >> but >> that >> > predates my NuttX journey. >> > >> > I see there are some very good value combined WiFi + Bluetooth >> modules >> now >> > (Espressif for example...and I know there's a well-known proponent >> of >> those >> > devices here lol) and, having seen a few other questions here, I am >> thinking >> > that I can go the HCI route and make use of the Bluetooth Stack in >> NuttX: >> > and add WiFi capability to my board at the same time. Winner! >> > >> >> First let me explain the differences: >> >> Espressif modules are not used as external modules on NuttX, >> everything is integrated inside the chip. >> >> During the WildernessLab's presentation on NuttX Workshop their team >> shown an ESP32 solution sharing WiFi as an external module. >> But they didn't use the default USRSOCK route, they implemented a new >> solution at home. >> >> > I'm hoping I can program up a suitable module with generic radio >> > co-processor software (HCI I think, and whatever is needed for >> WiFi) >> and >> > access it via UART from my main processor and have it all under the >> NuttX >> > system in a much more easily managed manner than a separate app on >> the >> > SiLabs SoC that just happens to communicate on some way with my >> main >> app on >> > the SAMA5D2. >> > >> > Have I got this right? Is an Espressif module a good choice (email >> me >> direct >> > if you want to !!)? >> > >> >> For Bluetooth (BLE) if there is a HCI firmware to SiLabs chip, then >> it >> could be possible to you use it, but you'll need to do some tests and >> debugging to get things working. >> >> For WiFi things are more complex because you need to implement a >> USRSOCK yourself to the chip. >> >> I never tested others possibilities: i.e. share Internet using SLIP >> between ESP32 and SAMA5D2, should be an easier route if it works, but >> of course you wil be limited to UART speed. >> >> Ethernet could be a better option (since ESP32 has Ethernet >> hardware), >> but it seems like an ugly and expensive workaround. >> >> BR, >> >> Alan >> >> >> >
Re: Bluetooth+WiFi+NuttX
Hi Tim, I just searched if it was possible to connect two Ethernet MAC directly without using PHY and it is possible, so it will not involve cost for you: https://stackoverflow.com/questions/39503466/can-two-ethernet-mac-chips-be-connected-directly-without-going-thru-phy BR, Alan On 10/29/22, Tim Hardisty wrote: > Thanks for your clarifications Alan - I have messaged Espressif (your reply > ended up in SPAM otherwise I might not have needed to) so I guess I'll get a > similar answer. > > There is HCI (RCP) firmware for the SiLabs module so I can try that - it's > the £7 per module saving of Espressif vs. SiLabs, plus getting WiFi for free > that appeals. SAMA5D2 has Ethernet - unused on my board so it is not an idea > that is completely out of the question: writing USRSOCK for the Espressif > module is probably beyond me at this time! > > On 29/10/2022, 00:20, "Alan C. Assis" wrote: > > Hi Tim, > > On 10/28/22, Tim Hardisty wrote: > > Bit of a tangential question this, but I know there are folk on here > who > > are much more conversant with the way NuttX can be used with WiFi > and > > Bluetooth modules than I am. > > > > I think these are important questions and other people could face > similar issues in the future. > > > I may have an opportunity forced on me to have to respin my custom > board > > which currently has a SiLabs Bluetooth SoC as well as the main > SAMA5D2 > > processor. I used that module as I already have experience of it - but > that > > predates my NuttX journey. > > > > I see there are some very good value combined WiFi + Bluetooth modules > now > > (Espressif for example...and I know there's a well-known proponent of > those > > devices here lol) and, having seen a few other questions here, I am > thinking > > that I can go the HCI route and make use of the Bluetooth Stack in > NuttX: > > and add WiFi capability to my board at the same time. Winner! > > > > First let me explain the differences: > > Espressif modules are not used as external modules on NuttX, > everything is integrated inside the chip. > > During the WildernessLab's presentation on NuttX Workshop their team > shown an ESP32 solution sharing WiFi as an external module. > But they didn't use the default USRSOCK route, they implemented a new > solution at home. > > > I'm hoping I can program up a suitable module with generic radio > > co-processor software (HCI I think, and whatever is needed for WiFi) > and > > access it via UART from my main processor and have it all under the > NuttX > > system in a much more easily managed manner than a separate app on > the > > SiLabs SoC that just happens to communicate on some way with my main > app on > > the SAMA5D2. > > > > Have I got this right? Is an Espressif module a good choice (email me > direct > > if you want to !!)? > > > > For Bluetooth (BLE) if there is a HCI firmware to SiLabs chip, then it > could be possible to you use it, but you'll need to do some tests and > debugging to get things working. > > For WiFi things are more complex because you need to implement a > USRSOCK yourself to the chip. > > I never tested others possibilities: i.e. share Internet using SLIP > between ESP32 and SAMA5D2, should be an easier route if it works, but > of course you wil be limited to UART speed. > > Ethernet could be a better option (since ESP32 has Ethernet hardware), > but it seems like an ugly and expensive workaround. > > BR, > > Alan > > >
Re: Bluetooth+WiFi+NuttX
Hi Tim, On 10/28/22, Tim Hardisty wrote: > Bit of a tangential question this, but I know there are folk on here who > are much more conversant with the way NuttX can be used with WiFi and > Bluetooth modules than I am. > I think these are important questions and other people could face similar issues in the future. > I may have an opportunity forced on me to have to respin my custom board > which currently has a SiLabs Bluetooth SoC as well as the main SAMA5D2 > processor. I used that module as I already have experience of it - but that > predates my NuttX journey. > > I see there are some very good value combined WiFi + Bluetooth modules now > (Espressif for example...and I know there's a well-known proponent of those > devices here lol) and, having seen a few other questions here, I am thinking > that I can go the HCI route and make use of the Bluetooth Stack in NuttX: > and add WiFi capability to my board at the same time. Winner! > First let me explain the differences: Espressif modules are not used as external modules on NuttX, everything is integrated inside the chip. During the WildernessLab's presentation on NuttX Workshop their team shown an ESP32 solution sharing WiFi as an external module. But they didn't use the default USRSOCK route, they implemented a new solution at home. > I'm hoping I can program up a suitable module with generic radio > co-processor software (HCI I think, and whatever is needed for WiFi) and > access it via UART from my main processor and have it all under the NuttX > system in a much more easily managed manner than a separate app on the > SiLabs SoC that just happens to communicate on some way with my main app on > the SAMA5D2. > > Have I got this right? Is an Espressif module a good choice (email me direct > if you want to !!)? > For Bluetooth (BLE) if there is a HCI firmware to SiLabs chip, then it could be possible to you use it, but you'll need to do some tests and debugging to get things working. For WiFi things are more complex because you need to implement a USRSOCK yourself to the chip. I never tested others possibilities: i.e. share Internet using SLIP between ESP32 and SAMA5D2, should be an easier route if it works, but of course you wil be limited to UART speed. Ethernet could be a better option (since ESP32 has Ethernet hardware), but it seems like an ugly and expensive workaround. BR, Alan
Re: [DISCUSS] NuttX graduation: Draft Resolution
Agree! Alin is actively helping this project! BR, Alan On 10/28/22, Alin Jerpelea wrote: > If none has a better idea I can step in > > Best Regards > Alin > > On Fri, 28 Oct 2022, 06:35 Nathan Hartman, > wrote: > >> Ping... Folks, we need to choose a Vice President for the proposed >> Apache NuttX TLP. >> >> >> On Tue, Oct 25, 2022 at 9:55 PM Nathan Hartman >> wrote: >> > >> > Dear NuttX community, >> > >> > As our community VOTE [1] for graduation to Top Level Project has >> > PASSED [2], the next steps are: >> > >> > (1) Draft our Charter/Resolution >> > (2) Decide members of the initial Project Management Committee (PMC) >> > (3) Choose the 1st Vice President of the proposed Apache NuttX PMC >> > >> > Please participate so we can get this done efficiently! >> > >> > Regarding item #1, below please find a 1st Draft Resolution for review >> > and discussion -- this draft was generated by Whimsy (there's a button >> > at the bottom of our podling page [3] to draft the resolution). Please >> > read it anyway and provide feedback!!! >> > >> > Regarding item #2, currently the draft resolution lists all members of >> > the Apache NuttX (Incubating) PPMC to become members of the proposed >> > Apache NuttX PMC. If anyone feels there should be changes, please let >> > us know. >> > >> > Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!] >> > where the name of the proposed Vice President should be written. We >> > need to decide who that will be. The Vice President reports to the >> > board 4 times each year, similarly to how we have been reporting to >> > the Incubator PMC (IPMC), but there are no mentors who need to sign >> > off on it. Speak up if you're interested in being the Vice President >> > of Apache NuttX! >> > >> > 1st draft of our Resolution: >> > >> > [[[ >> > >> > Establish the Apache NuttX Project >> > >> > WHEREAS, the Board of Directors deems it to be in the best interests of >> > the Foundation and consistent with the Foundation's purpose to >> > establish a Project Management Committee charged with the creation and >> > maintenance of open-source software, for distribution at no charge to >> > the public, related to a mature, real-time embedded operating system >> > (RTOS). >> > >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee >> > (PMC), to be known as the "Apache NuttX Project", be and hereby is >> > established pursuant to Bylaws of the Foundation; and be it further >> > >> > RESOLVED, that the Apache NuttX Project be and hereby is responsible >> > for the creation and maintenance of software related to a mature, real- >> > time embedded operating system (RTOS); and be it further >> > >> > RESOLVED, that the office of "Vice President, Apache NuttX" be and >> > hereby is created, the person holding such office to serve at the >> > direction of the Board of Directors as the chair of the Apache NuttX >> > Project, and to have primary responsibility for management of the >> > projects within the scope of responsibility of the Apache NuttX >> > Project; and be it further >> > >> > RESOLVED, that the persons listed immediately below be and hereby are >> > appointed to serve as the initial members of the Apache NuttX Project: >> > >> > * Abdelatif Guettouche >> > * Alan Carvalho de Assis >> > * Alin Jerpelea >> > * Anthony Merlino >> > * Brennan Ashton >> > * David Sidrane >> > * Duo Zhang >> > * Flavio Paiva Junqueira >> > * Gregory Nutt >> > * Gustavo Henrique Nihei >> > * Junping Du >> > * Justin Mclean >> > * Lup Yuen Lee >> > * Masayuki Ishikawa >> > * Mohammad Asif Siddiqui >> > * Nathan Hartman >> > * Sara Monteiro >> > * Xiang Xiao >> > >> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!] >> > be appointed to the office of Vice President, Apache NuttX, to serve in >> > accordance with and subject to the direction of the Board of Directors >> > and the Bylaws of the Foundation until death, resignation, retirement, >> > removal or disqualification, or until a successor is appointed; and be >> > it further >> > >> > RESOLVED, that the Apache NuttX Project be and hereby is tasked with >> > the migration and rationalization of the Apache Incubator NuttX >> > podling; and be it further >> > >> > RESOLVED, that all responsibilities pertaining to the Apache Incubator >> > NuttX podling encumbered upon the Apache Incubator PMC are hereafter >> > discharged. >> > >> > ]]] >> > >> > References: >> > >> > [1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4 >> > >> > [2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2 >> > >> > [3] https://whimsy.apache.org/roster/ppmc/nuttx >> > >> > [4] https://incubator.apache.org/guides/graduation.html >> > >> > Thanks to everyone! >> > >> > Cheers, >> > Nathan >> >
Re: libpq and libscpi: how to start
Hi Sebastien, AFAIK there is not such directive, although it is always need to add support to NuttX on external projects. External projects needs to be integrated to be downloaded and compiled dynamically, once again like LVGL. BR, Alan On 10/28/22, Sebastien Lorquet wrote: > IIRC the idea was that we dont integrate code fom externally maintained > projects? > > Also IIRC the acceptable method is a specific makefile that downloads > code and patch/builds it. > > I agree that such libs go into apps. > > Sebastien > > Le 27/10/2022 à 19:28, Nathan Hartman a écrit : >> On Thu, Oct 27, 2022 at 12:19 PM Alan C. Assis wrote: >> >>> Hi Michael, >>> >>> I think someone else told some time ago that he used a similar lib for >>> mysql, I think it was Ivan. >>> >>> Those libs inside nuttx/libs/ are libs used by the kernel and apps, >>> but in this case the lib should be put inside apps/databases/postgres >>> for example. It should be a lib just like apps/graphics/lvgl and many >>> others. >> >> I agree with that; nothing prevents applications from using the libs >> under >> apps. >> >> If they require kernel support then that might be another thing. >> >> Cheers >> Nathan >> >
Re: libpq and libscpi: how to start
Hi Michael, I think someone else told some time ago that he used a similar lib for mysql, I think it was Ivan. Those libs inside nuttx/libs/ are libs used by the kernel and apps, but in this case the lib should be put inside apps/databases/postgres for example. It should be a lib just like apps/graphics/lvgl and many others. BR, Alan On 10/27/22, michael.sch...@mdc-service.de wrote: > Dear all, > > i would like to see Nuttx support for the PostgreSQL client library > libpq(https://github.com/postgres/postgres/tree/master/src/interfaces/libpq), > > and a library for SCPI(https://www.jaybee.cz/scpi-parser/api/). These > scpi parser lib could then be used for USBTMC and LXI, 2 standards to > expose lab instruments in a standardized way to software like LabView, > GNU Octave, ect. > > Both projects are under BSD license, so they should be compatible from > the license side with Nuttx. > > I think, as common libraries for other app, and maybe service, they > should be placed under nuttxspace/nuttx/libs in the Nuttx tree, not in > the application tree. At least the PostgreSQL client library requires > network. What would be the advice, where to place these kind of > libraries? > > For the PostgreSQL client library, there are implementations for > Arudino, additional to the PC based implementations. But because the > POSIX compatibility of Nuttx, starting from the Linux version should > make more sense, or? > > regards, > Michael >
Re: Dev-Board for Nuttx
Hi Michael, Yes, this is the way to go! Actually NuttX already supports loading ELF from SDCard or USB Thumb Driver (called "pendrive" in some countries). I created a video demonstrating it, see here: https://www.youtube.com/watch?v=oL6KAgkTb8M Also there is a PR in progress that will extend the ELF loading to enable loading libraries: https://github.com/apache/incubator-nuttx/pull/7202 About the JTAG, I think it should be nice to have an standard connector, but of course it uses a lot of space in the board. BR, Alan On 10/26/22, michael.sch...@mdc-service.de wrote: > Hi Alan, > > I am really happy to got your interest. Replacing the Pi with an EsPiFF > with Nuttx is also our intention. > > The SWD for the RP2040 is alredy broken out, on J5, pin 6(SWCLK) and pin > 8 (SWDIO). The connector J5 is a DF11, 2mm spacing connector, we will > add cables with 2.54 Duponts on the other side. The RP2040 have > exclusive pins for SWD, so no limit on functionality. Just for the > ESP32, we need to add the JTAG header. We used that DF11 connector, to > make these pins accesable from outside, when the EsPiFf is in a > Raspberry Pi 4 enclosure, what have 2 mini HDMI connectors at this > position. Other connectors would be too big for the openings for mini > HDMI. > > In the past, I did also STM32 boards, until the chip crisis made most of > the STM32Fxxx unavailable. This is the big advantage of the ESP32, they > are always available. I have not yet jumped on the GD32xxx and friends > as pincompatible? replacement, that could be an way out. But 8 MB RAM on > a board, means for most MCUs external RAM, whats included with the > ESP32-WROVER. I am hoping, that (one day) to load ELF binaries from > SDcard into memory and execute it, as Linux is doing. This will open a > new chapter in using microcontrollers, and Nuttx is already nearly > there. > > Would be happy to see the EsPiFF one day in your Nuttx Videos! > > best regards, > Michael > > Am 2022-10-26 14:56, schrieb Alan C. Assis: >> Hi Michael, >> >> Congratulations! You created a really great board!!! >> >> I'm sure that many people here will be interested on it, those who are >> really interested to contribute. >> >> The idea of using RPI form-factor is really good. Actually we were >> discussing about the idea of creating some RPI-like board to replace >> high level Linux system with a system running NuttX RTOS. >> >> I think adding JTAG for ESP32 and SWD for RP2040 will be very useful, >> please include it for the final board. >> >> A friend of mine created a nice and simple board for NuttX that he >> released as open-source: >> >> https://github.com/lucaszampar/NuttX_STM32F4_RS485_DevBoard >> >> He send me some pictures that I put on my flickr: >> >> https://live.staticflickr.com/65535/52456145643_97eca8e9b1_o.jpg >> >> https://live.staticflickr.com/65535/52455885674_94eba29fcc_b.jpg >> >> Soon, he will submit support to mainline. >> >> BR, >> >> Alan >> >> On 10/26/22, michael.sch...@mdc-service.de >> wrote: >>> Dear Nuttx developers, >>> >>> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form >>> Factor), a open source board to replace RasPi's and there clones, >>> where >>> the high processing power and/or Linux is not needed, but stability >>> and >>> the reuse of RasPi HATs are required. >>> >>> The github home is https://github.com/MDCservice/EsPiFF >>> >>> We will also offer the EsPiFF on CrowdSupply >>> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff >>> >>> We would like to send a few boards for free to Nuttx developers, to >>> improve Nuttx compatibility. Would there be interest? >>> >>> A high level summary about the EsPiFF: >>> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care >>> - wired Ethernet via a IP101 PHY, >>> - Wifi (need an external Wifi Antenna with uFL connector), >>> - 3 serial UARTs, >>> - one the 3 serial UARTs is used for programming via a CH340 USB-UART >>> chip, what can be enabled/disabled with jumpers, >>> - I2C port expander PCA 9557 for some chip select signals and 3 user >>> LEDs, >>> - SDcard in SPI mode, >>> - external real time clock, with supervisior, >>> - 2kB FRAM, >>> - USB Type-C connector for up to 5V/3A, connected to the CH340 >>> USB-UART >>> to program the ESP32 >>> >>> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header, >>> - connected to t
Re: Dev-Board for Nuttx
Hi Michael, Congratulations! You created a really great board!!! I'm sure that many people here will be interested on it, those who are really interested to contribute. The idea of using RPI form-factor is really good. Actually we were discussing about the idea of creating some RPI-like board to replace high level Linux system with a system running NuttX RTOS. I think adding JTAG for ESP32 and SWD for RP2040 will be very useful, please include it for the final board. A friend of mine created a nice and simple board for NuttX that he released as open-source: https://github.com/lucaszampar/NuttX_STM32F4_RS485_DevBoard He send me some pictures that I put on my flickr: https://live.staticflickr.com/65535/52456145643_97eca8e9b1_o.jpg https://live.staticflickr.com/65535/52455885674_94eba29fcc_b.jpg Soon, he will submit support to mainline. BR, Alan On 10/26/22, michael.sch...@mdc-service.de wrote: > Dear Nuttx developers, > > we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form > Factor), a open source board to replace RasPi's and there clones, where > the high processing power and/or Linux is not needed, but stability and > the reuse of RasPi HATs are required. > > The github home is https://github.com/MDCservice/EsPiFF > > We will also offer the EsPiFF on CrowdSupply > https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff > > We would like to send a few boards for free to Nuttx developers, to > improve Nuttx compatibility. Would there be interest? > > A high level summary about the EsPiFF: > An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care > - wired Ethernet via a IP101 PHY, > - Wifi (need an external Wifi Antenna with uFL connector), > - 3 serial UARTs, > - one the 3 serial UARTs is used for programming via a CH340 USB-UART > chip, what can be enabled/disabled with jumpers, > - I2C port expander PCA 9557 for some chip select signals and 3 user > LEDs, > - SDcard in SPI mode, > - external real time clock, with supervisior, > - 2kB FRAM, > - USB Type-C connector for up to 5V/3A, connected to the CH340 USB-UART > to program the ESP32 > > An RP2040 (Pi Pico) what takes care the 40 pin RasPi header, > - connected to the ESP32 via SPI, > - UAB-A connector, also used to program the RP2040 (need to hold the > boot button while power the board). > > In earlier versions, we had the LAN8720 PHY, but as others (Olimex, > wESP) we also got problems and replaced it with the IP101 since v3.1. > > Currently, there is no HW debugging broken out on the board. But we > could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS, > GND, 3V3 in the next board production run. The ESP32 has the JTAG pins > on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code > using the SPI could not be debugged while JTAG is using the pins. Would > it still make sense to build in the JTAG header? > > Would be glad to get your feedback, > Michael >
Re: [VOTE] Apache NuttX Community Graduation
+1 Finally!!! I hope we could remove that cumbersome "incubator-nuttx" name! Or even better: redirect it to "nuttx" to avoid issues! On 10/21/22, Nathan Hartman wrote: > Dear Apache NuttX Community, > > Following the [DISCUSS] thread which has gone 72 hours without any > further issues raised [1]: > > This is a call to VOTE on Graduation of Apache NuttX from the > Incubator to Top-Level Project (TLP). > > Please vote: > > [ ] +1: Apache NuttX is ready to graduate to TLP > [ ] 0: No opinion > [ ] -1: Apache NuttX is NOT ready to graduate; please state reason(s) > > If this community vote passes, we will proceed to the next steps. The > graduation process is documented at [2]. The vote will remain open for > at least 72 hours. A minimum of 3 binding +1 votes and more binding +1 > than binding -1 are required to pass. The ASF requirements for voting > can be found at [3]. > > Project Highlights Since Incubation: > * Incubating since 2019-12-09 > * Website migrated to nuttx.apache.org > * Shipped 9 releases under the ASF Incubator > * Merged 8000 PRs across incubator-nuttx and incubator-nuttx-apps > * More than 1000 stars on GitHub > * More than 500 forks on GitHub > * More than 250 subscribers to dev@nuttx.apache.org > * In Top 10 Apache projects of 2021 by number of commits [4] > * 5 mentors > * 18 PPMC members > * 26 committers > * 75 ICLAs > * 2 CCLAs > * 21 SGAs > * 2 release managers > * 3 NuttX online workshops > * And much, much more > > Let me express a big ***THANK YOU*** to everyone for helping make this > possible! > > [1] https://lists.apache.org/thread/vpj21ofyxmjs528n3b9s72wozh9hjz8f > > [2] > https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project > > [3] https://www.apache.org/foundation/voting.html > > [4] > https://thestack.technology/top-apache-projects-in-2021-from-superset-to-nuttx/ > > Cheers, > Nathan Hartman >
Re: [DISCUSS] Graduate NuttX as TLP
+1 Please go ahead Nathan! BR, Alan On 10/19/22, David Sidrane wrote: > +1 - The time has come. > > David > > -Original Message- > From: Xiang Xiao > Sent: Wednesday, October 19, 2022 1:52 AM > To: dev@nuttx.apache.org > Subject: Re: [DISCUSS] Graduate NuttX as TLP > > +1. > We are ready after two years of incubation! > > On Wed, Oct 19, 2022 at 1:07 PM Alin Jerpelea wrote: > >> +1 >> I think that we are ready to graduate >> >> >> Best regards >> Alin >> >> On Wed, 19 Oct 2022, 06:16 Tomek CEDRO, wrote: >> >> > Just my vote for the path names: >> > apache/nuttx_rtos >> > apache/nuttx_apps >> > >> > Looks safe and self-explanatory :-) >> > >> > If clone to nuttx_rtos.git/ and nuttx_apps.git/ would be also >> > acceptable that would be perfect (and marked there is a git repo >> > inside). >> > >> > Thank You and Good Luck! :-) >> > >> > -- >> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >> > >> >
Re: [ANNOUNCE] Apache NuttX 11.0.0-incubating released
Thank you Alin! Amazing job! On Saturday, October 15, 2022, Alin Jerpelea wrote: > The Apache NuttX (incubating) project team is proud to announce > Apache NuttX 11.0.0-incubating has been released. > > The release artifacts and Release Notes can be found > at:https://nuttx.apache.org/download/https://nuttx.apache. > org/releases/11.0.0/ > > Thanks, > Alin Jerpelea > on behalf of Apache NuttX PPMC >
Re: Anna-b112 Bluetooth module support
Hi Ivan, Right, I think this is a good approach case you don't want to replace the firmware. Maybe for WiFi the u-connect could be used with USRSOCK. BR, Alan On 10/14/22, Embedded Systems wrote: > Hi Alan, > > Unfortunately ublox does not, maybe Nordic does, but i dont wish to reflash > the module. What i am thinking is to implement an u-connect parser similar > to the NMEA parser (GPS parcer) and implement it in utils in apps, in this > way i wont disturb the already existing Bluetooth functionality and add > support for ublox devices which use u-connect, they have also Wifi and > other modules which use u-connect so i think it will be nice addition to > have this parser in Nuttx. > > Best regards, > Ivan > > On Fri, Oct 14, 2022 at 2:53 PM Alan C. Assis wrote: > >> Hi Ivan, >> >> Ok, understood the issue! >> >> Maybe U-Block has an HCI H4 firmware that you can use on Anna-B112 >> instead of this AT firmware. It's always a good idea to use and follow >> the standard, this is a compelling motivation to use NuttX in the >> first place! :-) >> >> BR, >> >> Alan >> >> On 10/14/22, Embedded Systems wrote: >> > Hello Alan, >> > >> > Unfortunately we cannot use the module as HCI H4, we can control it >> > only >> > with AT commands. So in our case IMXRT is running nuttx and its >> > connected >> > to the BLE module with uart and control it with AT commands, so far i >> just >> > implemented an application in nuttx which controls the module from the >> user >> > space. The aplication is using a UART char driver to communicate with >> > the >> > module and everything else is managed in the application , but i dont >> think >> > this is a good way to use the module and i wish to make a driver in >> > nuttx >> > for it, My problem is that i dont see a good way to implement the >> > driver >> > and connect it with the already existing nuttx Bluetooth >> > functionalities >> . >> > >> > >> > Best regards, >> > Ivan >> > >> > On Thu, Oct 13, 2022 at 11:59 PM Alan C. Assis >> wrote: >> > >> >> Hi Ivan, >> >> >> >> Normally using external BLE modules that follows the HCI H4 is easier >> >> than porting to some chip with internal BLE and application in the >> >> same chip. >> >> >> >> You can see how it is done in the sim and also here: >> >> >> >> boards/arm/stm32/stm32f4discovery/src/stm32_hciuart.c >> >> >> >> BR, >> >> >> >> Alan >> >> >> >> On 10/13/22, Embedded Systems wrote: >> >> > Hello Alan, >> >> > >> >> > Its good to hear from you too. >> >> > >> >> > So, you don't to flash NuttX inside Anna-B112, but just want to use >> >> > it >> >> > as external BT BLE module, right? >> >> > >> >> > The Anna module is flashed with u-blox connect and we are using it >> >> > as >> >> > external ble module, the module has the whole ble stack embedded in >> the >> >> > u-box connect and is controlled via AT commands, thats why i am not >> >> > sure >> >> > how exactly to port it for Nuttx in a suitable way. >> >> > >> >> > Best regars, >> >> > Ivan ucherdzhiev >> >> > >> >> > >> >> > На чт, 13.10.2022 г., 18:31 Alan C. Assis >> >> > написа: >> >> > >> >> >> Hi Ivan, >> >> >> >> >> >> Nice to hear news from you! >> >> >> >> >> >> So, you don't to flash NuttX inside Anna-B112, but just want to use >> it >> >> >> as external BT BLE module, right? >> >> >> >> >> >> In this case you need to enable the "Bluetooth H4 UART" >> >> >> >> >> >> There are some examples on NuttX about how to use it. >> >> >> >> >> >> Also you can opt for using NuttX internal BLE Stack (that derives >> from >> >> >> an old BLE Stack that Intel integrated on Zephyr and that was >> released >> >> >> for Arduino/Genuino under BSD License) or you can use the NimBLE >> stack >> >> >> that is more complete and also have examples on NuttX. >> >> >&
Re: Anna-b112 Bluetooth module support
Hi Ivan, Ok, understood the issue! Maybe U-Block has an HCI H4 firmware that you can use on Anna-B112 instead of this AT firmware. It's always a good idea to use and follow the standard, this is a compelling motivation to use NuttX in the first place! :-) BR, Alan On 10/14/22, Embedded Systems wrote: > Hello Alan, > > Unfortunately we cannot use the module as HCI H4, we can control it only > with AT commands. So in our case IMXRT is running nuttx and its connected > to the BLE module with uart and control it with AT commands, so far i just > implemented an application in nuttx which controls the module from the user > space. The aplication is using a UART char driver to communicate with the > module and everything else is managed in the application , but i dont think > this is a good way to use the module and i wish to make a driver in nuttx > for it, My problem is that i dont see a good way to implement the driver > and connect it with the already existing nuttx Bluetooth functionalities . > > > Best regards, > Ivan > > On Thu, Oct 13, 2022 at 11:59 PM Alan C. Assis wrote: > >> Hi Ivan, >> >> Normally using external BLE modules that follows the HCI H4 is easier >> than porting to some chip with internal BLE and application in the >> same chip. >> >> You can see how it is done in the sim and also here: >> >> boards/arm/stm32/stm32f4discovery/src/stm32_hciuart.c >> >> BR, >> >> Alan >> >> On 10/13/22, Embedded Systems wrote: >> > Hello Alan, >> > >> > Its good to hear from you too. >> > >> > So, you don't to flash NuttX inside Anna-B112, but just want to use it >> > as external BT BLE module, right? >> > >> > The Anna module is flashed with u-blox connect and we are using it as >> > external ble module, the module has the whole ble stack embedded in the >> > u-box connect and is controlled via AT commands, thats why i am not >> > sure >> > how exactly to port it for Nuttx in a suitable way. >> > >> > Best regars, >> > Ivan ucherdzhiev >> > >> > >> > На чт, 13.10.2022 г., 18:31 Alan C. Assis написа: >> > >> >> Hi Ivan, >> >> >> >> Nice to hear news from you! >> >> >> >> So, you don't to flash NuttX inside Anna-B112, but just want to use it >> >> as external BT BLE module, right? >> >> >> >> In this case you need to enable the "Bluetooth H4 UART" >> >> >> >> There are some examples on NuttX about how to use it. >> >> >> >> Also you can opt for using NuttX internal BLE Stack (that derives from >> >> an old BLE Stack that Intel integrated on Zephyr and that was released >> >> for Arduino/Genuino under BSD License) or you can use the NimBLE stack >> >> that is more complete and also have examples on NuttX. >> >> >> >> Using the internal stack could be more challenging, but it will help >> >> to improve our own stack. >> >> >> >> BR, >> >> >> >> Alan >> >> >> >> On 10/13/22, Embedded Systems wrote: >> >> > Hello Nuttx Community, >> >> > >> >> > First i would like to say that i really hope that everybody is doing >> >> well! >> >> > I am sorry that long time i didn't had a chance to contribute >> anything, >> >> but >> >> > life is moving in a very fast pace for me lately. >> >> > >> >> > For our sport Wearable system i am working on integration of a >> >> > Bluetooth >> >> > module Anna-B112, it is a very interesting small module. The version >> >> which >> >> > we are using is preflashed with Ublox u-connect software and the >> module >> >> is >> >> > based on nRF52832 nordic chip. I would like to ask for advice on how >> >> > exactly to implement a relevant support for this to suit Nuttx >> >> architecture >> >> > because i wish to contribute this port when its done. I am familiar >> >> > that >> >> > Nuttx has Bluetooth stack and also support for HCI bluetooth >> >> > modules, >> >> > but >> >> > the difference here is that ANNA-B112 has its stack embedder in the >> >> nordic >> >> > chip and the module is controlled via AT commands through UART, so i >> am >> >> not >> >> > exactly sure how to implement the driver for this module. To me it >> >> > looks >> >> > like it has to bypass the nuttx bluetooth stack (because it already >> has >> >> an >> >> > embedded one) and directly connect to the application layer, please >> >> correct >> >> > me if i am wrong here. >> >> > >> >> > I would really appreciate some insight of how exactly to implement >> >> > the >> >> port >> >> > to suit Nuttx design and to NOT disrupt in any way the already >> existing >> >> > implementations of bluetooth connectivity >> >> > >> >> > Thank you in advance! >> >> > >> >> > -- >> >> > Kind regards, >> >> > Ivan Ucherdzhiev >> >> > >> >> > CTO @ Barin Sports >> >> > Bulgaria >> >> > >> >> >> > >> > > > -- > Kind regards, > Ivan Ucherdzhiev > > Team Lead @ Barin Sports > Bulgaria > skype: ipy_44 > tel: +359888927760 >
Re: Anna-b112 Bluetooth module support
Hi Ivan, Normally using external BLE modules that follows the HCI H4 is easier than porting to some chip with internal BLE and application in the same chip. You can see how it is done in the sim and also here: boards/arm/stm32/stm32f4discovery/src/stm32_hciuart.c BR, Alan On 10/13/22, Embedded Systems wrote: > Hello Alan, > > Its good to hear from you too. > > So, you don't to flash NuttX inside Anna-B112, but just want to use it > as external BT BLE module, right? > > The Anna module is flashed with u-blox connect and we are using it as > external ble module, the module has the whole ble stack embedded in the > u-box connect and is controlled via AT commands, thats why i am not sure > how exactly to port it for Nuttx in a suitable way. > > Best regars, > Ivan ucherdzhiev > > > На чт, 13.10.2022 г., 18:31 Alan C. Assis написа: > >> Hi Ivan, >> >> Nice to hear news from you! >> >> So, you don't to flash NuttX inside Anna-B112, but just want to use it >> as external BT BLE module, right? >> >> In this case you need to enable the "Bluetooth H4 UART" >> >> There are some examples on NuttX about how to use it. >> >> Also you can opt for using NuttX internal BLE Stack (that derives from >> an old BLE Stack that Intel integrated on Zephyr and that was released >> for Arduino/Genuino under BSD License) or you can use the NimBLE stack >> that is more complete and also have examples on NuttX. >> >> Using the internal stack could be more challenging, but it will help >> to improve our own stack. >> >> BR, >> >> Alan >> >> On 10/13/22, Embedded Systems wrote: >> > Hello Nuttx Community, >> > >> > First i would like to say that i really hope that everybody is doing >> well! >> > I am sorry that long time i didn't had a chance to contribute anything, >> but >> > life is moving in a very fast pace for me lately. >> > >> > For our sport Wearable system i am working on integration of a >> > Bluetooth >> > module Anna-B112, it is a very interesting small module. The version >> which >> > we are using is preflashed with Ublox u-connect software and the module >> is >> > based on nRF52832 nordic chip. I would like to ask for advice on how >> > exactly to implement a relevant support for this to suit Nuttx >> architecture >> > because i wish to contribute this port when its done. I am familiar >> > that >> > Nuttx has Bluetooth stack and also support for HCI bluetooth modules, >> > but >> > the difference here is that ANNA-B112 has its stack embedder in the >> nordic >> > chip and the module is controlled via AT commands through UART, so i am >> not >> > exactly sure how to implement the driver for this module. To me it >> > looks >> > like it has to bypass the nuttx bluetooth stack (because it already has >> an >> > embedded one) and directly connect to the application layer, please >> correct >> > me if i am wrong here. >> > >> > I would really appreciate some insight of how exactly to implement the >> port >> > to suit Nuttx design and to NOT disrupt in any way the already existing >> > implementations of bluetooth connectivity >> > >> > Thank you in advance! >> > >> > -- >> > Kind regards, >> > Ivan Ucherdzhiev >> > >> > CTO @ Barin Sports >> > Bulgaria >> > >> >
Re: simulation spi driver
Hi Prelude, It is using on boards/arm/sam34/arduino-due What issue are you facing? On 10/13/22, Prelude wrote: > Have any friends done gpio simulation spi on Nuttx？ > > > > >
Re: Anna-b112 Bluetooth module support
Hi Ivan, Nice to hear news from you! So, you don't to flash NuttX inside Anna-B112, but just want to use it as external BT BLE module, right? In this case you need to enable the "Bluetooth H4 UART" There are some examples on NuttX about how to use it. Also you can opt for using NuttX internal BLE Stack (that derives from an old BLE Stack that Intel integrated on Zephyr and that was released for Arduino/Genuino under BSD License) or you can use the NimBLE stack that is more complete and also have examples on NuttX. Using the internal stack could be more challenging, but it will help to improve our own stack. BR, Alan On 10/13/22, Embedded Systems wrote: > Hello Nuttx Community, > > First i would like to say that i really hope that everybody is doing well! > I am sorry that long time i didn't had a chance to contribute anything, but > life is moving in a very fast pace for me lately. > > For our sport Wearable system i am working on integration of a Bluetooth > module Anna-B112, it is a very interesting small module. The version which > we are using is preflashed with Ublox u-connect software and the module is > based on nRF52832 nordic chip. I would like to ask for advice on how > exactly to implement a relevant support for this to suit Nuttx architecture > because i wish to contribute this port when its done. I am familiar that > Nuttx has Bluetooth stack and also support for HCI bluetooth modules, but > the difference here is that ANNA-B112 has its stack embedder in the nordic > chip and the module is controlled via AT commands through UART, so i am not > exactly sure how to implement the driver for this module. To me it looks > like it has to bypass the nuttx bluetooth stack (because it already has an > embedded one) and directly connect to the application layer, please correct > me if i am wrong here. > > I would really appreciate some insight of how exactly to implement the port > to suit Nuttx design and to NOT disrupt in any way the already existing > implementations of bluetooth connectivity > > Thank you in advance! > > -- > Kind regards, > Ivan Ucherdzhiev > > CTO @ Barin Sports > Bulgaria >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hi Mike, Thank you very much for your fast reply. I'm CC our mailing list (I hope you don't get angry with me) because your words are really inspiring for everyone here! Case you find your initial M68K port please let us know! I think it should be a nice achievement for NuttX to retro-computing community. We are missing you! You was always prone to help everyone and your level of knowledge is remarkable, I learned a lot from you! BR, Alan On 10/12/22, Mike Smith wrote: > G'day Alan, > > I worked on a port to the 68k a while back, but it stalled for various > reasons; real work got in the way, and I recall at least one technical issue > related to interrupt / exception handling (likely surmountable, but I don't > remember the details). > > As you see, I'm still contactable 8) but as Greg notes I had to put my > involvement with NuttX (and many other things) on hold in order to focus on > paying work. Regrettable. 8( > > I did a little digging around, but I haven't been able to locate the working > copy. If I do I'll pass it along, but it wasn't anything revolutionary and > could probably be replicated in a couple of days - especially with the > emulation options now available. > > As an aside, the current state of NuttX is simply remarkable. I haven't had > time to look at the community, but the continued growth and maturity of the > code is an inspiration, and I have used it as an example to other teams more > than once. Whatever the community is doing, it certainly looks like it > works. 8) > > Regards, > > = Mike > >> On Oct 10, 2022, at 4:24 PM, Alan C. Assis wrote: >> >> Hi Mike, >> >> How are you? >> >> Greg commented about you today, he said you did the NuttX port to Motorola >> 68k ! >> >> Is that true? If so, could you share it and we'll clean-up and upstream >> it. >> >> BR, >> >> Alan >> >> -- Forwarded message -- >> From: Gregory Nutt >> Date: Mon, 10 Oct 2022 16:49:26 -0600 >> Subject: Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2] >> To: dev@nuttx.apache.org >> >> Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if >> he >> completed it or not, but the port never came upstream. Mike is no longer >> involved with NuttX and probably not contactable. If anyone out there in >> PX4 land knows where Mike kept his code, that might be helpful. >> >> >> >> A port to one of the WDC 65xx parts would also be interesting: >> https://www.westerndesigncenter.com/ >> >> >> >> On Mon, Oct 10, 2022 at 4:12 PM Sebastien Lorquet >> wrote: >> >>> Hi, >>> >>> If you want to play with 68k, tell me, the ti68k calculators >>> (ti89,92+,v200,titanium) should be great platforms: 256K RAM and 2-4M >>> flash, full keyboard and lcd screen. >>> >>> They have some peculiarities, I could help with drivers or find friends >>> that could. >>> >>> The cemetech/tiplanet communities should like it. >>> >>> Sebastien >>> >>> On 10/8/22 18:06, Tomek CEDRO wrote: >>>> On Sat, Oct 8, 2022 at 4:58 PM Alan C. Assis wrote: >>>>> Hi Tomek, >>>>> I think 6502 compiler are evolving, but I don't know if they are >>> compatible. >>>>> There is a interesting comparison here: >>>>> https://gglabs.us/node/2293 >>>>> CC. Gabriele here, since I don't know if here is in our list! >>>> Thank you Alan :-) 8-bit platforms are on list, but before I would >>>> like to make smooth out-of-the box experience with NuttX on FreeBSD, >>>> then port MicroPython to NuttX, then as a training in porting I would >>>> prefer to target 16-bit MC68000 in the first place (Atari + Amiga), >>>> then 8-bit Atari, in that order, and all of that in my free time >>>> between other tasks, so there is no rush :-) >>>> >>> > >
Re: Unicode characters in codebase.
Agree! It is better to avoid it. On 10/10/22, Fotis Panagiotopoulos wrote: > Hello! > > A few weeks ago I had some problems with a static analysis tool that > couldn't parse NuttX code, due to non-Unicode characters. I provided a > couple of PRs and fixed the issues, but it got me thinking... > > Do we really need Unicode characters within the codebase? > > I can only think of problems with this, from missing glyphs from fonts, to > difficulties in search... > I don't see any value in writing μs instead of us, or I²C instead of I2C. > > What do you think? > Shall we allow such characters, or enforce ASCII-only characters in the > codebase? >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Fixed email! On 10/8/22, Alan C. Assis wrote: > Hi Tomek, > > I think 6502 compiler are evolving, but I don't know if they are > compatible. > > There is a interesting comparison here: > > https://gglabs.us/node/2293 > > CC. Gabriele here, since I don't know if here is in our list! > > BR, > > Alan > > On 10/8/22, Tomek CEDRO wrote: >> By the way, I also found some tools for MOS6502 in the ports tree :-) >> >> # make quicksearch key="6502" >> Port: acme-0.97.r319,1 >> Path: /usr/ports/devel/acme >> Info: Crossassembler for 6502, 65c02 and 65816 processors >> >> Port: cc65-2.19 >> Path: /usr/ports/devel/cc65 >> Info: Cross-compiler for 6502-based systems >> >> Port: dxa65-0.1.4 >> Path: /usr/ports/devel/dxa65 >> Info: Disassembler for MOS 6502 and compatible CPUs >> >> Port: vasm-1.8c >> Path: /usr/ports/devel/vasm >> Info: Portable 6502 6800 arm c16x jagrisc m68k ppc vidcore x86 z80 >> assembler >> >> Port: xa65-2.3.11 >> Path: /usr/ports/devel/xa65 >> Info: Two-pass cross-assembler for MOS 6502 and compatible CPUs >> >> Port: p5-Acme-6502-0.77_2 >> Path: /usr/ports/emulators/p5-Acme-6502 >> Info: Pure Perl 65C02 simulator >> >> Port: nesasm-20040314_1 >> Path: /usr/ports/lang/nesasm >> Info: 6502 assembler with specific NES support >> >> >> Not sure about dedicated toolchain for MC68000 (16-bit Atari and >> Amiga) if there needs to be one or generic compiler can cross compile >> that target.. but I will know that in some time as I have both Amiga >> 600 and Atari ST Mega1 :-) >> >> Best regards :-) >> Tomek >> >> >> On Sat, Oct 8, 2022 at 3:15 PM Tomek CEDRO wrote: >>> >>> Well, toolchain is another thing on the BSD TODO list :-) You either >>> need to have Espressif toolchain installed and in path or you can >>> provide your own or system toolchain by hand durign build. >>> >>> I am on a trip right now with my backup laptop that is not my main >>> development workstation, sorry, but the summary is below. >>> >>> 1. Because FreeBSD can natively emulate Linux ELF binaries, I did a >>> trick with support of Espressif that allows download and install Linux >>> tools on FreeBSD with ESP-IDF. That works fine.. but it would be >>> perfect to build and distribute also toolchain binaries for FreeBSD by >>> Espressif. So far I have used ESP IDF Linux tools on FreeBSD for >>> initial experiments on ESP32 and ESP32-C3. >>> >>> % uname -a >>> FreeBSD 0xCFMX4 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64 >>> >>> % ls -1 ~/.espressif/tools >>> esp32s2ulp-elf >>> esp32ulp-elf >>> openocd-esp32 >>> riscv32-esp-elf >>> xtensa-esp32-elf >>> xtensa-esp32s2-elf >>> xtensa-esp32s3-elf >>> >>> That gives: >>> >>> % ./xtensa-esp32-elf-gcc -v >>> Using built-in specs. >>> COLLECT_GCC=./xtensa-esp32-elf-gcc >>> COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper >>> Target: xtensa-esp32-elf >>> Configured with: >>> /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure >>> --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu >>> --target=xtensa-esp32-elf >>> --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf >>> --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf >>> --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include >>> --with-newlib --enable-threads=no --disable-shared >>> --with-pkgversion='crosstool-NG esp-2021r2' --disable-__cxa_atexit >>> --enable-cxx-flags=-ffunction-sections --disable-libgomp >>> --disable-libmudflap --disable-libmpx --disable-libssp >>> --disable-libquadmath --disable-libquadmath-support >>> --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --enable-lto --enable-target-optspace --without-long-double-128 >>> --disable-nls --enable-multiarch --enable-languages=c,c++ >>> --disable-libstdcxx-verbose --enable-threads=posix >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
oolcahin for >> embedded ARM development >> u-boot-qemu-arm-2022.04_1 Cross-build das u-boot for model qemu-arm >> u-boot-qemu-arm64-2022.04_1Cross-build das u-boot for model >> qemu-arm64 >> u-boot-rpi-arm64-2022.04_1 Cross-build das u-boot for model rpi-arm64 >> >> >> % pkg search powerpc >> powerpc-binutils-2.37_4,1 GNU binary tools >> powerpc-freebsd-sysroot-a2021.11.09 FreeBSD 13.0-RELEASE powerpc sysroot >> powerpc-gcc12-12.1.0 Cross GNU Compiler Collection for powerpc >> powerpc-gcc9-9.5.0 Cross GNU Compiler Collection for powerpc >> powerpc-rust-bootstrap-1.63.0 Create bootstrap compilers for building >> lang/rust >> powerpc64-binutils-2.37_4,1GNU binary tools >> powerpc64-elfv1-freebsd-sysroot-a2021.11.09 FreeBSD 12.2-RELEASE >> powerpc64 elfv1 sysroot >> powerpc64-elfv1-rust-bootstrap-1.63.0 Create bootstrap compilers for >> building lang/rust >> powerpc64-elfv2-freebsd-sysroot-a2021.11.09 FreeBSD 13.0-RELEASE >> powerpc64 elfv2 sysroot >> powerpc64-elfv2-rust-bootstrap-1.63.0 Create bootstrap compilers for >> building lang/rust >> powerpc64-gcc12-12.1.0 Cross GNU Compiler Collection for >> powerpc64 >> powerpc64-gcc6-6.5.0_3 Cross GNU Compiler Collection for >> powerpc64 >> powerpc64-gcc9-9.5.0 Cross GNU Compiler Collection for >> powerpc64 >> powerpc64le-binutils-2.37_4,1 GNU binary tools >> powerpc64le-freebsd-sysroot-a2021.11.09 FreeBSD 13.0-RELEASE powerpc64le >> sysroot >> powerpc64le-rust-bootstrap-1.63.0 Create bootstrap compilers for >> building lang/rust >> >> >> % pkg search avr >> arduino-avrdude-6.3_4 Program for programming the on-chip >> memory of Atmel AVR Arduino CPUs >> avr-binutils-2.37_4,1 GNU binary tools >> avr-gcc-11.2.0 FSF GCC for Atmel AVR 8-bit RISC >> cross-development >> avr-gdb-7.3.1_6GNU GDB for the AVR target >> avr-libc-2.0.0_4,1 C and math library for the Atmel AVR >> controller family >> avra-1.4.2 Macro Assembler for Atmel AVR >> microcontrollers >> avrdude-7.0_2 Program for programming the on-chip >> memory of Atmel AVR CPUs >> simavr-1.7_2 Simulator for several Atmel AVR chips >> >> >> % pkg search z80 >> p5-CPU-Z80-Assembler-2.18 Z80 assembler written in Perl >> z80-asm-2.4.p3 Z80 assembly code assembler and >> disassembler >> z80asm-1.8 Assembler for the Z80 microprocessor >> z80ex-1.1.21 ZiLOG Z80 CPU emulator library >> z80pack-1.37 Complete CP/M-80 emulator >> >> >> % pkg search openocd >> openocd-0.11.0_1 Open On-Chip Debugger >> >> >> And many many more :-) >> >> Best regards :-) >> Tomek >> >> >> >> On Sat, Oct 8, 2022 at 2:33 PM Alan C. Assis wrote: >> > >> > Thank you very much Tomek! >> > >> > when you get NuttX compiled on FreeBSD, please run the similar >> > commands like these: >> > >> > $ xtensa-esp32-elf-gcc -v >> > Using built-in specs. >> > COLLECT_GCC=xtensa-esp32-elf-gcc >> > COLLECT_LTO_WRAPPER=/usr/local/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper >> > Target: xtensa-esp32-elf >> > Configured with: >> > /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure >> > --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu >> > --target=xtensa-esp32-elf >> > --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf >> > --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf >> > --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include >> > --with-newlib --enable-threads=no --disable-shared >> > --with-pkgversion='crosstool-NG esp-2021r2-patch3' >> > --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections >> > --disable-libgomp --disable-libmudflap --disable-libmpx >> > --disable-libssp --disable-libquadmath --disable-libquadmath-support >> > --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> > --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> > --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> > --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> > --enable-lto --enable-target-optspace --without-long-
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Thank you very much Tomek! when you get NuttX compiled on FreeBSD, please run the similar commands like these: $ xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=xtensa-esp32-elf-gcc COLLECT_LTO_WRAPPER=/usr/local/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper Target: xtensa-esp32-elf Configured with: /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include --with-newlib --enable-threads=no --disable-shared --with-pkgversion='crosstool-NG esp-2021r2-patch3' --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --enable-lto --enable-target-optspace --without-long-double-128 --disable-nls --enable-multiarch --enable-languages=c,c++ --disable-libstdcxx-verbose --enable-threads=posix --enable-gcov-custom-rtio --enable-libstdcxx-time=yes Thread model: posix gcc version 8.4.0 (crosstool-NG esp-2021r2-patch3) If you send just the last line above it fine, we only need to know the toolchain version and characteristic. $ xtensa-esp32-elf-size nuttx textdata bss dec hex filename 75231 3207736 83287 14557 nuttx BR, Alan On 10/8/22, Tomek CEDRO wrote: > Hey there Alan :-) > > I am working on FreeBSD / BSD: > 1. kconfig-frontends is now in the FreeBSD ports and packages. > 2. I need to fix the SEDvsGSED issue. > 3. Have some ideas on how to unify MAKEvsGMAKE. > 4. KConfig work to add BSD also needs to be done. > 5. All 2 to 4 would point to GNUvsBSD build tools unification so > things work out of the box on both GNU and BSD in the same way with no > local modifications. > > This is not yet into this release, but lots of other work is done, and > this seems to be a release that others also wait to go out in order to > add their patches.. thus +1 from me not to block the works.. otherwise > no rush from me as things are done when they are done :-) > > Best regards :-) > Tomek > > > > > > On Sat, Oct 8, 2022 at 1:37 PM Alan C. Assis wrote: >> >> Hi everyone, >> >> As suggestion when voting for a new release, please send together the >> information about what compiler was used and the output of your >> toolchain "size". >> >> This is just a suggestion, but help us to know that you really tested >> the release and also it is used as reference to know if the size >> increased too much or if there is some discrepancies between different >> toolchains. >> >> Thank you for understanding. >> >> BR, >> >> Alan >> >> On 10/8/22, Tomek CEDRO wrote: >> > +1 from me :-) >> > >> > -- >> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >> > > > > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hi everyone, As suggestion when voting for a new release, please send together the information about what compiler was used and the output of your toolchain "size". This is just a suggestion, but help us to know that you really tested the release and also it is used as reference to know if the size increased too much or if there is some discrepancies between different toolchains. Thank you for understanding. BR, Alan On 10/8/22, Tomek CEDRO wrote: > +1 from me :-) > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Correction!!! Re: Embedded World Conference 2023
Today is the last day to submit your Abstract! So, you need to run fast, but the process is simple! Good luck! I just submitted mine! BR, Alan On 10/7/22, Alan C. Assis wrote: > Hi Everyone, > > Tomorrow is the last day to submit proposal: > > https://events.weka-fachmedien.de/embedded-world-conference/home/ > > Please use this opportunity to let more people discover about our amazing > RTOS! > > Let's do it! > > BR, > > Alan >
Embedded World Conference 2023
Hi Everyone, Tomorrow is the last day to submit proposal: https://events.weka-fachmedien.de/embedded-world-conference/home/ Please use this opportunity to let more people discover about our amazing RTOS! Let's do it! BR, Alan
Re: NxWidgets
Hi Victor, Please see page 43 to see some nice interfaces developed using NXWidgets: https://web.archive.org/web/20161019222034/http://dspace.cc.tut.fi/dpub/bitstream/handle/123456789/22051/Aimonen.pdf You can look the NXWM to see some examples of screens using NXWidgets. BR, Alan On Tuesday, October 4, 2022, Victor Suarez Rovere wrote: > > Hi > I'm interested on trying some UI code. NxWidgets seems quite interesting > but I haven't seen any screenshot besides a terminal (that uses no > widgets). Is there any more complex application por demo, or at least some > screenshots? > > Regards, > Víctor
NuttX Wikipedia entry vandalized
Hi Eveyone, I went to Wikipedia to get a link to show Victor about nice project using NXWidgets and NXWM, but I noticed the page is "completely" empty. Just look the history and click on October 2021 to see the difference. BR, Alan
Re: How to use the esp8266 network module？
Hi Prelude, There is not documentation to it yet, it was contributed many years ago. Please helps to improve NuttX, if you get it working, submit a documentation over github PR. Important note, that esp8266 integration is not using USRSOCK, so it is not the right way to do it. BR, Alan On 9/29/22, Prelude wrote: > I saw the code of esp8266 in the directory apps/netutils/esp8266, but there > is no test case. How can I test esp8266 using the UART? > >
Re: NXTerm with USB console
I was refering to ALT CONSOLE, it could be used to any other device. Not only SLCD :-) Maybe it was removed because now there is another alternative to Alternative Console, hehehe. I need to check. On 9/27/22, Jernej Turnsek wrote: > Hi Alan, > > what do you mean about someone removing the nsh console. It is still in > apps repo. Your video was actually using a different slcd console which is > available for alphanumeric lcd displays. > > Regards, > Jernej > > On Tue, Sep 27, 2022 at 3:05 PM Alan C. Assis wrote: > >> Hi Jernej, >> >> NSH used to be an Alternative Console, but I think someone removed it >> few months ago, probably now my video tutorial explaning show to put >> the NSH terminal in a matrix display will not work see: >> >> https://www.youtube.com/watch?v=4za1lhfsct8 >> >> Maybe someone who removed it could help us :-) >> >> BR, >> >> Alan >> >> On 9/27/22, Jernej Turnsek wrote: >> > Hi, >> > >> > I have enabled nxterm functionality on my board with a 400x240 display >> and >> > I am using an USB console. When starting nxterm example in nsh, I am >> seeing >> > the nxterm booting and setting the display, but when it should redirect >> > stdout to nxterm, it doesn't. I am still in USB console. Looking the >> code I >> > see that nsh_consolemain function is called from nsh_usbconsole.c, >> because >> > of USB console set in KConfig. Later it is calling nsh_configstdio >> > which >> > duplicates stdio again and I think this is the reason for nxterm stdout >> not >> > working. How can I get around this problem? >> > >> > Thanks, >> > Jernej >> > >> >
Re: NXTerm with USB console
Hi Jernej, NSH used to be an Alternative Console, but I think someone removed it few months ago, probably now my video tutorial explaning show to put the NSH terminal in a matrix display will not work see: https://www.youtube.com/watch?v=4za1lhfsct8 Maybe someone who removed it could help us :-) BR, Alan On 9/27/22, Jernej Turnsek wrote: > Hi, > > I have enabled nxterm functionality on my board with a 400x240 display and > I am using an USB console. When starting nxterm example in nsh, I am seeing > the nxterm booting and setting the display, but when it should redirect > stdout to nxterm, it doesn't. I am still in USB console. Looking the code I > see that nsh_consolemain function is called from nsh_usbconsole.c, because > of USB console set in KConfig. Later it is calling nsh_configstdio which > duplicates stdio again and I think this is the reason for nxterm stdout not > working. How can I get around this problem? > > Thanks, > Jernej >
Re: New UNUSED macro not working
Hi Jernej, There is a discussion about it here: https://github.com/apache/incubator-nuttx/pull/6779 The issue with previous implementation was it only worked for integers variable. BR, Alan On 9/27/22, Jernej Turnsek wrote: > Hi, > > when compiling LuaJIT on NuttX with new UNUSED macro I get following error: > > LuaJIT/src/lj_frame.h:70:61: error: lvalue required as unary '&' operand >70 | #define setframe_gc(f, p, tp) (setgcref((f)->fr.func, (p)), > UNUSED(tp)) > > What was the reason to change UNUSED macro from: > > # define UNUSED(a) ((void)(1 || (a))) > > to > > # define UNUSED(a) ((void)(1 || &(a))) > > Thanks, > Jernej >
Re: GESO: AEROBATICS in PHALABORWA
Thanks, Larry. By Jove, you're right about the passenger. Alan C On 25-Sep-22 09:09 PM, Larry Colen wrote: On Sep 25, 2022, at 8:41 AM, Alan C wrote: A group of Aerobatic Pilots graced our skies from Wed. until this morning. Solo & Formation stuff. Rather warm for flying at midday but ideal early & late. Ideal venue for practicing. We could see most of the action from our house. I took a few shots - here are 2: https://www.flickr.com/photos/wisselstroom/52383382418/ Very cool. It looks like the blue plane has a passenger. K5 & HD 55-300 @ 300 Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- Larry Colen l...@red4est.com -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
GESO: AEROBATICS in PHALABORWA
A group of Aerobatic Pilots graced our skies from Wed. until this morning. Solo & Formation stuff. Rather warm for flying at midday but ideal early & late. Ideal venue for practicing. We could see most of the action from our house. I took a few shots - here are 2: https://www.flickr.com/photos/wisselstroom/52383382418/ K5 & HD 55-300 @ 300 Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
NuttX Workshop Youtube link
Hi Everyone, Please find the link to the NuttX Workshop here: https://www.youtube.com/watch?v=I-msubvN3Nw BR. Alan
NuttX International Workshop 2022: will start in less than 14h
Hi Everyone, We are looking forward to see you tomorrow in the NuttX Workshop. The schedule with all the presentations is already available: https://nuttx.events/ BR, Alan
Re: Design by Hotblack Desioto
HORRIBLE. Alan C On 21-Sep-22 12:46 PM, Henk Terhell wrote: https://us.ricoh-imaging.com/product/pentax-k-3-mark-iii-jet-black-edition-body-kit/?mc_cid=d4644d40d8 Op di 20 sep. 2022 om 23:46 schreef : Sounds great off you want to photograph a disaster area concert The K-3 Mark III JET BLACK Edition is a limited-edition, special design model that has all the features and specs of the standard K-3 Mark III in a sleek all-black finish. With its unique monochromatic design, the PENTAX logo, SR logo and indicators on the mode dial are in black, while the K-3 Mark III logo and operation parts, such as the markings on 4-way key on the back of the camera body are in charcoal black. This color allows the markings to remain inconspicuous but can be easily seen by adjusting the light. By paying close attention to details, the K-3 Mark III JET BLACK Edition is a true black body that blends into the darkness yet stands out in the crowd. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: imxrt1176 on Nuttx
Hi Prelude, I think imxrt1176 is not available yet, did you get it? Probably the peripherals will be the same. BTW: did you test the W5500? BR, Alan On Wednesday, September 21, 2022, prelude wrote: > I want to ask my friends, is there anyone who supports imxrt1176 on > Nuttx？At present, there are only imxrt1020, imxrt1050, imxrt1060 and > imxrt1064 in the Nuttx code. > > >
Re: Geso:Annual Motorfest car show
Thank's Dave. Enjoyed tat lot. Many memories from long ago. Alan C On 11-Sep-22 03:55 PM, David J Brooks wrote: Saturday was the annual big get together at Memorial park and did my yearly wander around. About 62 slides http://www.caughtinmotion.com/2022-motorfest/album/index.html D7200 18-70 some LR6 minor exposure edits Dave B -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
PESO: Speaking of Heat Waves
Over the last 3 days, Phalaborwa has suffered temps. in the high 30's, peaking at 38°C today - very high for springtime. I hate to think what we may be in store this summer. https://www.flickr.com/photos/wisselstroom/52349942884/ K5 & HD 18-55 WR The Limpopo Provincial Aerobatic Champs. was scheduled here this weekend but only about 6 planes turned up. The whole thing seems to have fizzled out & most already left yesterday. We were able to watch a bit of early morning aerobatics from our house about a Km away but that was it. Most disappointing. Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: September PUG is up (yes, really!)
I had nothing suitable for the Sept. PUG except, perhaps, this one - taken in 2012 before I had acquired a Pentax digital body. I was using my old Pentax lenses with Big-Is EMF adapters on a Canon 1000D body. Worked very well, but all manual. This one is at full stretch with the FA100-300. https://www.flickr.com/photos/wisselstroom/52340551481/ Alan C On 07-Sep-22 09:12 AM, Ralf R Radermacher wrote: Am 07.09.22 um 05:47 schrieb Alan C: Nope. It is here, after a refresh. But my photo is still missing. Ralf -- Ralf R. Radermacher - Köln/Cologne, Germany Blog : http://the-real-fotoralf.blogspot.com Audio : http://aporee.org/maps/projects/fotoralf Web : http://www.fotoralf.de -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Heat wave
Welcome to Phalaborwa. We turn on the heaters when it goes under 40°C! Alan C On 07-Sep-22 02:25 AM, John Francis wrote: On Tue, Sep 06, 2022 at 11:50:57PM +0100, Steve Cottrell wrote: Here, down to a balmy 21 or so daytime, big fat low revolving over us dumping good amounts of rain. The grass has lost the bright yellow glow and patches of green are returning. Rain til the weekend. Happier days. Cot What is this grass of which you speak? :-) I stopped watering the grass several years ago when it became painfully obvious that: 1) California didn't have enough water to meet existing requirements, let alone the increases expected from population growth. 2) It was extremely unlikely that California would be able to get the votes required to change the allocation system, so there was no way to prevent long-established agriculture, etc., having first rights to take as much water as they wanted to grow crops; there wasn't even a way to require efficient irrigation systems (too expensive) or to prevent crops such as almonds (or even hay) being exported. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: September PUG is up (yes, really!)
Nope. Alan C On 07-Sep-22 01:07 AM, Brian W wrote: The September PUG is now back at the main link: http://pug.komkon.org/ Cheers Brian -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: SD woes
Rick, I think Godfrey may well be on to the problem. The card contacts in the camera may be a bit grimy. Plastering an SS card with one of those electronic cleaning agents (Like Spanjaard LektroKleen) & putting it in and out a few times may help. I have solved USB contact problems like that. Alan C On 04-Sep-22 09:23 PM, Rick Womer wrote: Progress so far: - Tested all 4 SD cards. One occasionally lost its connection to the camera when I wiggled it, and another seemed to fit loosely in the slot and its connection seemed unreliable. I threw them away and ordered 4 new cards from B Rick On Sep 4, 2022, at 12:58 PM, John Francis wrote: On Sun, Sep 04, 2022 at 11:01:30AM -0400, Rick Womer wrote: Last spring we took a walk in Morris Arboretum, where the spring blossoms offered lots of photographic fodder. Alas, when I got home, the card had thumbnail JPGs on it, but no DNG files. As usual I erased the card (SanDisk Extreme Pro) in the camera after transferring the files to my computer. Last week we toured Winterthur, a beautiful DuPont estate about an hour away. Again I took about a hundred photos. When i put the SD card into the reader, I got a screen full of thumbnails from Winterthur and the flea market in the parik a couple of weeks ago, all stirred together (even though the card had been erased). No DNGs. I have four SD cards, of which three were indistinguishable until I numbered them yesterday. I checked each of them with the Mac Disk Utility, and they all passed. Any ideas apart from buying a new set of cards? Is there any way to distinguish a card failure from a camera failure? Rick The most obvious reason for a perfectly readable card to contain only JPGs, no DNGs, is that the camera has somehow got set to only write JPGs. I assume you checked that, but ... (Or, depending on which camera body you have, to write JPGs to one card, and DNGs to a different card) -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PESO Darter
Amazing shot, Toine. I was expecting to see a bird! Alan C On 04-Sep-22 07:49 PM, Toine wrote: The common darter. As a couple in flight and depositing eggs. You can spot the next egg on madam darter on the right. https://repiuk.nl/new/#pid=_1005734-Edit.jpg One of the same species posing for the paparazzi https://repiuk.nl/new/#pid=_1005747.jpg I installed a new CMS (X3) for my website. All older links are now broken. I used the Koken CMS for many years but Koken is no more, no updates resulted in a major crash. Long live X3 https://www.photo.gallery/ Toine -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Out, out, dan spot!
Refraction? https://photographylife.com/what-is-diffraction-in-photography Alan C On 28-Aug-22 02:21 PM, coll...@brendemuehl.net wrote: If at f/18 there’s a soft shadows spot (several) but none at f/5.6 then I’m wondering about sensors. Seems to be a common situation. Never had that issue with film. ;-) -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Monitor calibrator question
Late on this. a couple of years go there was some discussion about new software for a Spyder. I recall Toine saying how well it worked. So... if you have a Spyder? Alan C On 24-Aug-22 11:05 PM, Rick Womer wrote: It’s a long story, but I recently bought a new MacBook Pro and external monitor as “work” computers. The colors are ugly, though, and I’d like to calibrate both devices. The problem is that my calibrator is an Xrite i1 Display, which is old enough that there is no longer software available. So, I am shopping for a new calibrator. I’m not feeling fond of Xrite at the moment. What are people’s experiences with the Spyder calibrator (a mere $169)? Rick -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PESO - A day at the races: OT VESO
Very enjoyable, Larry. I look forward to a faster lap (I could knock off a bunch of time)! Perhaps you could consider affixing the Go-Pro to a faster car & getting him to follow you around for lap? Alan C On 27-Aug-22 04:46 PM, l...@red4est.com wrote: This is a slower lap, from Saturday morning. The go pro is mounted in the grill giving a very different view https://youtu.be/INoBryyyS-w On August 26, 2022 10:56:13 AM PDT, Larry Colen wrote: I was playing with a gopro for the first time last weekend. This wasn’t my fastest lap but it starts with an amusing lesson on a premature attmept at a pass. There are a bunch of places that I could knock off a bunch of time by just keeping my foot on the floor and also later and harder braking. Last weekend was my first time on sticky tires in about 15 years, I was last at this track about 8 years ago, and before that about 15 years ago, and it was my first weekend at any track with this car. So, especially with the fun I had the day before with brakes, https://www.youtube.com/watch?v=SGxSUDNwmqQ -- Larry Colen l...@red4est.com. sent from ret4est -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: Pentax 18-250 - stuck in the "locked" zoomed out position
Well done, Igor "Courage" is certainly the word - I buggered up a couple of old lenses trying to repair them blind. Alan C On 26-Aug-22 11:01 PM, Igor PDML-StR wrote: A delayed follow-up: The rubber grip is not glued, and it was much easier to pull it up and fold a half of it over the rest than I was expecting. Tightening the screw fixed the issue completely. It took 2-3 minutes once I had the lens and the right tools (a bamboo splint and a very small Phillips screwdriver) at the same location, and the courage to do it. :-) Cheers, Igor -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PESO Wadden Sea pano
That's what I do except H/H & then I always have to crop a bit top & bottom. Not more than 3 frames in Landscape, but up to 6 in portrait. Alan C On 15-Aug-22 07:49 AM, Toine wrote: Put the camera in manual or AE lock so every shot has the same exposure. Take overlapping shots while rotating in the same spot. Merge the shots as a pano in lightroom or special panorama stitcher software. Most important is to keep the camera level which is easy to do with the level indicators in the viewfinder. Normally I use a monopod to rotate the camera.lens around its optical center. With modern software its very easy to use and produces a seamless stitch On Sun, 14 Aug 2022, 23:54 Rick Womer, wrote: Toine, I agree with the other compliments! Could you please describe the technique briefly? Rick On Aug 11, 2022, at 12:04 PM, Toine wrote: Maybe a little over tweaked in the color department (I like it or remembered it as is). Since this subject doesn't have any straight lines a pano (8 shots portrait handheld, no bracketing or hdr) works perfectly to capture the scenery https://www.repiuk.nl/favorites/#=1=006-750-waddenpano-aug-2022-edit Toine -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: GESO: Spring blossoms
Idiot! All with the K5. First 3 with the FA 100/2.8 Macro, Crassula with the DA 18-55 WR. Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
GESO: Spring blossoms
Well, Spring has arrived in the Lowveld. The birds are going beserk. Already 35°C forecast for Friday but there is certain to be another cold snap yet! Here are 4 early spring blossoms. Scroll as necessary. See the descriptions under the images. A Knoppiesdoorn tree with a few early flowers right at the top, A Camel's foot tree (from the shape of the leaves), A single Coral tree blossom & a Crassula (succulent). https://www.flickr.com/photos/wisselstroom/52269426199/ All with the K5. First 3 with the DA 18-55 WR, others with the FA 100/2.8 Macro Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
[stunnel-users] stunnel to the computer's IP address works, 127.0.0.1 fails
Hi, I setup a newly installed Windows 10 computer with STunnel. The same exact command using the IP address of the computer (eg 192.168.1.xxx) works while 127.0.0.1 fails. The config is set to listen on port only. What could be the problem? Thanks ___ stunnel-users mailing list -- stunnel-users@stunnel.org To unsubscribe send an email to stunnel-users-le...@stunnel.org
Re: quiet
You'll see! Alan C On 31-Jul-22 10:51 PM, Henk Terhell wrote: You mean on the road just for next PUG? Op zo 31 jul. 2022 om 17:00 schreef Alan C : Road Race organising mode. Alan C On 31-Jul-22 04:23 PM, David J Brooks wrote: been pretty quiet since July 27, only 2 pdml emails. Everyone in vacation mode?? Dave B -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions. -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: quiet
Road Race organising mode. Alan C On 31-Jul-22 04:23 PM, David J Brooks wrote: been pretty quiet since July 27, only 2 pdml emails. Everyone in vacation mode?? Dave B -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
OT: LIONS
Karin van Zyl is a member of PENTAX PHOTOGRAPHERS SOUTH AFRICA. Here is a link to a recent photo of hers - A Lioness with 3 cubs at a waterhole. I have posted the link so you can see her submission: https://www.facebook.com/groups/606970746122355/permalink/2289765277842885/ She mostly uses her K5 with a Sigma 170-500 DG. Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: PESO: Bee
Thanks, Rick & Larry. The bee actually crawled right up inside the floret. The difficulty with getting sharp macros is DOF. I used f16 in this case. Perhaps I'll try again at f22 or even f32. Henk T uses stacks with stationary subjects like mushrooms but I haven't tried that yet. Alan C On 18-Jul-22 01:54 AM, Rick Womer wrote: Alan, I like that pic a lot. The composition and colors work very well together. It’s also sharper than my attempts to shoot bees on flowers. Rick On Jul 17, 2022, at 11:24 AM, Alan C wrote: It was cold (by our standards!) with light rain today - then the clouds dispersed & the sun came out. I noticed some bees on the Aloes & decided to try the Macro. This is the pick of the bunch: https://www.flickr.com/photos/wisselstroom/5229446/ K5 & FA 00/2.8 Macro Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
Re: OT: Nikon (and Canon?)
On 16-Jul-22 05:33 PM, Steve Cottrell wrote: Never went back, sadly. Thus initiating the cataclysm of Pentax? Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
PESO: Bee
It was cold (by our standards!) with light rain today - then the clouds dispersed & the sun came out. I noticed some bees on the Aloes & decided to try the Macro. This is the pick of the bunch: https://www.flickr.com/photos/wisselstroom/5229446/ K5 & FA 00/2.8 Macro Alan C -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to pdml-le...@pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
