Ahh yes thank you! I was looking in the wrong place . it has been too long 😉
-Oorspronkelijk bericht-
Van: Alan Carvalho de Assis
Verzonden: dinsdag 2 augustus 2022 21:43
Aan: dev@nuttx.apache.org
Onderwerp: Re: Sensor DS18b20
maybe you are not looking at the right place:
https://g
Its not there anymore? Or am I missing something?
Ben
-Oorspronkelijk bericht-
Van: Alan Carvalho de Assis
Verzonden: dinsdag 2 augustus 2022 21:30
Aan: dev@nuttx.apache.org
Onderwerp: Re: Sensor DS18b20
Hi Ben,
It is supposed to be at drivers/sensors/ds18b20.c
BR,
Alan
On 8/2/22,
Is there a driver available for the DS18b20/DS1820? And yes where can I find
dit?
Thanks in advance
Ben
Hello,
Who could point out a way to implement a Hall sensor driver for say the
Hamlin 55100? Is there an example (driver) which is already in the
repository?
Say an "attachInterrupt" routine like in the Arduino stack?
Thanks again.
Ben
Hi All,
Ik had the STM32F407xE (https://github.com/mcauser/MCUDEV_DEVEBOX_F407VET6)
and others on this site added in NuttX 8.2 BSD version. Is it plausible to
bring these over to this NuttX version. Or is it already in place?
Thanks again.
Ben
Hello,
I see some info searching Google about the 1-Wire (through USART)
implementation for NuttX. It seems there is a driver for it for use through
U(S)ART.
Did someone already have implemented STM32 for it? src/stm32_1wire.c (or
something) how I could initialize this driver?
I appreci
--> My reply
1) If I enable Debug Assertions the build will not run at all as it halts
very very early on. Debugger suggests the system is in up_idle(). --> Mostly
this is caused by a "fault" somewhere down the line. Does it "print" ABCDE?
Did you enable "debug" in make menuconfig?
2) Any (valid
Non of these. I do not need this overhead?
Ben
-Oorspronkelijk bericht-
Van: Grr
Verzonden: zaterdag 8 mei 2021 19:57
Aan: dev@nuttx.apache.org
Onderwerp: Re: CAN example crashes
No, I mean on top of that: CANopen, UAVCAN, other?
El sáb., 8 de may. de 2021 12:44 PM,
escribió:
> You
Maybe my video from some while ago CAN help ?
https://www.youtube.com/watch?v=sSpNrP0DUI4
Ben
-Oorspronkelijk bericht-
Van: Grr
Verzonden: zaterdag 8 mei 2021 19:09
Aan: dev@nuttx.apache.org
Onderwerp: Re: CAN example crashes
Hello.
What protocol do you use on top of CAN?
El sáb., 8
You mean CAN FD or the CAN V2.0B? I use the standard with Extended ID's.
(MCP2515 / SPI) for automotive interaction.
https://ww1.microchip.com/downloads/en/DeviceDoc/MCP2515-Stand-Alone-CAN-Controller-with-SPI-20001801J.pdf
Ben
-Oorspronkelijk bericht-
Van: Grr
Verzonden: zaterdag 8 m
Hi All,
In Elektor I see that the promotion of Zephyr (also Apache2.0 licensed) is
named. Is there also something about NuttX in this matter?
Thanks
Ben
Thank you. Then my observation was a good one. This is not like the datasheet
was telling how the driver "should" work. I was trying to solve this, but its
deep in the core system where this CONFIG_PWM_PULSECOUNT has effect. If I only
had more time
Ben
-Oorspronkelijk bericht-
Van:
I Tried to show the difference (debug) in one image
https://imgshare.io/image/image.p307iH
I tried to state the differences... according the reference sheets and
application notes from the STM32F4xx family this should work "together"
where you use say TIM1 (or TIM8) [ADVANCED TIMERS] w
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.
Thank you. I am not so experienced as all you are. So I am a couple of years
behind... but beter late then never 😉
I recon I have to place some sort of voltage divider for the pins on the
QEncoder. This because i twill blow my MCU? Right?
Ben
-Oorspronkelijk bericht-
Van: Gregory Nut
Hi all,
I have a Honywell Quadrature Encoder:
http://www.farnell.com/datasheets/2329419.pdf
The LM7366R seems tob e an option, but this chip is hard to obtain and is old
(so it seems).
Would it be possible to get this encoder to work with say an STM32? (32-bit
timer I think)?
I want to read
Hello Matt,
You have 2 enable i2ctool in make menuconfig (also see blog Alan):
https://acassis.wordpress.com/2019/01/19/how-to-use-nuttx-i2c-scan-features/
And then on the prompt in NuttX you can do the command say:
i2c dev -b 1 0x00 0x7f
It will show you the used I2C addresses.
Hope this will
Nice.. I just want to use the ADC as feedback sensor for a plunger... I all
works fine until the FIFO is full 😉
-Oorspronkelijk bericht-
Van: Daniel Pereira Carvalho
Verzonden: woensdag 21 oktober 2020 21:01
Aan: dev@nuttx.apache.org
Onderwerp: Re: NuttX and continuous ADC conversion
M
I have implemented a daemon which uses sigaction. And indeed the ADC works with
this solution until the FIFO is full... Maybe I have to add an IOCT that resets
the ADC?... Or set the FIFO buffer back? Or make a ringbuffer instead of
FIFO
Ben
-Oorspronkelijk bericht-
Van: Nathan Har
Thats correct... so I have to start the conversion every time over again...
and het the value after that conversion I have seen continuous conversions
ADC on an STM32...
I will try to find a plausible solution.
Ben
-Oorspronkelijk bericht-
Van: Daniel Pereira Carvalho
Verzonden:
Is it possible to achieve a continuous ADC conversion, where the
sample[0].am_data is written in a struct (and constantly updated) and where I
can get and check the voltage from the ADC?
I have it working that the value I get is true and it also seems to measure the
change, but after some time
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
Please do not make technology about looks in functionality it has to work
and be solid and has to address its purposes. If all is finished and value is
there, one could bring a nice color too it 😉 Color is throwing money where
functionality died
Ben
-Oorspronkelijk bericht-
Van
And will there be a Zoom link? Or did I miss some info?
Ben
-Oorspronkelijk bericht-
Van: Schock, Johannes - NIVUS GmbH
Verzonden: zaterdag 15 augustus 2020 10:33
Aan: 'dev@nuttx.apache.org'
Onderwerp: NuttX Online Workshop
Just a hint:
If I'm correct, https://nuttx.events/ is broken
@Nathan
Maybe I am just a simple soul .but the root concept is (seems to be)
shared memory. Memory which is some sort of "topic" where an MCU is a
"subscriber" and where there is some sort of "applicational" orchestration. A
kafka bus on memory 😉
I think I am getting it, but where I am str
I added (git cloned some elementary files: libmetal and open-amp) and I have
got it build and compiled in Nuttx again.
Now looking at videos how I could use it. My "sensor" core (slave..?) is a
STM32F4VE.
Ben
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: vrijdag 17 april 2020
Very interesting... but Openamp was removed right?
Ben
-Oorspronkelijk bericht-
Van: Daniel Pereira Carvalho
Verzonden: vrijdag 17 april 2020 14:27
Aan: dev@nuttx.apache.org
Onderwerp: Re: Algorithm and Nuttx integration other platforms
AI..Kalman..et
Hi,
Did you think about an a
All,
I want to experiment with sensor fusion. Nuttx is the sensor "collector" and
does this in a great way. I want to use python for adding algorithms and
micro python is gone. With reason I think. And the embedded platform
Cortex-M4's mostly are not suited for this job. To slow in general.
Most of the "video's" and "learning material" for Nuttx is based on the
STM32F1. So that's validation enough?
And quirks? Which MCU does not have quirks? I benchmarked all kinds of MCU's
and every supplier/vendor has quirks and really annoying features and/or
other quirks. Documentation, support, e
Update:
I think I have found it. it has to do with 1-bit and 4-bit:
The SDIO Card Specification Version 2.0 is also supported with two different
databus modes: 1-bit (default) and 4-bit.
Nuttx has default 4-bit and that's why I was thrown of.
I tried to change the SDIO Clock (DIV) and wan
Update:
My purpose is to write data to a file in a thread. With append. Writing once
works.
int nbytesi;
nbytesi = write(fd_mmcsd, g_testmsg, strlen(g_testmsg));
if (nbytesi < 0)
{
printf("write_test_file: ERROR failed to write to %s, errno=%d\n",
"/dev/mm
Hi All,
I had the SD card written with using Nuttx, but then it stopt writing and
reading to and from the SD card. I get a CMD24 error:
mmcsd_eventwait: ERROR: Awakened with 14
mmcsd_writesingle: ERROR: CMD24 transfer failed: -5
It seems to think it wrote bytes, but no file there. What a
THREAD CAN BE CLOSED -- SOLVED!
SOLUTIONS:
1) File Descriptor expanding freezes MCU
Like Bernd stated!
2) SDIO -116 when I enable DEV-GPIO
Datasheet also comfirms:
PD2 -> SDIO_CMD
Changed:
#define GPIO_OUT1 (GPIO_OUTPUT|GPIO_PUSHPULL|GPIO_PORTD|GPIO_PIN2)
To:
#define GPIO_OUT1
I always do a:
sudo find ../apps/. -type f -name '*.o' -delete
sudo make clean && sudo make
sudo make distclean is reconfiguring kernel ... ... offcourse yes! It is
not crashing anymore!!! Thanks Bernd!
Now find out why my mount -t vfat /dev/mmcsd0 /sd is giving a 116 maount
failed when DEV_G
Hi all,
2 questions:
File Descriptor expanding freezes MCU
1)
Maybe a too simple question.. But why is my MCU "freezing up" when I expand
my File Descriptors:
RTOS Features -> Files and I/O -> Maximum number of file descriptors per
task .. From 8 --> 10. freeze. Back to 8. Oke.
SDIO
Why is the CS not pulled low at the end? So it can receive the last 0xFF?
When I bypass the gate it is working.. Using the gate it is not?
Thanks
Ben
I just got a 23LC1024 (128kb SDRAM 1MBit) and want to "attach" this as
external RAM. To scale up the free mem.
I am looking at examples like stm32_extmem.c and qspi.. which one is best to
use? And do I have to "make" a driver for it? And bind it to SPI? Or are my
thoughts wrong?
Thanks again...
All,
I want to set up some generic SDRAM as a component (board) to support the
ILI9341 LCD screens. I tried a few boards now (L476RG, F407VE, etc.), but
all seem to come short in (SD)RAM fort he framebuffer.
What do you advise? And is there already a solution in Nuttx for it?
In this ar
Oke I think I am getting somewhere
Priv has (during lcd_framebuffer):
fblen -> 153600
xres -> 320
yres -> 240
stride -> 640
display -> 0 '\0'
fbmem = 0x0
*fbmem -> 72 'H'
But it stil runs into this error:
priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen);
if (priv->fbmem == NULL)
{
Priv->fblen = 0
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: zaterdag 4 januari 2020 21:02
Aan: dev@nuttx.apache.org
Onderwerp: Re: NX Graphics
> nsh> free
>
> procfs_open: Open 'meminfo'
>
> meminfo_open: Open 'meminfo'
>
> procfs_read: buffer=0x16d0 buflen=512
>
> meminf
Ow and PS:
With FSMC I could allocate the framebuffer tot he ILI9341???
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: zaterdag 4 januari 2020 21:09
Aan: dev@nuttx.apache.org
Onderwerp: Re: NX Graphics
>> priv->fbmem = 0
> But what was priv->fblen? The size you are trying to a
Yes... but where does it get set?
I tried the f429i and compared "free":
(picture… hope it shows)
-Oorspronkelijk bericht-
Van: Gregory Nutt
Verzonden: zaterdag 4 januari 2020 21:09
Aan: dev@nuttx.apache.org
Onderwerp: Re: NX Graphics
>> priv->fbmem = 0
> But what wa
nsh> free
procfs_open: Open 'meminfo'
meminfo_open: Open 'meminfo'
procfs_read: buffer=0x16d0 buflen=512
meminfo_read: buffer=0x16d0 buflen=512
total used freelargest
Umem: 192576 7696 184880 124848
procfs_read: buffer=0x16d0 bufle
priv->fbmem = (FAR uint8_t *)kmm_zalloc(priv->fblen);
if (priv->fbmem == NULL)
{
lcderr("ERROR: Failed to allocate frame buffer memory\n");
I dont seem to get fbmem filled. tried all config options, but it stays
empty. I do not have NX(WM) activated. The framebuffer should be
All,
I am trying to get a ILI9341 working and a tip from Dave gave me the option
to implement it as a generic SPI driver. Before I have tried to do this with
LTDC and FMC like on the STM32F429i.
But in both cases I get in pdccurses:
* Unable to create SP: in pdc_initscr.c its not rea
http://incubator.apache.org/projects/nuttx.html
Gives back 404's when clicking on links like Board Reports and Website.
And Wiki is nog active yet?
No dates are filled here? Is this not the right project overview site?
Roadmap/status?
Ben
My current state is that the outline is formed and that the filling per
"chapter" is on its way and that the purpose of the book is set. Its public is
also for people who come across Nuttx for the first time and do not have seen
movies or other tutorials from Nuttx and did not have the privilege
48 matches
Mail list logo
