On Sat, Jan 16, 2021 at 6:08 PM Matias N. wrote:
> Hi,
> I would like to add this feature so I can measure used stack on nRF52. I'm
> trying to figure out what
> is needed and it would seem I need to replicate the go_nx_start() function
> found on other _start.c
> files. Is that all there is to i
Hello,
I am working to port NuttX on a board based on STM32F4DISCOVERY. The
microcontroller is the STM32F407VET6.
USB CDC support is not initializing.
When I plug the USB on the board, I have the following dmesg response in Linux:
[517062.075048] usb usb1-port2: attempt power cycle
[517062.7269
As an additional information, if I load the STM32F4DISCO on my board, USB works.
Em dom., 17 de jan. de 2021 às 10:43, Flavio Castro Alves Filho
escreveu:
>
> Hello,
>
> I am working to port NuttX on a board based on STM32F4DISCOVERY. The
> microcontroller is the STM32F407VET6.
>
> USB CDC suppor
On Sun, Jan 17, 2021 at 8:43 AM Flavio Castro Alves Filho <
flavio.al...@gmail.com> wrote:
> Hello,
>
> I am working to port NuttX on a board based on STM32F4DISCOVERY. The
> microcontroller is the STM32F407VET6.
>
> USB CDC support is not initializing.
>
> When I plug the USB on the board, I have
What you can do is compare .config generated from that defconfig to .config
generated from "./tools/configure.sh -l stm32f4discovery:usbnsh" and see
the differences. You can also compare include/nuttx/config.h from both
configs
Another approach is to start from discovery config and do the modifica
Thank you very much for your fast response.
I checked the boot calls and they are the same, regarding USB initialization.
I compared the include/nuttx/config.h files too ... at least regarding
USB, I couldn't see anything critical.
The development approach that I am working was exactly starting
Thanks, I tested simply copying the code and it works. I will probably make a
PR for that and we can then refactor the code to have a single place for each
arch.
Best,
Matias
On Sun, Jan 17, 2021, at 05:06, Xiang Xiao wrote:
> On Sat, Jan 16, 2021 at 6:08 PM Matias N. wrote:
>
> > Hi,
> > I w
El dom, 17 ene 2021 a las 9:10, Flavio Castro Alves Filho (<
flavio.al...@gmail.com>) escribió:
> Thank you very much for your fast response.
>
> I checked the boot calls and they are the same, regarding USB
> initialization.
>
> I compared the include/nuttx/config.h files too ... at least regardi
I don't think that this combination will work:
CONFIG_CDCACM_CONSOLE=y
CONFIG_CONSOLE_SYSLOG=y
I think that the syslog console device would have to be available at
bootup. Normally a RAM log is is used to hold syslog data if a USB
console is used.
I might be wrong about that and this should
Hi Flávio,
Other file to compare is the System.map, it will give you some hints
about which functions are missing in your board. Then you can
investigate why the function is missing.
Maybe it is just an #ifdef that is not entering because you forgot the
rename the board's name.
Try to do it and
On Sun, Jan 17, 2021 at 11:36 AM Grr wrote:
> Have you tried starting from original, working config and adding and
> testing after _every single_ change?
>
> If you're changing OS elements, maybe one of them is affecting USB without
> you knowing
>
> Testing at every change is tedious but sometim
Sort of binary search? You're right, that's faster. I tend to see it like a
sequence rather than a searchable collection
El dom, 17 ene 2021 a las 11:15, Nathan Hartman ()
escribió:
> On Sun, Jan 17, 2021 at 11:36 AM Grr wrote:
>
> > Have you tried starting from original, working config and addi
On Sun, Jan 17, 2021 at 1:34 PM Grr wrote:
>
> Sort of binary search? You're right, that's faster. I tend to see it like a
> sequence rather than a searchable collection
Oh yes, bisect does a binary search of a sequence of commits to find
the one that broke something. I've used it to find which c
Em dom, 17 de jan de 2021 13:52, Gregory Nutt
escreveu:
> I don't think that this combination will work:
>
> CONFIG_CDCACM_CONSOLE=y
> CONFIG_CONSOLE_SYSLOG=y
>
> I think that the syslog console device would have to be available at
> bootup. Normally a RAM log is is used to hold syslog data if a
I was preparing myself psychology to start rebuilding, but the idea to
follow the commits is much more attractive :-)
Thank you for the advice.
Best regards
Flavio
Em dom, 17 de jan de 2021 14:15, Nathan Hartman
escreveu:
> On Sun, Jan 17, 2021 at 11:36 AM Grr wrote:
>
> > Have you tried sta
What I realized is that there is no USB log message showing.
I checked the options on USB monitor to show initialization messages but
got no messages. :-(
Best regards,
Flavio
Em dom, 17 de jan de 2021 14:08, Alan Carvalho de Assis
escreveu:
> Hi Flávio,
>
> Other file to compare is the Syste
This probably explains why you get no USB log. How could you? It is
configured to go to the console (i.e., /dev/console) but there is no console
device.Sent from my Galaxy
Original message From: Flavio Castro Alves Filho
Date: 1/17/21 3:50 PM (GMT-06:00) To:
dev@nuttx.apac
17 matches
Mail list logo
