When using an I2C master, the file won't compile without the change,
because BUSY is undefined
diff --git a/contrib/nuttx/arch/arm/src/samd2l2/sam_i2c_master.c
b/contrib/nuttx/arch/arm/src/samd2l2/sam_i2c_master.c
index 0874a66716..588b355336 100644
--- a/contrib/nuttx/arch/arm/src/samd2l2/sam_i2
arch/arm/src/samd2l2/sam_adc.c requires two files to be includes:
arch/arm/src/samd2l2/sam_adc.h
and
arch/arm/include/samd2l2/sam_adc.h
Both however use the same inlcude protector define.
I've changed one of them locally.
When I try to register as /dev/adc0 I get error 17.
I could trace it furthe
ork the
> https://github.com/apache/incubator-nuttx to github user, apply your
> patch and click on Pulll requests -> New pull request
>
> Thank you very much!
>
> BR,
>
> Alan
>
> On 10/29/20, Bernd Walter wrote:
> > When using an I2C master, the file
ot;, which calls register_driver),
in which inode_reserve() then fails with EEXIST.
This is common code for all platforms, which fails.
> On 10/29/20, Bernd Walter wrote:
> > arch/arm/src/samd2l2/sam_adc.c requires two files to be includes:
> > arch/arm/src/samd2l2/sam_adc.h
> >
On Thu, Oct 29, 2020 at 05:42:58PM -0300, Alan Carvalho de Assis wrote:
> Hello,
>
> On 10/29/20, Bernd Walter wrote:
> > On Thu, Oct 29, 2020 at 08:51:13AM -0300, Alan Carvalho de Assis wrote:
> >> Hi Bernd,
> >>
> >> It was "working" f
.h
As you can see, the cxd56xx isn't prefixed, which is the same it had been
for the samd2l2 until 6bff1f4df4ae3e4fc21d7d98afdbfdcc855a6ed2 changed the
filename and protector name.
> On 10/29/20, Bernd Walter wrote:
> > On Thu, Oct 29, 2020 at 05:42:58PM -0300, Alan Carvalho de Assis wro
nto this and change it to match other arches.
But I like to find the other ADC problem before I rearrange the code.
Might take a few days.
> Its content should be inside the arch/arm/src/samd2l2/sam_adc.h
>
> BR,
>
> Alan
>
> On 10/29/20, Bernd Walter wrote:
> > On Thu
On Fri, Oct 30, 2020 at 12:26:33PM +0100, Bernd Walter wrote:
> On Thu, Oct 29, 2020 at 07:39:16PM -0300, Alan Carvalho de Assis wrote:
> > Ok, now I understood the issue you found
> >
> > Yes, arch/arm/include/samd2l2/sam_adc.h is wrong.
> >
> > I think thi
On Fri, Oct 30, 2020 at 12:26:33PM +0100, Bernd Walter wrote:
> On Thu, Oct 29, 2020 at 07:39:16PM -0300, Alan Carvalho de Assis wrote:
> > Ok, now I understood the issue you found
> >
> > Yes, arch/arm/include/samd2l2/sam_adc.h is wrong.
> >
> > I think thi
On Mon, Nov 02, 2020 at 03:09:12PM +0100, Bernd Walter wrote:
> On Mon, Nov 02, 2020 at 10:17:41AM -0300, Alan Carvalho de Assis wrote:
> > This should be a better idea because you will have 32KB of RAM. They
> > after getting it working you can remove not necessary features to
>
On Tue, Nov 03, 2020 at 03:34:46PM +0100, Bernd Walter wrote:
> On Mon, Nov 02, 2020 at 03:09:12PM +0100, Bernd Walter wrote:
> > On Mon, Nov 02, 2020 at 10:17:41AM -0300, Alan Carvalho de Assis wrote:
> > > This should be a better idea because you will have 32KB of RAM. They
&
On Wed, Nov 04, 2020 at 06:56:50PM -0300, Alan Carvalho de Assis wrote:
> Hi Bernd,
>
> Did you disable the serial console?
>
> CONFIG_NO_SERIAL_CONSOLE=y (Device Drivers -> Serial Driver Support ->
> Serial console (No serial console) ).
[194]nuttx-devel> grep CONSOLE contrib/nuttx/.config
# CO
I am supposed to call an spoi bus init function to get the spi device I
then use to register my device to.
This is the code in sam34:
/
* Public Functions
*
On Sat, Nov 14, 2020 at 07:25:36PM +0100, Bernd Walter wrote:
> I've tried to update for my board and saw that allocating the ethernet
> buffer failed.
> After activating more some debugging output, I've noticed that malloc
> fails even earlier.
> Don't think this
On Tue, Dec 15, 2020 at 07:28:38PM +0100, Bernd Walter wrote:
> Ich have some older boards with an at91samd21j18, but without xtal.
> I use them with USB and like to convert the code wo NuttX.
> So far I'd used the Atmel-ASF to setup the clock and for USB stack
> under FreeRTOS.
Ich have some older boards with an at91samd21j18, but without xtal.
I use them with USB and like to convert the code wo NuttX.
So far I'd used the Atmel-ASF to setup the clock and for USB stack
under FreeRTOS.
However, after reinspecting I hadn't used the correct clock setup,
which would be using t
that time was to use the DPLL instead.
I will submit a pull request for that, including the missing USB sync
support.
>
> BR,
>
> Alan
>
> On 12/15/20, Bernd Walter wrote:
> > On Tue, Dec 15, 2020 at 07:28:38PM +0100, Bernd Walter wrote:
> >> Ich have some
I usually do the following to measure time differences:
struct timespec tp;
uint64_t starttime;
clock_gettime(CLOCK_MONOTONIC, &tp);
starttime = ((uint64_t)(tp.tv_sec) * 100) + tp.tv_nsec / 1000;
//do something
clock_gettime(CLOCK_MONOTONIC, &tp)
On Fri, Oct 08, 2021 at 04:28:41AM +0200, Tomasz CEDRO wrote:
> Hello world :-)
>
> My first steps with NuttX on FreeBSD. I will ask some questions here
> for support and make it working on BSD :-)
>
> First one:
>
> % ./tools/configure.sh esp32c3-devkit:ble
> Copy files
> /home/cd/cederom/work
On Tue, Oct 19, 2021 at 07:16:14AM +0200, Tomasz CEDRO wrote:
> Sorry for yesterday, I just need to remember about zfs snap before
> root experiments or simply experiment in vm ;-)
I'm using sysutils/zfs-periodic for that reason.
>
> kconfig-frontends port for FreeBSD is ready:
>
> https://bugs
On Wed, May 11, 2022 at 07:13:17PM -0400, Nathan Hartman wrote:
> On Wed, May 11, 2022 at 5:19 AM Fotis Panagiotopoulos
> wrote:
> >
> > I was thinking the same thing.
> >
> > Which layer is responsible for this check?
> > IP, UDP, or ICMP?
>
>
> Logically it would seem to me that UDP should do
A recent change (e8f4d74ad0c33389c1094c3ca6c10a6336d8fbe7) moved the
individual rp2040_spi.c into the common directory.
How can a board with different chip select GPIO usage have a board
specific setup?
I don't see a way to disable the common implementation.
--
B.Walter https://www.bwct.de
Modbu
This is not about nuttx, but about this list.
Just a few minutes ago I had send a mail to this list.
The returned mail from the list was tagged as spam.
It wasn't enough to reject the mail, but tag it, so that it was filed
into the spam folder.
The major reason (rspamd default config) was 7 points
On Thu, Sep 15, 2022 at 09:48:42AM -0300, Alan Carvalho de Assis wrote:
> Actually you can include support for multiple devices of same type in
> the same SPI bus:
>
> #if defined(LCDxyz) || defined(LCDwku) ...
> switch (devid)
> {
> case SPIDEV_DISPLAY(0):
> /* Set the GPIO low to
While looking into the mcp2515 driver I noticed something unexpected.
In mcp2515_instantiate() it does the follofing:
SPI_SETFREQUENCY(config->spi, CONFIG_MCP2515_SPI_SCK_FREQUENCY);
SPI_SETMODE(config->spi, MCP2515_SPI_MODE);
SPI_SETBITS(config->spi, 8);
SPI_HWFEATURES(config->spi, 0);
I
On Fri, Jan 13, 2023 at 07:12:37AM +0800, Lee, Lup Yuen wrote:
> PinePhone on NuttX will soon support LVGL Touchscreen Apps! This article
> explains how we created the NuttX Driver for PinePhone's I2C Touch Panel...
>
> https://lupyuen.github.io/articles/touch2
Wow - this is quite interesting.
Th
> https://github.com/apache/nuttx/pull/8101
> >
> > Lup
> >
> > On Fri, Jan 13, 2023 at 7:41 AM Bernd Walter
> > wrote:
> >
> >> On Fri, Jan 13, 2023 at 07:12:37AM +0800, Lee, Lup Yuen wrote:
> >> > PinePhone on NuttX will soon suppo
Because of compiler updates I had to update Nuttx in one of my
SAMD21 based boards as well.
The last compile time issue was missing irqinfo in that file.
After adding an #include the issue was solved.
However, I'm in a merged environment and can't easily verify if that
isn't a local issue.
I have
On Tue, Mar 28, 2023 at 04:28:58PM -0400, Nathan Hartman wrote:
> On Tue, Mar 28, 2023 at 3:43 PM Fotis Panagiotopoulos
> wrote:
> >
> > Hello,
>
> Replying inline below...
>
> > I just noticed that there are some problems with the usage of asprintf()
> > throughout the code base.
> > This funct
On Mon, Jul 31, 2023 at 09:52:16AM +0200, Milan Obuch wrote:
> Hi,
>
> I'd like to know who else builds NuttX on FreeBSD - right now I know
> just one. Also, I'd like to know which hardware they use NuttX on.
> Could you please share? I'd like to create some FreeBSD port(s) to make
> user experien
On Wed, Aug 16, 2023 at 11:18:19AM +0200, Milan Obuch wrote:
> Hi,
>
> at the moment, I am able to build NuttX on FreeBSD for arm (Raspberry
> Pi Pico boards and similar, QuickFeather), xtensa (Espressif ESP32 and
> ESP32S2) and risc-v (Espressif ESP32C3 and ESP32C6, and PineCone -
> BL602 based),
On Thu, Dec 28, 2023 at 04:46:08PM +, Janardhan Silwal wrote:
> Oh!!
> So that is the one you used.
> I did see that on the menu config, but wasn't sure if it was the one. and I
> was halfway through completing the driver when I noticed that option in menu
> config anyway, so I went ahead and
ips.
> > On 28 Dec 2023, at 17:11, Bernd Walter wrote:
> >
> > On Thu, Dec 28, 2023 at 04:46:08PM +, Janardhan Silwal wrote:
> >> Oh!!
> >> So that is the one you used.
> >> I did see that on the menu config, but wasn't sure if it was the one.
The original ESP32 is said to have 320k RAM.
All board configs have the following:
CONFIG_RAM_SIZE=114688
Are RAM sections added later in the startup process or is there another
reason?
--
B.Walter https://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
d in, but not started and
that's my meminfo:
total used freelargest nused nfree
Umem: 230384 19120 211264 12995
So some RAM must have been added somewhere else.
>
> Best Regards,
>
> Alan
>
> On Thu, Apr 25, 2024 at 8:59 PM Bernd W
WiFi and BLE.
> > > >
> > > > The memory is used but the WiFi/BLE driver!
> > > >
> > > > Do you remember the old days where your video card used to eat your
> > main
> > > > memory and you should define in the BIOS how much memory
On Fri, Apr 26, 2024 at 07:58:00PM +0200, Tomek CEDRO wrote:
> Can you please elaborate more on why / how system hangs?
Nothing I can easily answer.
I have a complex codebase for a custom SAM4X board that I ported over to
a custom ESP32 board.
As part of that there is running HTTP code that I port
On Fri, Apr 26, 2024 at 09:17:30PM +0200, Bernd Walter wrote:
> On Fri, Apr 26, 2024 at 07:58:00PM +0200, Tomek CEDRO wrote:
> > Can you please elaborate more on why / how system hangs?
I've found two bugs in my http code related to that.
I have had random hangs when doing a
I have had problens with a new SAM4S based board in that it hang eraly
during startup, before initializing my 12MHz xtal.
Also the SWD didn't work anymore until I erased the chip.
Since the SWD didn't work it was quite obvious that there is some clock
related issue.
I've found out that the startup
On Tue, Jan 28, 2020 at 12:40:12PM -0300, Alan Carvalho de Assis wrote:
> Hi Bernd,
>
> On 1/28/20, Bernd Walter wrote:
> > I have had problens with a new SAM4S based board in that it hang eraly
> > during startup, before initializing my 12MHz xtal.
> > Also the SWD
On Tue, Jan 28, 2020 at 05:22:08PM +0100, Bernd Walter wrote:
> On Tue, Jan 28, 2020 at 12:40:12PM -0300, Alan Carvalho de Assis wrote:
> > Hi Bernd,
> >
> > On 1/28/20, Bernd Walter wrote:
> > > I have had problens with a new SAM4S based board in that it hang eral
I'm a bit confused about the state of LoRa support in NuttX.
I've seen a few configs with STM32 controllers.
And there is apps/examples/sx127x_demo
So far everything looks as if there is only radio support, but no
LoRaWAN implementation to send and receive messages from the things
network.
--
B.W
On Wed, Feb 19, 2020 at 02:33:19PM +0100, Philippe Coval wrote:
> Hi,
>
> I can share a personnal experience of using LoRaWAN on mcu.
> I also used a RN2483 module that handle serial commands,
In my case I have an RFM95W module connected to an SAM4E controller.
Those are quite common modules and
d to get the code running and maybe do some low power
node later.
> I also plan to make some tests on this as soon as I receive the Sx1276
> dev Kit.
I've already rolled my own PCB - lol.
Porting the existing driver to my own board isn't that difficult.
Just changing GPIO and and inte
I have a SAM4S16C, which has 128kB RAM and an ILI9325 display.
After some initial problems (the Panel I use is wired to 16-bit bus)
and several hardware problems I got it fully initialized with a testpattern
instead of the normal background color.
The code is based on the SAM4E driver.
...
board_l
On Sat, Mar 21, 2020 at 09:54:15PM +0100, Bernd Walter wrote:
> I have a SAM4S16C, which has 128kB RAM and an ILI9325 display.
> After some initial problems (the Panel I use is wired to 16-bit bus)
> and several hardware problems I got it fully initialized with a testpattern
> in
On Sat, Mar 21, 2020 at 11:34:41PM +0100, Bernd Walter wrote:
> On Sat, Mar 21, 2020 at 09:54:15PM +0100, Bernd Walter wrote:
> > I have a SAM4S16C, which has 128kB RAM and an ILI9325 display.
> > After some initial problems (the Panel I use is wired to 16-bit bus)
> >
On Thu, Apr 09, 2020 at 10:29:30AM +0200, disruptivesolution...@gmail.com wrote:
> 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 ->
I couldn't find a driver in the tree.
I'm asking in case I just oversaw it.
Otherwise I have to write it myself.
--
B.Walter http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
I recently started playing with the Core746I board from waveshare.
It is quite different from the stm32f746g-disco.
Seeveral IO are differently, the SDRAM is connected to bank 2, it
has a different xtal.
The stm32f746-ws looks like it could be for the waveshare board.
At least the PLL setup makes s
On Sun, Apr 26, 2020 at 07:38:44AM -0600, Gregory Nutt wrote:
>
> >>I recently started playing with the Core746I board from waveshare.
> >>It is quite different from the stm32f746g-disco.
> >>Seeveral IO are differently, the SDRAM is connected to bank 2, it
> >>has a different xtal.
> >>The stm32f
On Mon, Jul 13, 2020 at 05:41:05PM +0200, Disruptive Solutions wrote:
> Is there a millis() equivalent? Where the system timer (milliseconds) is
> kept solid in the back? Where you can obtain "passed system time"...
> without delay interventions from threads etc?
Is this what you mean?
#in
On Mon, Apr 14, 2025 at 04:11:40PM +0200, Tomek CEDRO wrote:
> Yeah I also had problems flashing this rpiPico boards with USB MSC
> method (mount+cp+umount) on FreeBSD.. is there a OpenOCD like method
> so I could try too? :-)
On FreeBSD I never mount and just dd directly to the device with bs=1M.
Out of curiosity I just took a look into the thhtp cgi code and noticed
something I don't understand myself.
There is the cgi_child(), which looks like it is to be called after a fork
for the child case.
It prepares the filedescriptors and calls exec.
The result of the exec is stored in a variable
54 matches
Mail list logo
