Re: AVR32 on NuttX

; raman@foo:~/Skullets/nuttxspace/nuttx$ cat >> boards/avr/at32uc3/avr32dev1/src/CMakeLists.txt >> >> set(SRCS avr32_boot.c avr32_bringup.c) >> >> if(CONFIG_BOARDCTL) >> list(APPEND SRCS avr32_appinit.c) >> endif() >> >> if(CONFIG_ARCH_BUTTONS)

Re: AVR32 on NuttX

Hi Raman, On 11/20/23, Raman Gopalan wrote: > Dear Alan, > > I confirm the following settings from the NuttX make menuconfig. RX: PA24, > alternate function 0. TX: PA23, alternate function 0. So, this is correct. > Greg's user manual helped. I just grepped for the definitions. > > I see that the

Re: AVR32 on NuttX

Hi Raman, On 11/20/23, Raman Gopalan wrote: > Dear Alan, Greetings! > > Many thanks for your suggestions. > >> Note that I already adapted it to use your Atmel ICE Device S/N. I just > use: $ >> sudo openocd -f openocd.cfg > > Thank you Alan. I just pasted your openocd configuration and invoked

Re: AVR32 on NuttX

X (FTDI) to J2, pin 10. > 3) TX (FTDI) to J2, pin 7. > > I don't see the nsh shell yet. It is possible the pins are wrong. OR I > suspect > the alternate pin function configuration. I will attack this tomorrow. > > Many thanks again, > > R > > On Sun, 19 Nov 2023 at 2

Re: AVR32 on NuttX

Hi Greg, AFAIK, Mr. Zou (CC here) fixed the Windows/Cygwin build few months ago. We just need to add it in our CI to avoid it breaks again in the feature. Brennan/Petro/Xiang, do you have a machine to add the Windows CI ? Best Regards, Alan On 11/18/23, Gregory Nutt wrote: > AFAIK, the

Re: AVR32 on NuttX

Hi Raman, On 11/19/23, Raman Gopalan wrote: > Dear Alan, Dear Gregory, Greetings! > > Hello Kevin and Zou Boan! > > Many thanks for your suggestions. I will write in detail in a bit but > before, I was too excited about Alan's suggestion. > >> Other option could be extend the CMake support to

Re: AVR32 on NuttX

option is not supported. Let me know >> if this is a problem for you, as it wouldn't be that hard to implement. >> Note that modules are supported -- Kconfiglib just assumes the sy >> mbol name MODULES, like older versions of the C implementation did when >> 'option modules

Re: AVR32 on NuttX

INCDIR="${TOPDIR}\tools\incdir.bat"} > > Has anyone seen this before? Can you please give me a few tips to > tackle this problem? > No, maybe Greg or Zou Boan who were using Windows + Cygwin in the past. >> BTW, if you saw the LED turned ON, it means that proba

Re: AVR32 on NuttX

