Thank you all for your advice. I'm sorry for the delay in replying to this
email. I'm able to get Nuttx and Nuttx-apps to work properly now.
On Tue, Mar 30, 2021 at 12:45 AM Xiang Xiao
wrote:
> This is a known issue, fixed here:
> https://github.com/apache/incubator-nuttx-apps/pull/624
> I would
So /dev/pmw0 = TIM1
/dev/pmw1 = TIM4
All well.. but with CONFIG_PWM_PULSECOUNT only TIM1 is working when you
give in counts but with counts=0 nothing happens
TIM4 is quitting immediatly. with CONFIG_PWM_PULSECOUNT DISABLED I can use
both in a generic way...
I think the:
#i
Hi,
I was implementing the following use-case:
On TIM1 (advanced) timer I want to use pulse counts (By configuring and
enabling: "CONFIG_PWM_PULSECOUNT") And for TIM4 I do NOT want to use this. Just
normal time-based.
But when I use examples/pwm_main.c this is giving me very strange responses.
Hi Alan,
yes of course, moving to include/nuttx/1wire/1wire_master.h also means
splitting into different header files 1wire_master.h 1wire_slave.h and so
on.
Maybe juha doesn't knew if this is 1wire specific. I think the fact that
only maxim integrated/or dallas provides chips for the 1wire bus it
My idea was to do something similar to the framebuffer device, using map to
access image data and ioctl's to control camera parameters and wait for a
frame. Is this mostly how v4l works?
Do you see a need for something more? Not sure what other aspects of video
handling require a specific so
Hi Marco,
This code was submitted by Juha, maybe he has some rational why it was
put there.
In fact the structures and functions definition seam to be generic and
should be at include/
But, including that file inside 1wire_master.h is not correct, because
it was has slaves definition.
BR,
Alan
Hi
I currently working on a sensor driver for a temperature sensor DS18B20
connected on a 1wire bus.
It seems to be that logic exists under drivers/1wire/1wire.c that provides
a common mechanism to select a sensor on the bus by their unique rom code.
I'm not quite sure if that procedure is specif
video driver contributed by Sony, already mimic v4l2 interface:
https://github.com/apache/incubator-nuttx/blob/master/drivers/video/video.c
We can enhance this driver by:
1.Split the upper/lower half interface
2.Add more ioctl
On Sat, Apr 3, 2021 at 6:00 AM Matias N. wrote:
> I looked around to
I looked around to get a sense of V4L complexity. This [1] (very old) article
here gives a good broad idea
and it wouldn't seem too difficult to have something like this in NuttX,
focusing on minimal initial support.
It could be an upper-half driver which expects the lower-half to provide the
ca
Am Sa., 3. Apr. 2021 um 13:40 Uhr schrieb Matias N. :
> Do you see a need for something more? Not sure what other aspects of video
> handling require a specific solution.
When talking about cameras you also need to specify the camera output
format.
This is mostly a raw format YUV for mipi cameras
Hi Matias,
yes, this is more or less the way how v4l works.
But v4l allows more flexibility. It is not restricted to cameras only.
v4l allows handling different types of input and output devices such as
cameras, monitors whatever.
I'm only a bit familiar with camera input devices.
The question is
My idea was to do something similar to the framebuffer device, using map to
access image data and ioctl's to control camera parameters and wait for a
frame. Is this mostly how v4l works?
Do you see a need for something more? Not sure what other aspects of video
handling require a specific soluti
Hi Marco,
I'm not sure, normally emails arrive fast here.
Maybe if it was your first email it could delay a little bit.
BR,
Alan
On Saturday, April 3, 2021, Marco wrote:
> Am Sa., 3. Apr. 2021 um 10:06 Uhr schrieb Marco :
>
> Sorry for spamming here, but showing my last reply in the mailing
Am Sa., 3. Apr. 2021 um 10:06 Uhr schrieb Marco :
Sorry for spamming here, but showing my last reply in the mailing list was
so slowly. It took about 30 minutes or more. Is this the default case?
Marco
>
Hi,
I would love to see video support in nuttx.
I worked with video4linux a few years ago. What I loved was how to deal
with memory buffers from the user space.
The video4linux API allows the device configuration and also a registration
of an undefined amount of memory buffers (usually related to
16 matches
Mail list logo
