Say I do not want to use a board but a standalone MCU say the STM32F722RET6

NuttX speaks of "boards" and not about MCUs. Maybe a dumb question, but does NuttX run on custom made PCB's where one uses the MCU named in "boards"? Or is there something with a bootloader or something? With DFU I can push nuttx.bin right (if the mcu supports it). Is there some wish to add the

Re: Say I do not want to use a board but a standalone MCU say the STM32F722RET6

I didn't follow! Maybe someone else could get it and help. On 9/26/20, disruptivesolution...@gmail.com wrote: > NuttX speaks of "boards" and not about MCUs. Maybe a dumb question, but > does > NuttX run on custom made PCB's where one uses the MCU named in "boards"? Or > is there something with a

Re: Say I do not want to use a board but a standalone MCU say the STM32F722RET6

Awesome, thanks! Op za 26 sep. 2020 10:31 p.m. schreef Bob Feretich < bob.feret...@rafresearch.com>: > Nuttx already supports the STM32F722RET6.� The configuration controls > can be found at > > https://github.com/apache/incubator-nuttx/tree/master/boards/arm/stm32f7/nucleo-144/configs/f722-nsh

Re: Say I do not want to use a board but a standalone MCU say the STM32F722RET6

Board does not mean dev board, it's the the board that your chip is soldered down to. When you do your design you need to define how the clocking, power, peripherals and bring up for your device work. This is all what board means. You can define this all externally and include it as you want, but

Re: Say I do not want to use a board but a standalone MCU say the STM32F722RET6

I see you already got an answer but just in case I'll add mine, if it helps: On Sat, Sep 26, 2020, at 04:32, disruptivesolution...@gmail.com wrote: > NuttX speaks of "boards" and not about MCUs. Maybe a dumb question, but does > NuttX run on custom made PCB's where one uses the MCU named in "board

Stack size alignment

Hi! I just encountered a problem with do_stackcheck(), and wanted to ask for an opinion... In my (PX4) software I have got some threads, who define their stack size unaligned by 4 bytes (uint32_t). The stack coloring works on uint32, and thus doesn't color the topmost bytes of the stack whe

Re: Stack size alignment on arm

Hi, Yes it happens on master (just tested a minute ago). I think everything else is in order, but stack coloring is broken at the top of the stack, if the stack size is not aligned. -Jukka On 25.9.2020 11.08, Schock, Johannes - NIVUS GmbH wrote: Is this happening on master as well? I've co

Re: RE: Stack size alignment on arm

Sure! Go ahead and fix it the way you see best, thanks! -Jukka Schock, Johannes - NIVUS GmbH kirjoitti perjantai 25. syyskuuta 2020: > > 1. Set the stack size as aligned already in > > arch/arm/src/common/arm_createstack.c: > > > > - tcb->adj_stack_size = stack_size; > > + tcb->adj_sta

Task socket Binding

Hi, i am new to nuttx. so when i was going through the code then could not understand how task is binded to sockets. like in linux, sockets are created with socket_create() which calls sock_alloc() and then it creates an inode under sockfs and retrieves the socket tied to the inode. so with this w

parallelizing mkdep?

Hi, as a test I changed the depend generation to main nuttx Makefiles to this: %.dd: %.c $(Q) $(MKDEP) $(DEPPATH) "$(CC)" -- $(CFLAGS) -- $< > $@ makedepfile: $(patsubst %.c,%.dd,$(SRCS)) @for f in $^; do cat $$f; done > Make.dep $(call DELFILE, $^) .depend: Makefile $(SRCS) $(TOPDIR)$(DELIM).c