Hi Raman, Thank you for reviving this discussing (I'm CC NuttX mailing list because it could interest one person or two). On 11/14/23, Raman Gopalan wrote: > Dear Alan, Greetings! > > I trust you're doing so well. I am so sorry about the long pause. I > revisited NuttX again a couple of days

Re: SPI+DMA with ws2812 driver on samd21

Hi Bert, Are you configuring the DMA similar to way he did: https://web.archive.org/web/20221027190645/http://www.lucadavidian.com/2018/03/08/wifi-controlled-neo-pixels-strips/ ? Although on NuttX each driver is a separated instance, under the hook the basic configuration will be similar. BR,

Re: CTU CAN FD driver multi-licence for Nuttx

...@apache.org ? BR, Alan On 11/9/23, Andrew Dennison wrote: > Hi Alan, > > Just confirming you got the suggested request i sent you off-list and that > it didn't end up in spam. > > Thanks, > > Andrew > > > On Sat, Oct 21, 2023, 12:38 AM Alan C. Assis wrote: &g

Re: Trouble adding a new board

Hi Robert, On 11/8/23, Robert Middleton wrote: > Turns out it was a typo in the Kconfig file that took a while to track > down. I don't think that Kconfig has an option to detect errors like > this, which is pretty annoying. > > From boards/Kconfig: > config ARCH_BOARD_STM32_THING_PLUS >

Re: ws2812 on sam

Hi Bert, On 10/30/23, Bert Voldenuit wrote: > Hi Alan, > Thanks for adding Brennan to the discussion. > > My answers below. > > Le lun. 30 oct. 2023 à 16:09, Alan C. Assis a écrit : > >> Hi Bert, >> >> I'm CC Brennan (the original author) and Victor (

Re: ws2812 on sam

Hi Bert, I'm CC Brennan (the original author) and Victor (the author of the other driver using ESP32 RMT) they have more experience with WS2812. On 10/29/23, Bert Voldenuit wrote: > Hi Alan, > > Thanks to your advices, I was able to find why board_ws2812_initialize() > was not in System.map. >

Re: [Article] NuttX on Star64 JH7110: OpenSBI (Supervisor Binary Interface)

Hi Lup, Great work, you are creating a huge set of documentation, not only about NuttX but also about RISC-V, OpenSBI and JH7110 processor! Kudos!!! BR, Alan On 10/28/23, Lee, Lup Yuen wrote: > Bare Metal Programming on a RISC-V SBC (Single-Board Computer) sounds > difficult. Thankfully we

Re: ESP32 I2S audio recording is incomplete

that time. > ____ > From: Alan C. Assis > Sent: Thursday, October 26, 2023 10:55 > To: dev@nuttx.apache.org > Cc: Lucas Vaz > Subject: Re: ESP32 I2S audio recording is incomplete > > [External: This email originated outside Espressif] > > Hi Simona, > &g

Re: ESP32 I2S audio recording is incomplete

t was your mistake, it could help to improve NuttX. BR, Alan On 10/26/23, Simona Toaca wrote: > Yes, ESP32_PSRAM_8M is enabled. > > Regards, > Simona > > În joi, 26 oct. 2023 la 16:55, Alan C. Assis a scris: > >> Hi Simona, >> >> On 10/26/23, Simona T

Re: ESP32 I2S audio recording is incomplete

Hi Simona, On 10/26/23, Simona Toaca wrote: > Hello, > > I want to make sure that I understood this correctly, you're saying that > the I2S audio saved to an SDCard (via SPI) on Lyra T is working ok? > I think that is true. Maybe Lucas can confirm if he was saving in the SDCard. > Also, I

Re: nsh_fileapps and usage of sched_lock()

On 10/25/23, Nathan Hartman wrote: > On Wed, Oct 25, 2023 at 5:16 AM Ville Juven wrote: > >> Hi all, >> >> I noticed that when spawning a new task/process from a file in >> nsh_fileapps, the scheduler is locked prior to calling posix_spawn(), >> which >> does the file loading into memory etc. >>

Re: [VOTE] Apache NuttX 12.3.0 RC1 release

Sorry, I missed the vote window, please find below the results (NuttX still increasing size in a predictable way) ESP32-DEVKITC = $ xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=xtensa-esp32-elf-gcc

Re: STM32 and ttyACM device

Hi Robert, Thanks for sharing your finding! I think the current implementation is more fail safe, but of course, it doesn't fit for all user cases. Some years ago a company created a thermal printer using NuttX and they said when the computer was sending too much data to the printer NuttX was

Re: CTU CAN FD driver multi-licence for Nuttx

; >>> > Can anyone in the project help facilitate an "official" answer from >>> Apache? >>> > >>> > Kind regards, >>> > >>> > Andrew >>> > >>> > PS: the driver authors are not subscribed,

Re: ESP32 I2S audio recording is incomplete

; > Simon > > -- > Ingenieurbüro-Filgis > USt-IdNr.: DE305343278 > -- > sent by mobile phone > > Alan C. Assis schrieb am Do., 19. Okt. 2023, 23:36: > >> Hi Simona, >> >> On 10/19/23, Simona Toaca wrote: >> > Hello, >> > I am t

Re: ESP32 I2S audio recording is incomplete

Hi Simona, On 10/19/23, Simona Toaca wrote: > Hello, > I am trying to record audio using a MEMS microphone, but the final > recording is missing parts periodically (for example, with a sample rate of > 8kHz, there are parts ~1s long missing once every ~10-11s. Using a sample > rate of 48kHz, the

Re: CTU CAN FD driver multi-licence for Nuttx

taking legal advice, on behalf of an apache project, > from a generative language model? > > Sebastien > > > Le 17/10/2023 à 22:22, Alan C. Assis a écrit : >> Oops, it was: you cannot enforce both at same time. >> >> Actually I think I was wrong (not about enforcing)

Re: CTU CAN FD driver multi-licence for Nuttx

ntire project. Consulting with a legal expert is a wise step when dealing with complex licensing issues. " So, we are back to square one! BR, Alan On 10/17/23, Alan C. Assis wrote: > Hi Tomek, > > On 10/17/23, Tomek CEDRO wrote: >>> To be honest I don't see a big issue of

Re: CTU CAN FD driver multi-licence for Nuttx

Hi Tomek, On 10/17/23, Tomek CEDRO wrote: >> To be honest I don't see a big issue of a driver as dual license, we >> already have SocketCAN and other drivers as dual license (GPL and >> Apache, BSD and Apache, etc). The original Author said the want is to >> be released as dual license: A or

Re: CTU CAN FD driver multi-licence for Nuttx

Hi Christofer, On 10/17/23, Christofer Dutz wrote: > Hi all, > > Just came across this thread while reviewing your last board report. > In the PLC4X project we have CAN drivers and we Support C in PLC4C. > However nobody has ported CAN driver to C yet (But thanks to our code > generation it

Re: ESP32 SoftAP - Station bridging

Hi Zhe Weng, Welcome to NuttX mailing list! What a great first message here! It worked perfectly: In the ESP32: nsh> ? help usage: help [-v] [] . cd execkillpwd true [ cp exitls reboot truncate ?

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

That was Alin :-) On 10/16/23, Daniel Appiagyei wrote: > Hi Alan, > Apologies for the delay. Please go ahead and make the RC1. > The issue regards using DMA for UART in (at least) the IMXRT family of > chips. I've created an issue here > and have a

Re: ESP32 SoftAP - Station bridging

Hi Robert, I reproduced your issue here, but I don't know if it is some network issue on NuttX or just because I don't know how to configure the network route correctly. See my board config attached. I tried many scenarios and it never worked: nsh> ? help usage: help [-v] [] .

Re: ws2812 on sam

Hi Bert, On 10/15/23, Bert Voldenuit wrote: > Hello, > > I am trying use ws2812 driver with a samd21 mcu. > > I took example from the /boards/arm/rp2040. > > added to board.h: > #define BOARD_GPIO_WS2812_PIN5 /* verifier pin #5 = PA15 */ > > added to sam_bringup.c: > > #ifdef CONFIG_WS2812 >

Re: execv obsolet ?

; Enviado do meu iPhone > >> Em 12 de out. de 2023, à(s) 18:16, Alan C. Assis >> escreveu: >> >> Hi Greg, >> >>> On 10/12/23, Gregory Nutt wrote: >>> >>>> On 10/12/2023 2:18 PM, Alan C. Assis wrote: >>>> The exe

Re: execv obsolet ?

Hi Greg, On 10/12/23, Gregory Nutt wrote: > > On 10/12/2023 2:18 PM, Alan C. Assis wrote: >> The execv on Linux also fails when we can an builtin program, try it: > > You are right, but the semantics are really confusing. In Bash, > commands that are included inside of

Re: execv obsolet ?

rams that are not internal in NuttShell itself, but compiled separated and executed in the nsh. BR, Alan On 10/12/23, Alan C. Assis wrote: > Ah ok, I tested using the original code with "ls" instead "/bin/ls" > and the result as similar to NuttX: didn't print anything. >

Re: execv obsolet ?

gt; static char * const args[2] = > { > "/bin/ls", > NULL > }; > printf("Executing 1 %s \n", args[0]); > execv(args[0], args); > } > > > De: Al

Re: execv obsolet ?

Hi Miguel, I suggest you to try first in the Linux. NuttX should give you the same result ;-) BR, Alan On 10/12/23, MIGUEL ALEXANDRE WISINTAINER wrote: > Now compiles  > > in theory should show the files got from ls on terminal ? > > Builtin Apps: > i2c sh hellonsh > nsh>

Re: PCF8575 driver for NuttX

Hi David, On 10/6/23, David S. Alessio wrote: >>> In a quick search I noticed that i2c_vbus_initialize() never was part of NuttX, >>> >>> OK, that’s not good. What’s the best way to submit it now? >>> >> >> No idea, I think this function is something you created for your project. >>

Re: PCF8575 driver for NuttX

Hi David, On 10/6/23, David S. Alessio wrote: > >> In a quick search I noticed that i2c_vbus_initialize() never was part >> of NuttX, > > OK, that’s not good. What’s the best way to submit it now? > No idea, I think this function is something you created for your project. How is

Re: PCF8575 driver for NuttX

Hi Gustavo, On 10/6/23, Gustavo Soares wrote: > Hi, Alan and David! > > I'm using nrf52_sx1509.c (at boards/arm/nrf62/thingy52/src) as model for my > driver. I've attached what I have wrote so far and I'd like to know if you > could tell me if I'm at the right direction: >

Re: PCF8575 driver for NuttX

you point me to > how that’s done today? (I’m sure email won’t work). > > The problem I see with the existing IOEXPANDER code is that I don’t believe > it’s thread safe (multiple threads each hammering its own sensor on > different sub buses). > > Cheers, > -david > >

Re: PCF8575 driver for NuttX

Hi David, I think you figure out Gustavo's mistake. Gustavo, all you need to do is use the existing driver. In your code you was trying to implement a low level driver to communicate with your PCF8575. You don't need to do it. Unfortunately there is not much boards examples using IOEXPANDER

Re: [OT] Link to YouTube NuttX Internacional Workshop

for marking all video sections) NuttX International Workshop Day 1: https://www.youtube.com/watch?v=nDLplwggiX4 NuttX International Workshop Day 2: https://www.youtube.com/watch?v=dTzOhl7_kz8 Best Regards, Alan On 9/29/23, Alan C. Assis wrote: > Please link the link below: > > https://www.yo

