Re: NuttX Workshop 2024 - event planning
Wow! I would love to visit Japan in May/June and will definitely try to make it this year. / Erik Den fre 12 jan. 2024 kl 10:25 skrev alin.jerpe...@sony.com < alin.jerpe...@sony.com>: > Hi all, > > A new year started and we should start planning for the yearly workshop > > This year Sony offered to host the workshop in Tokyo, Japan as it as > planned on 2020 (the in person event was canceled due to Covid) > > Sony proposed the following periods for the event and will come back with > practical information for attending the event > 20 May - 16 June (better weather/beautiful nature) > 1-15 September (may be rainy) > > I would like to ask for volunteers to help organizing the event and > opinions regarding the dates > > Best regards > Alin > > >
Re: [Russia attacked Ukraine]
Stay safe! This surely is the worst of humanity. Hope you get all the support you need to get through this. Den fre 25 feb. 2022 17:26Petro Karashchenko skrev: > Hi, > > I know that this channel is not intended for things that I will write, but > I still will send this E-mail. > > For people that do not know: yesterday at 5AM Russia started massive > invasion and attacked Ukraine. The fightings are all over the central, > eastern, north and south. The bombs are exploding all over the country. > This is terrible. People are in fear. The war is in my country. We are > praying for peace and people to stop dying. > > At least knowing about this will be a support for my and my people's. > > Let Lord be with us, > Petro >
Re: Nimble on U-blox Nina B112 (Nrf52832)
Change the Nimble stacksize from 16384 to 2048, the nimble application starts as it should. Haven't had time to look into it anymore, it should've been 16k for a reason. We´ll have to trim stacksizes to leave some ram for the actual application though. I guess the board should start advertising some data, which it doesn't. I´m not familiar with Mynewt/Nimble at all, our BLE products use the zephyr rtos/stack together with MCUboot. This is tested on nrf52832-dk. apps/wireless/bluetooth/nimble/Makefile STACKSIZE = 2048 NuttShell (NSH) NuttX-10.1.0-RC1 nsh> nimble & nimble [5:255] hci init port init gap init gatt init ans init ias init lls init tps init hci_sock task init ble_host task init nsh> hci sock task host task free total used freelargest nused nfree Umem:31120 26144 4976 4944 83 2 nsh> ps PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK USED FILLED COMMAND 0 0 FIFO Kthread N-- Ready 002048 000536 26.1% Idle Task 1 224 RR Kthread --- Waiting Signal 002032 000600 29.5% hpwork 2 100 RR Kthread --- Waiting Signal 002032 000600 29.5% lpwork 3 100 RR Task--- Running 002032 001308 64.3% init 4 100 RR Kthread --- Waiting MQ empty 001000 000408 40.8% BT HCI Tx 5 255 RR Task--- Waiting Signal 002032 000856 42.1% nimble 6 1 RR pthread --- Waiting MQ empty 002048 000440 21.4% pt-0x12bed 0 7 1 RR pthread --- Waiting Semaphore 002048 000736 35.9% pt-0x12c05 0 nsh> arm-none-eabi-size nuttx textdata bss dec hex filename 3135742340 29472 345386 5452a nuttx Med vänlig hälsning Erik Englund Innoware Development AB Hyttvägen 13 73338 SALA Org.nr. 556790-2977 www.innoware.se Den lör 29 maj 2021 kl 01:03 skrev Nathan Hartman : > On Fri, May 28, 2021 at 5:24 PM Alan Carvalho de Assis > wrote: > > > Hi Nathan, > > > > On 5/28/21, Nathan Hartman wrote: > > > On Fri, May 28, 2021 at 4:43 PM Alan Carvalho de Assis > > > wrote: > > >> > > >> Hi Erik, > > >> > > >> Thank you very much for your help. > > >> > > >> I noticed the final binary is too big (more than 300KB), is it also > > >> happening to you? > > >> > > >> BR, > > >> > > >> Alan > > > > > > > > > Do some sections in the linker script need (NOLOAD)? > > > > > > See PR-3198 [1], where the binary was also huge, until davids5 taught > > > me about that: > > > > > > [1] https://github.com/apache/incubator-nuttx/pull/3198 > > > > > > > Good question! > > > > When using external libraries with NuttX I need to use "--gc-sections" > > to reduce the final size: > > > > > > > https://acassis.wordpress.com/2020/10/06/linking-external-libraries-on-nuttx/ > > > > BR, > > > > Alan > > > > Ah, yes, I use that too, together with -ffunction-sections and > -fdata-sections, because the linker gc works at the granularity of a > section. > > Did it work in this case? > > Nathan >
Re: Nimble on U-blox Nina B112 (Nrf52832)
Yes, I think seamless Nordic BLE support is important for NuttX. I will try to release some time for this, I´ve got nrf52832, nrf52833 and nrf52840 boards/products at my disposal. Med vänlig hälsning Erik Englund Innoware Development AB Hyttvägen 13 73338 SALA Org.nr. 556790-2977 www.innoware.se Den ons 26 maj 2021 kl 11:42 skrev Alan Carvalho de Assis : > Thank you Erik and Greg, > > I think we need to modify the default "sdc" board config to get nimBLE > running correctly. > > Thank you for these suggestions. > > BR, > > Alan > > On Wednesday, May 26, 2021, Erik Englund wrote: > > > I was encountering the same error while trying to run NuttX 10.x / nimble > > on NRF52832, tracked it down to insufficient ram available. > > The nimble nsh-app were present in the builtin-apps internal lists, but > > when trying to allocate application stack NuttX will return an error > code, > > and it seems all allocation error codes when trying to start an nsh-app > > will result in that "command not found" error message. > > I think enabling some memory debugging flags in nuttx will show you the > > correct error. > > > > So this isn't a nimble problem. > > > > > > Med vänlig hälsning > > Erik Englund > > > > Innoware Development AB > > Hyttvägen 13 > > 73338 SALA > > > > > > Org.nr. 556790-2977 > > www.innoware.se > > > > > > Den ons 26 maj 2021 kl 01:42 skrev Gregory Nutt : > > > > > The failure doesn't seem to have anything to do with nimBLE. The > nimble > > > app is not running at all! > > > > > > Put a breakpoint on nimble_main(). I doubt that you ever get there. > > > But I don't know why. > > > > > > The error report is probably misleading too... I seem to recall that > > > that there is an issue that the NSH error reported is always "command > > > not found" even if some other error occurs. It does mean that NSH > could > > > not run the built-in command, but it does not necessarily mean that the > > > built-in command was not found. > > > > > > On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote: > > > > Hi Matias and Miguel, > > > > > > > > I just tried nimble on nrf52832-mdk board without success: > > > > > > > > $ ./tools/configure.sh nrf52832-mdk:sdc > > > > $ make > > > > > > > > It downloaded and compiled nimble for NuttX correctly, the nuttx.bin > > > > was about 314944 bytes. > > > > > > > > When I drop this file inside DAPLINK disk it tries to flash and > create > > > > the file FAIL.TXT with this content: > > > > > > > > "The hex file cannot be decoded. Checksum calculation failure > > occurred." > > > > > > > > Then I ran "make menuconfig" and enabled the "Intel HEX binary > format" > > > > and after copying the nuttx.hex to DAPLINK disk the error > disappeared. > > > > > > > > Accessing the nsh terminal I can see the nimble binary, but it is not > > > running: > > > > > > > > NuttShell (NSH) NuttX-10.1.0-RC1 > > > > nsh> ? > > > > help usage: help [-v] [] > > > > > > > >. cdecho hexdump mkdir pssource > > > > unset > > > >[ cpexec ifconfig mkfatfs pwd test > > > > usleep > > > >? cmp exit ifdownmkrd rmtime > > > > xd > > > >basename dirname false ifup mount rmdir true > > > >break ddfree kill mvset uname > > > >cat dfhelp lsnslookup sleep umount > > > > > > > > Builtin Apps: > > > >nimble sh nsh > > > > nsh> nimble > > > > nsh: nimble: command not found > > > > nsh> ifconfig > > > > bnep0 Link encap:UNSPEC at UP > > > > > > > > nsh> nimble -h > > > > nsh: nimble: command not found > > > > nsh> nimble > > > > nsh: nimble: command not found > > > > nsh> > > > > > > > > Initially I thought it was caused by recent update of the nimble > stack > > > > on NuttX, but I moved to a commit previous to that update and still > > > > facing same error. > > > > > > > > Matias, do you think it could be some issue with my crosscompiler? > > > > > > > > I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi > > > package: > > > > > > > > gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision > > > > 277599] (15:9-2019-q4-0ubuntu1) > > > > > > > > Thank you very much! > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On 5/25/21, Miguel Wisintainer wrote: > > > >> Matias > > > >> > > > >> Me and Alan will investigate! > > > >> > > > >> Thank you so much! > > > >> > > > >> Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> > para > > > >> Windows 10 > > > >> > > > >> > > > > > >
Re: Nimble on U-blox Nina B112 (Nrf52832)
I was encountering the same error while trying to run NuttX 10.x / nimble on NRF52832, tracked it down to insufficient ram available. The nimble nsh-app were present in the builtin-apps internal lists, but when trying to allocate application stack NuttX will return an error code, and it seems all allocation error codes when trying to start an nsh-app will result in that "command not found" error message. I think enabling some memory debugging flags in nuttx will show you the correct error. So this isn't a nimble problem. Med vänlig hälsning Erik Englund Innoware Development AB Hyttvägen 13 73338 SALA Org.nr. 556790-2977 www.innoware.se Den ons 26 maj 2021 kl 01:42 skrev Gregory Nutt : > The failure doesn't seem to have anything to do with nimBLE. The nimble > app is not running at all! > > Put a breakpoint on nimble_main(). I doubt that you ever get there. > But I don't know why. > > The error report is probably misleading too... I seem to recall that > that there is an issue that the NSH error reported is always "command > not found" even if some other error occurs. It does mean that NSH could > not run the built-in command, but it does not necessarily mean that the > built-in command was not found. > > On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote: > > Hi Matias and Miguel, > > > > I just tried nimble on nrf52832-mdk board without success: > > > > $ ./tools/configure.sh nrf52832-mdk:sdc > > $ make > > > > It downloaded and compiled nimble for NuttX correctly, the nuttx.bin > > was about 314944 bytes. > > > > When I drop this file inside DAPLINK disk it tries to flash and create > > the file FAIL.TXT with this content: > > > > "The hex file cannot be decoded. Checksum calculation failure occurred." > > > > Then I ran "make menuconfig" and enabled the "Intel HEX binary format" > > and after copying the nuttx.hex to DAPLINK disk the error disappeared. > > > > Accessing the nsh terminal I can see the nimble binary, but it is not > running: > > > > NuttShell (NSH) NuttX-10.1.0-RC1 > > nsh> ? > > help usage: help [-v] [] > > > >. cdecho hexdump mkdir pssource > > unset > >[ cpexec ifconfig mkfatfs pwd test > > usleep > >? cmp exit ifdownmkrd rmtime > > xd > >basename dirname false ifup mount rmdir true > >break ddfree kill mvset uname > >cat dfhelp lsnslookup sleep umount > > > > Builtin Apps: > >nimble sh nsh > > nsh> nimble > > nsh: nimble: command not found > > nsh> ifconfig > > bnep0 Link encap:UNSPEC at UP > > > > nsh> nimble -h > > nsh: nimble: command not found > > nsh> nimble > > nsh: nimble: command not found > > nsh> > > > > Initially I thought it was caused by recent update of the nimble stack > > on NuttX, but I moved to a commit previous to that update and still > > facing same error. > > > > Matias, do you think it could be some issue with my crosscompiler? > > > > I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi > package: > > > > gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision > > 277599] (15:9-2019-q4-0ubuntu1) > > > > Thank you very much! > > > > BR, > > > > Alan > > > > On 5/25/21, Miguel Wisintainer wrote: > >> Matias > >> > >> Me and Alan will investigate! > >> > >> Thank you so much! > >> > >> Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para > >> Windows 10 > >> > >> >
Re: Anyone working on an MCUBoot Port for NuttX?
One important thing to have in mind is to keep it fully compatible with other RTOS. There are lots of products shipped with MCUBoot using Zephyr RTOS / other OS. If it is possible to sign and boot a NuttX application on a MCUBoot bootloader that is built on top of Zephyr, there are a much greater possibility for companies to try NuttX as it's just a firmware update thing, instead of a complete change of bootloader. Med vänlig hälsning Erik Englund Innoware Development AB Hyttvägen 13 73338 SALA Org.nr. 556790-2977 www.innoware.se Den ons 3 feb. 2021 kl 21:50 skrev bryan costanich : > Our interests align, maybe we can help? Ping me. :) >
Re: mkrd missing from build
Thanks for pointing me in the right direction.
My apps folder were 153 commits behind master, updating it resolved the
problem.
CONFIG_FS_WRITABLE flag was omitted as of Mars 21st.
Den ons 22 apr. 2020 kl 16:59 skrev Gregory Nutt :
>
> > nuttx$ cat .config | grep MKRD
> > CONFIG_BOARDCTL_MKRD=y
> > CONFIG_DRVR_MKRD=y
> > # CONFIG_NSH_DISABLE_MKRD is not set
> >
> > NuttShell (NSH) NuttX-8.2.0
> > nsh> help
> > help usage: help [-v] []
> >
> >[ cdecho help mkdir pwd sleep
> > unset
> >? cpexec hexdump mhrmtest
> > usleep
> >basename cmp exit kill mvrmdir time
> xd
> >break dirname false lsmwset true
> >cat ddfree mbpsshuname
> >
> > Builtin Apps:
> >hello nsh
> > nsh> mkrd
> > nsh: mkrd: command not found
>
> The commands are kept in an array of structures in
> apps/nshlib/nsh_commands.c. It the command is in the array, it will be
> executed and it will be in the help. So from the above, this would mean
> that the mkrd command is not in the array.
>
> That is determined by a setting in apps/nshlib/nsh.h:
>
>70 #undef NSH_HAVE_WRITABLE_MOUNTPOINT
>71 #if !defined(CONFIG_DISABLE_MOUNTPOINT) && CONFIG_NFILE_STREAMS > 0
>72 # define NSH_HAVE_WRITABLE_MOUNTPOINT 1
>73 #endif
>
> And logic in apps/nshlib/nsh_command.c:
>
> 326 #ifdef NSH_HAVE_WRITABLE_MOUNTPOINT
> 327 # ifndef CONFIG_NSH_DISABLE_MKRD
> 328 { "mkrd", cmd_mkrd, 2, 6,
> 329 "[-m ] [-s ] " },
> 330 # endif
> 331 #endif
>
> That is everything that is involved. So those are what you would need
> to check.
>
>
>
mkrd missing from build
Hi.. Is there any changes lately regarding the mkrd command? It isnt included in my builds anymore. This is whit the stm32f4discovery/nsh config. nuttx$ cat .config | grep MKRD CONFIG_BOARDCTL_MKRD=y CONFIG_DRVR_MKRD=y # CONFIG_NSH_DISABLE_MKRD is not set NuttShell (NSH) NuttX-8.2.0 nsh> help help usage: help [-v] [] [ cdecho help mkdir pwd sleep unset ? cpexec hexdump mhrmtest usleep basename cmp exit kill mvrmdir time xd break dirname false lsmwset true cat ddfree mbpsshuname Builtin Apps: hello nsh nsh> mkrd nsh: mkrd: command not found