Re: Writing in an I2C device

Hi Gustavo, On 10/1/23, Gustavo Soares wrote: > Hello everyone! > > I have a PCF8575 IO expander with 16 channels wich I want to use 8 for write > (P10 to P17). The hardware is already configures and all LED's connected to > these ports are on. As you can see, NuttX sees the I2C device: > >

Re: STM Nucleo-32 board - I2C functionality

Hi Stewart, On 9/20/23, Stewart Charnell wrote: > Hi, > > Has anyone used the I2C functionality on the STM Nucleo-32 board (it > uses the STM32L432 processor)? I think there is an issue with the file > boards/arm/stm32l4/nucleo-l432kc/src/stm32_ina226.c. > > This board can support Arduino NANO

Re: fat32 sd-card filesystem broken

Hi Simon, I tested it recently (not extensive test) and it was working fine (stm32f777 meadow board). Did you try to run apps/testing/fstest to push its hard(ware) limits? :-) Also a simple way to verify if FAT is working is creating a RAMDISK (formatted as FAT) and run your application using

Re: riscv64 libm link question

Hi Ken, On 9/18/23, ken.dic...@whidbey.com wrote: > On 2023-09-18 13:08, Alan C. Assis wrote: > >> The thumb rule when starting with NuttX is using an existent >> configuration as base. > > OK. > >> Unfortunately the menuconfig is not prepared (better say it c

Re: Link error building c++ app with master branch

easy way to do JTAG/gdb as you can with other MCU RTOSes, and > there are just so many layers and configurations. > > -m > > On 9/18/2023 4:19 PM, Alan C. Assis wrote: >> Hi Mike, >> >> Let me explain the mental process I follow to fix this kind of error! >> >> The error m

Re: Link error building c++ app with master branch

Hi Mike, Let me explain the mental process I follow to fix this kind of error! The error message in this case is very "clear" undefined reference to `pthread_key_create' So let see where it is defined: $ cd nuttxspace/nuttx $ git grep pthread_key_create ...

Re: riscv64 libm link question

Hi Ken, On 9/18/23, ken.dic...@whidbey.com wrote: > On 2023-09-18 12:05, Alan C. Assis wrote: >> Hi Ken, >> >> Are you enabling the same symbols as in the sim bas or bastest ? > > I just used menuconfig interpreters bas selection > > Raspian:Ra

Re: UARTs ttyS and esp32

Please open arch/xtensa/src/esp32/esp32_serial.c and search for uart_register() function. Notice that it is wrapped by some #ifdef, that need to be satisfied to that function be called. Also if you enter inside boards/xtensa and "git grep UART1" or UART2 you will find some board configuration

Re: riscv64 libm link question

Hi Ken, Are you enabling the same symbols as in the sim bas or bastest ? $ cd nuttxspace/nuttx $ cd boards/ $ git grep "BAS=y" sim/sim/sim/configs/bas/defconfig:CONFIG_INTERPRETERS_BAS=y sim/sim/sim/configs/bastest/defconfig:CONFIG_INTERPRETERS_BAS=y $ cd .. $ ./tools/configure.sh

Re: ESP32S3 arbitrary crash when no optimization configured

he code, but >> If >> you really need to turn it off to debug a specific function, consider >> using >> the attribute `__attribute__((optimize(0)))`. >> >> Best regards, >> >> Em seg., 18 de set. de 2023 às 12:05, Alan C. Assis >> escreveu: >>

Re: epoll oddities following setup/teardown optimizations

Hi Wang Bowen and Marten, Is it possible to include an ostest with this code to avoid similar regression in the future? BR, Alan On 9/18/23, 汪博文 wrote: > Hi, > > I did the epoll optimization last year. And your analysis is right. The new > epoll implementation has BUG and I has reproduced

Re: ESP32S3 arbitrary crash when no optimization configured

Hi Mike, I remember facing similar issue with ESP32 in the past. Because I started using NuttX with ARM chip and in the past the GCC toolchain has some issue with you are trying to compile debug symbols (-g) and optimization enabled (-O2) I always disabled optimization while enabling debugging.

[OT] NuttX Internation Workshop Subscription is opened

Hi NuttXers, Please help us to spread the news: https://events.nuttx.apache.org Finally after four years we will have a physical event like that in Gouda, Netherlands in 2019. I'm looking forward to it! BR, Alan

Re: [EXT] Re: CTU CAN FD driver multi-licence for Nuttx

I think the authors of the driver can release the source code using two or more licenses. We already have an example of it in NuttX: SocketCAN Since they add the OR license clause it is fine. BR, Alan On 9/14/23, Alin Jerpelea wrote: > Hi Pavel, > > small oftopic regarding the license

Re: [EXT] Re: CTU CAN FD driver multi-licence for Nuttx

On 9/7/23, Brennan Ashton wrote: > On Thu, Sep 7, 2023, 9:01 AM Gregory Nutt wrote: > >> >> > I think GPL code shouldn't be included directly, but I think it is >> > fair to allow GPL code be downloaded using the building system case >> > user selected it. >> >> We created this directory

Re: make command error

he app name from 'M+++' to 'mthreeplus' but the error still > appears: > > [cid:35aa8eda-31a2-4d80-825e-e653c25698da] > > [cid:3cb94f25-e1fc-48b8-9f8d-753d5fc09ceb] > ________ > De: Alan C. Assis > Enviado: quinta-feira, 7 de setembro de 2023 13:10 > Para: dev@nuttx

Re: make command error

Hi Miguel, It was many years ago, normally the used hello_main() etc, to avoid main() symbol collision. Now the apps can use main() and the building system will concatenate it automatically. Probably the issue that Gustavo is facing is some messing with the source code. I think he is using

Re: [EXT] Re: CTU CAN FD driver multi-licence for Nuttx

I think GPL code shouldn't be included directly, but I think it is fair to allow GPL code be downloaded using the building system case user selected it. Some time ago I suggested to create a tainted variable in the building system to track it, after I suggested that a friend of mine from

Re: New application to Nuttx

Look: boards/xtensa/esp32/esp32-devkitc/configs/wifi Use: esp32-devkitc:wifi BR, Alan On 9/3/23, Gustavo Soares wrote: > Hi! > > I checked the value of the application stack size and it was 2048 ideed, so > I manually changed to 8000 using menuconfig and there it is: > >

Re: ESP32-S3 RS485 support

Hi Petro, The current RS485 implementation used on ESP32 is not using internal RS485 controller of ESP32, it is implemented by "software". So you can use it connecting a RS485 transceiver to UART port and using the right DIR pin controller by RS485 driver. It is possible to use the internal IP

Re: Adding bluetooth configuration on esp32 hangs nsh

done as >>> long >>> as you make sure you are grabbing the most recent version. You can also >>> build it (or MCUboot) from source by changing the image configuration >>> options in the menuconfig. >>> >>> Cheers, >>> Lucas >>> __

Re: bt4 + ble5 (plus wifi) on esp32 where are the docs?!?

Hi Mike, Actually NuttX doesn't use Zephyr BLE Stack, it uses an ancient BLE stack that Intel released as BSD license. That stack was used on Zephyr and evolved a lot with help from Nordic Semi. It was only a guy from Nordic that started porting that stack to nRF51/nRF52 and Nordic end-up adding

Re: Adding bluetooth configuration on esp32 hangs nsh

nt > the time to document this on your own web site instead of submitting a > PR to the official NuttX docs yourself? ;-) > > -m > > On 9/1/2023 10:02 AM, Alan C. Assis wrote: >> Probably because we didn't update the documentation yet! :-) >> >> We

Re: Adding bluetooth configuration on esp32 hangs nsh

; -m > > On 9/1/2023 9:13 AM, Alan C. Assis wrote: >> Hi Mike, >> >> Please sure you are using the right bootloader too: >> >> https://acassis.wordpress.com/2022/09/27/flashing-nuttx-bootloader-and-firmware-using-make-command/ >> >> BR, >> &

Re: Adding bluetooth configuration on esp32 hangs nsh

Hi Mike, Please sure you are using the right bootloader too: https://acassis.wordpress.com/2022/09/27/flashing-nuttx-bootloader-and-firmware-using-make-command/ BR, Alan On 9/1/23, Mike Moretti wrote: > Hi, > > So, just to be sure, I made a completely fresh directory, untarred the > 12.2.1

Re: Serialrx

Hi Bert, On 8/28/23, Bert Voldenuit wrote: > Hello, > > I am trying to run the serialrx app (out of the box) from the examples, but > i get the following errors: > > - Some warnings because of conversion; no big deal > - undefined reference to standard librarie function like: fprintf, >

Re: Porting NuttX - console management trouble

Hi Philippe, On 8/21/23, Philippe Leduc wrote: > Hello, > >> Sounds like the console device is in RAW mode. For proper NSH behavior, >> the console TTY must be configured in COOKED mode. That configuration >> should occur automatically if the uart was configured as the serial >> console. I

Re: Porting NuttX - console management trouble

Hi Philippe, On 8/18/23, Philippe Leduc wrote: > Hello, > > I am currently in the process of porting NuttX to the i.MX8MP (Cortex-M7) > SoC Did you see that: https://github.com/apache/nuttx/pull/10294 Maybe you can reuse or merge part of it. > from NXP. I managed to have a POC that boot and

Re: CDC/ACM console data to NuttX corrupted.

Hi Tim, On 8/16/23, Tim Hardisty wrote: > I am trying to get CDC/ACM working on my custom board so I can have a > USB console. I have finally worked out the arcane set of CONFIG options > needed, found the to-be-expected bugs/inconstencies with some of the > SAMA5 code, that I have worked around

[OT] Last days to submit your proposal to the NuttX International Workshop

Dear NuttXers, The submission of proposals to the NuttX Workshop will end on the 18th of August. Because we will have a mixed presentation (face-to-face and on the Internet), we accept in-person or remote presentation. Please consider contributing your knowledge with others who also love NuttX

Re: STM32F405RG and NuttX

Hi Robert, Why don't you use the omnibusf4 board as starting point, since it uses same MCU model: arm/stm32/omnibusf4/configs/nsh/defconfig:CONFIG_ARCH_CHIP_STM32F405RG=y Starting with a board and changing the MCU to other like you are doing will cause many issues, like this CONFIG_MM_REGIONS.

Help to review possible code coming from Linux kernel

Please help us to review: https://github.com/apache/nuttx/pull/10157 https://github.com/apache/nuttx/pull/10195 BR, Alan

Re: CAN TX fail handling

Hi Nathan, On 8/10/23, Nathan Hartman wrote: > On Thu, Aug 10, 2023 at 4:38 AM Tim Hardisty > wrote: > >> I like your idea of IOCTLs - I will be revisiting this issue in the next >> few weeks and will look to see what's involved in implementing this as it >> "feels" right. >> > > snip > > In

Re: CAN TX fail handling

metal > type software dev where I'm in total control albeit unique to a > given/chosen processor, so any suggestions would be very welcome. > > On 09/08/2023 19:56, Alan C. Assis wrote: >> Hi Tim, >> >> I think that the default behavior of CAN Controller is trying

Re: CAN TX fail handling

Hi Tim, I think that the default behavior of CAN Controller is trying to send indefinitely a message, some HW can define some retry limit. Please take a look: https://forum.pjrc.com/threads/67435-FlexCAN-Infinite-Endless-TX-Retries So, I'm not sure if it will make sense to implement a CAN TX

[OT] Top IoT Boards for Development & Prototyping You Need to Know in 2023

Thanks Halysson for the link: https://www.iotforall.com/top-iot-boards-for-development-prototyping-you-need-to-know-in-2023 The irony: the board they used in the image is the Meadow F7 powered by NuttX :-D Case some one know this gentleman, please ping him. BR, Alan

Re: [Article] NuttX on Star64 JH7110: Creating the First Release

Congratulations Lup!!! This is a great achievement! BR, Alan On 8/7/23, Lee, Lup Yuen wrote: > Good News! NuttX now officially supports the Pine64 Star64 64-bit RISC-V > SBC, based on the StarFive JH7110 SoC. > > (StarFive VisionFive 2 SBC will probably work too, anyone would like to > test?)

Re: [Article] NuttX on Star64 JH7110: RISC-V PLIC Interrupts and Serial I/O

Congratulations Lup! I'm looking forward to see Star64 JH7110 integrated into mainline. BR, Alan On 8/2/23, Lee, Lup Yuen wrote: > Thanks Tomek! Here's the backup link for the article (since Codeberg is > down): https://lupyuen.github.io/articles/plic > > I found out (from Hacker News) that

Re: NuttX on FreeBSD survey

Hi Milan and Tomek, It should be nice to have our CI testing on FreeBSD as well. Milan, after you get the port done, please let us know if you can help us to get it integrated in the github CI. BR, Alan On 7/31/23, Tomek CEDRO wrote: > On Mon, Jul 31, 2023 at 9:53 AM Milan Obuch wrote: >>

Re: ESP32 question

The JTAG pins are between pins 43 and 47 (page 12) here: https://www.espressif.com/sites/default/files/documentation/esp32-s2_datasheet_en.pdf BR, Alan On 7/30/23, Alan C. Assis wrote: > Hi Milan, > > On 7/30/23, Milan Obuch wrote: > sic >>> I got an S2 Mini V1.0.

Re: ESP32 question

Hi Milan, On 7/30/23, Milan Obuch wrote: sic >> I got an S2 Mini V1.0.0 WEMOS.CC like yours and confirmed the issue. >> After changing the pins to 33 and 34 (as you noticed pins 43 and 44 >> are not available, Wemos' mistake) the serial console is not showing >> up. > > Hi, > > do you see any

Re: ESP32 question

Hi Milan, On 6/30/23, Milan Obuch wrote: ... >> 1) Connect a USB/Serial adapter directly the the pins used as UART0, >> not ideal because probably you don't want attachment like it to your >> board; > > Problem here is not using additional USB/serial cable, I do it > regularly if necessary or

Re: Encoder STM32F7

Hi Roberto, I think currently the driver is hard-code to use X2 mode, you will need to modify it to work on X4 mode. Currently the QE é architecture specific, there is not a generic upper half driver where you can define features that driver will use like X1, X2, X4 mode, zero index pin, etc.

Re: Serial LCD example

Hi Mark, In fact some examples are ("incorrectly") hard-code to some I2C Bus or uses #ifdef to compile only if that I2C Bus is enabled in the menuconfig. There are pros and cons of using this approach: PROS: - 'Guarantee' that such config works (dev tested it); - Developer doesn't need to test

Re: Unable to get nsh working on Adafruit Feather rp2040

Hi Richard, Probably it is a MacOS issue. I just confirmed it still working fine on Linux (Ubuntu 23.04). These are the step-by-step process: --- $ git clone -b 1.1.2

Re: pwm examples...

Hi Ed, Run: $ make menuconfig And inside menuconfig type "/" (without quotes) to search for symbols. You can type PWM, but there are many PWM features so it is better to search for EXAMPLES_PWM It will return: Symbol: EXAMPLES_PWM [=n] Type : tristate Prompt: Pulse width modulation (PWM)

Re: [VOTE] Apache NuttX 12.2.1 RC0 release

Thank you Nathan, Maybe we should create some script to automatically generate this log release report and save it in some place, like a attachment log in the release page. I'm happy to see renewed interested in a small NuttX footprint to use as bootloader. I think it is possible to get a

Re: [VOTE] Apache NuttX 12.2.1 RC0 release

+1 Please find log of tested boards below! BR, Alan - ESP32: $ xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=xtensa-esp32-elf-gcc

Re: OpenFPGALoader

Hi Simon, ispVM is pure C: https://github.com/ganehag/br-ts7500/blob/master/ts7500utils/ispvm.c Could be easier to get working on NuttX than openFPGALoader, although to latter will open doors to many vendors! BR, Alan On 7/13/23, Simon Filgis wrote: > LFE5U-25F-8BG381C > > with attached SPI

Re: [Article] Boot NuttX from Network with U-Boot and TFTP

On 7/13/23, Nathan Hartman wrote: > On Thu, Jul 13, 2023 at 12:24 PM Gregory Nutt wrote: >> >> >> > Maybe you could that a look in the minnsh PoC, it was running on MCU >> > with less than 16KB Flash and 8KB RAM. As you can see in the image it >> > is using less than 2KB RAM: >> >> To get to the

Re: [Article] Boot NuttX from Network with U-Boot and TFTP

Hi Nathan, On 7/13/23, Nathan Hartman wrote: > Hi Lup, > > Excellent article, as always! > > On Thu, Jul 13, 2023 at 10:38 AM Alan C. Assis wrote: >> In NuttX case it is easier because we can do it without the bootloader! > > There was a recent discussion about usi

Re: OpenFPGALoader

Hi Simon, I didn't look the code, but openFPGALoader is implemented in C++ and I don't know if they are using features that don't fit well to microcontrollers. So, the only way to confirming if it works is trying to compile and run it. If you only need to use FPGAs from Lattice, maybe you can

Re: [Article] Boot NuttX from Network with U-Boot and TFTP

Hi Lup, That is very nice! I never tested TFTP on NuttX, but I used to boot Linux/uCLinux using it, downloading the kernel image inside the bootloader: https://acassis.wordpress.com/2009/03/19/solved-dbug-bootloader-network-problem/ In NuttX case it is easier because we can do it without the

Re: SPI api example...

Hi Ed On 7/11/23, Ed Sutter wrote: > On 7/11/2023 2:00 PM, Alan C. Assis wrote: >> Hi Ed, >> >> Are you the Ed Sutter from uMon bootloader author? >> >> On 7/11/23, Ed Sutter wrote: >>> Hi, >>> Are there any examples of application c

Re: SPI api example...

Hi Ed, On 7/11/23, Ed Sutter wrote: > On 7/11/2023 2:00 PM, Alan C. Assis wrote: >> Hi Ed, >> >> Are you the Ed Sutter from uMon bootloader author? > Yep. Hi Alan! > I just finished I2C and used apps/system/i2c as my test. Nice! I2CTools is very useful to verify

Re: SPI api example...

Hi Ed, Are you the Ed Sutter from uMon bootloader author? On 7/11/23, Ed Sutter wrote: > Hi, > Are there any examples of application code accessing a SPI device on Nuttx? > Thanks, Normally NuttX applications don't access the SPI Bus directly, an SPI device needs to be exported through the

Re: adding a new board - files?

Hi Krasimir, On 7/10/23, Krasimir Cheshmedzhiev wrote: > Hi all, > > > > I am working on adding a nucleo-u5a5zj-q to nuttx supported boards. How > (where I can read) to prepare files - those which I created and those which > I changed, to make them part of main source tree? > Please follow the

<    1   2   3   4   5   6   >