>From: Nathan Hartman
>Sent: 03 March 2023 18:36
>To: dev@nuttx.apache.org
>Subject: Re: Help me understand file open/close behaviours?
>
>On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
>> The bug I thought I had in a driver I'm developing (well, one of them!)
&
>From: Gregory Nutt
>Sent: 03 March 2023 19:03
>To: dev@nuttx.apache.org
>Subject: Re: Help me understand file open/close behaviours?
>
>On 3/3/2023 12:56 PM, Gregory Nutt wrote:
>> On 3/3/2023 12:36 PM, Nathan Hartman wrote:
>>> On Fri, Mar 3, 2023 at 1:07 PM Ti
Am I being dumb again? With CONFIG_DEBUG_ASSERTIONS set, the system doesn't
halt with a DEBUGASSERT (in a driver), and ends up in a while(true) type loop
and I have to pause the debug session and hope that the call stack helps (a
50:50 chance for reasons I am yet to understand).
The assert is i
>Sent: 06 March 2023 21:35
>To: dev@nuttx.apache.org
>
>Put a breakpoint on up_assert.
>
>You can also then set the PC and SP to the saved value to see the context
>of the assertion.
>
>On 3/6/2023 1:01 PM, Tim Hardisty wrote:
>>
>> I would really like it to
FWIW, I saw this yesterday on a new branch from Master. Bizarrely not with my
first distclean and make but with a subsequent rebuild. Then it disappeared
again: I tracked it down to a duplicate signal value with a random table having
appeared in Kconfig. That branch was short lived so I’m not ha
I have been frustrated at times by changes to master and it’s a conundrum:
- If you're developing code and base it on a stable release there's a good
chance that by the time your own code is "done" it will be incompatible with
latest and/or the current release.
- if you develop based on current,
>From: Gregory Nutt
>Sent: 03 March 2023 19:03
>
>On 3/3/2023 12:56 PM, Gregory Nutt wrote:
>> On 3/3/2023 12:36 PM, Nathan Hartman wrote:
>>> On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
>>>> - I have enabled CONFIG_SIGKILL_ACTION to allow me to ctr
age-
>From: Tim Hardisty
>Sent: 08 March 2023 17:37
>To: dev@nuttx.apache.org
>Subject: RE: Help me understand file open/close behaviours?
>
>>From: Gregory Nutt
>>Sent: 03 March 2023 19:03
>>
>>On 3/3/2023 12:56 PM, Gregory Nutt wrote:
>>> On 3/3/20
I was wrong. My app was mishandling console input :(
>-Original Message-
>From: Tim Hardisty
>Sent: 09 March 2023 15:34
>To: dev@nuttx.apache.org
>Subject: RE: Help me understand file open/close behaviours?
>
>Guess what - this behaviour is only on Master. Spent an h
I submitted a PR for a driver for the Broadcom APDS-9922 ambient light and
proximity sensor, written with what one might call the "traditional" method of
setting up the device via ioctl, then reading data when available according to
the device setup, via poll notify.
The reviewer (Hi Alan - I'
. In the
future someone - or I - can revisit it should there ever be a wish for the
APDS-9922 to follow the uORB/rpmsg approach.
Discuss! Guide me!
On 11/03/2023, 23:31, "Alan C. Assis" mailto:acas...@gmail.com>> wrote:
On 3/11/23, Xiang Xiao mailto:xiaoxiang781...@gmail.
Hi all,
I am investigating but someone may have seen this already?
Developing a custom audio driver but getting started with the null audio device
and NXplayer. I have saved a WAV file to the smartfs and it appears to be
valid. In case relevant I did this by saving the wav file to a header file
>From: Tim Hardisty
>
>Hi all,
>
>I am investigating but someone may have seen this already?
>
>
>When I try and play it with NXplayer, it fails while trying to enqueue
>the buffer and behaves as if the file is not open (EBADF)
After comparing audio_null.c to (for exa
Since my custom board still relies on a lot of out-of-tree stuff, I don't think
I can yet check this RC in the approved manner.
But, in the interests of trying to do my bit, I have rebased a new branch of my
current WIP fork of the upstream master to the upstream releases/12.1 branch,
and can c
What sort processing power? Memory? Peripherals?
SAMA5D27 (not that I’m biased lol) perhaps? ATSAMA5D27-WLSOM1 eval board has
what you need but might be over the top? USB host/device works and you can do
OTG/DRP on a custom board and it should be more than capable of doing CDC-ACM I
would have
f Microchip is planing to port ATWILC3000-MR110UA
WiFi/BLE chip to NuttX?
Should be nice to have a companion to BCM43 at drivers/wireless/ieee80211/
BR,
Alan
On 4/20/23, Tim Hardisty mailto:t...@hardisty.co.uk>>
wrote:
What sort processing power? Memory? Peripherals?
SAMA5D27 (not that I’m bi
20, 2023 at 9:15 PM Tim Hardisty wrote:
>> My longer term plan is to work on USB support for Bluetooth dongles rather
>> than dedicated module support as that – should – avoid the need for
>> Bluetooth SIG accreditation and fees. Don’t quote me on that!
>
> Blu
10k for "registering" a product with
>certified module. So no measurements, only paperwork.
>
>I would be glad to hear that's wrong! It feels wrong definitely...
>
>--
>Ingenieurbüro-Filgis
>USt-IdNr.: DE305343278
>--
>sent by mobile phone
>
>Tomek CEDRO schri
The SAMA5 support has no driver for the secure fuse peripheral. Kconfig allows
you to “enable” it but there’s no underlying code.
Before I go ahead and create a character driver for this, is the omission for a
“good” reason?
The driver would handle the relatively straightforward management of
Just posted this same text on GitHub:
https://github.com/apache/nuttx/issues/9127#issue-1687069010.
Content copied here for those that don't go there.
---
I have been investigating poor MTD performance with a GD25 memory on SPI0 of a
SAMA5D27 processor.
Using LittleFS, dd was
, but this arch has 32 bit "fields". Should I just stick
with 8 bit "fields" and have 4 times as many? Or have I missed the point of
"fields"?
Thank you!
>-Original Message-
>From: Tim Hardisty
>Sent: Tuesday, April 25, 2023 7:33 PM
>To: dev@nut
I am making use of the efuse driver code to create a driver for the sama5
secure fuse peripheral. There are not many drivers I can use as examplars but
there is code that follows this for the esp32 family of processors.
Those drivers protect fuse writes by encapsulating the entire write procedur
I am working on getting DMA working on the SPI peripheral of the SAMA5D2.
DMA reads now work well, but the writes take absolutely forever…unless I have
dma debug info enabled, when write transactions (to a GD25Q flash) do then work.
I’m working through it, as it sounds like a race condition or o
processors, though.
From: Simon Filgis
D-Cache flush?
--
Ingenieurbüro-Filgis
USt-IdNr.: DE305343278
--
sent by mobile phone
Tim Hardisty mailto:t...@hardisty.co.uk>> schrieb am Mi.,
17. Mai 2023, 20:05:
I am working on getting DMA working on the SPI peripheral of the SAMA5D2.
DMA rea
if there are obvious differences.
BR,
Petro
On Wed, May 17, 2023, 9:18 PM Simon Filgis
mailto:si...@ingenieurbuero-filgis.de>>
wrote:
D-Cache flush?
--
Ingenieurbüro-Filgis
USt-IdNr.: DE305343278
--
sent by mobile phone
Tim Hardisty mailto:t...@hardisty.co.uk>> schrieb am Mi.,
17. Mai
round 600KB/s (using dd to read from GD25 to
/dev/null) and write at 79KB/s (dd from FAT formatted ramdrv to GD25 memory
clocked at 103MHz). I think it should go faster, and I will probably keep
plugging away at it, but 20x faster than it was last week.
>-Original Message-
>From: T
Maybe OTG is superseded? USB C dual role port is the way to go, but needs a 25c
chip and software support to make it work. FUSB30x FTW :)
From: "Alan C. Assis"
Reply to: "dev@nuttx.apache.org"
Date: Saturday, 20 May 2023 at 20:10
To: "dev@nuttx.apache.org"
Subject: Re: esp32 custom board gpio
Hi,
This is perhaps more a POSIX/general programming question than NuttX but you
are all, so often, so very helpful :)
A touchscreen peripheral (SAMA5D2 as it happens) delivers X and Y coordinates
scaled 0-4095.
LVGL wants them scaled to the actual size of the display (800x480 in my case).
I'
Thanks Greg – I’ll take a look at those links, and take on board what you’re
saying.
From: Gregory Nutt
Reply to: "dev@nuttx.apache.org"
Date: Tuesday, 23 May 2023 at 19:52
To: "dev@nuttx.apache.org"
Subject: Re: Touchscreen scaling/LVGL
On 5/23/2023 12:11 PM, Tim Hardi
Could have sworn I had this working a year or 2 ago but it's stumped me today...
I have an SPI EEPROM device on my board, and use "ee25xx_initialize" to
register it as /dev/at25. That works fine.
But I can't do anything with it.
Unlike at25_initialize, the ee25xx_initialize doesn't return mtd_d
to allow access via USB from PCs etc., probably using YAML
formatting. Still thinking this all through.
From: Tim Hardisty
Reply to:
Date: Thursday, 25 May 2023 at 17:35
To: "dev@nuttx.apache.org"
Subject: SPI EEPROM
Could have sworn I had this working a year or 2 ago but it
My NuttX journey started in earnest about a year ago, after an enforced pause
for personal reasons. The processor on my board is ATSAMA5D2. In the last year
I have submitted (nearly all) merged PRs for this processor:
- mcan
- flexcom SPI
- ClassD audio
- SPI DMA
- flexcom USART
- efuse support
NXPlayer has an audio tone option to play tones, but no underlaying code hooks
for it.
Prompted by someone else's question today, I was thinking of looking at the
Audio Tone Generator in "Device Drivers | Audio Device Support" to see if it
could be adapted to output to a /dev/audio/pcm driver,
I have been tinkering with a blog/AboutMe thingy, also using it as a way to
learn markdown. Although I've not updated it for a short while, I decided to
add it to my GitHub profile if anyone is at all interested:
https://github.com/TimJTi
Where should that be in the (current) documentation? I’ll go and add it as I
didn’t know this.
From: Gregory Nutt
Reply to: "dev@nuttx.apache.org"
Date: Sunday, 11 June 2023 at 18:16
To: "dev@nuttx.apache.org"
Subject: Re: STM32 and GDB - How do I generate the ELF file?
On 6/11/2023 11:07 AM,
Not directly related to NuttX but I hope you don't mind me asking here.
Bottom line: has anyone used any bootloader other than u-boot to allow usb dfu
or RNDIS-type firmware updates, and that easily boot NuttX?
My board uses the usual SAMA5 methodology of AT91 bootstrap->u-boot->NuttX. It
all w
t; Maybe the only other suggestion is uMon (http://www.umonfw.com) an old
> bootloader that still active, but I didn't find port to SAMA5D.
>
> It was used mainly with Coldfire MCUs, but was ported to ARM too.
>
> BR,
>
> Alan
>
> On 7/1/23, Tim Hardisty wrote:
>&g
ons in the different phases(bootloader, ota, gui app),
cores(sensor hub, audio dsp), even security mode(tee).
The benefit of this approach include:
1. You just need write driver once and reuse in all possible scenario
2. Don't need learn and switch the development environment
On Sat, J
f :-)
Its a really nice idea but probably really lots of work :-)
--
CeDeROM, SQ7MHZ,http://www.tomek.cedro.info
--
Regards,
Tim Hardisty
A picture containing text, clipart Description automatically generated
+44 (0) 1305 534535
<http://www.jti.uk.com/>
to write a PC app and go
through all the signing malarkey etc.
On 01/07/2023 17:41, Gregory Nutt wrote:
On 7/1/2023 10:27 AM, Tim Hardisty wrote:
Lots of work to do a full u-boot replacement, yes. But a basic one
using existing NuttX stuff such as RNDIS, dfu, mtd etc. - for MY
board at least -
ith this and perhaps have developed some better
solutions.
--
Regards,
Tim Hardisty
A picture containing text, clipart Description automatically generated
+44 (0) 1305 534535
<http://www.jti.uk.com/>
JTi.uk.com <https://www.jti.uk.com/>
Having got u-boot to actually do something, I now have a board that
powers up autonomously and runs nsh with no intervention from me. Quite
relieved!
As a step towards it booting my own (barely started) app I thought I'd
play around with booting other example apps, and went for lvgldemo.
This
Yes - both that and the lvgldemo stack size (up to 65535 each).
On 05/07/2023 18:21, Xiang Xiao wrote:
Do you try CONFIG_INIT_STACKSIZE instead?
On Thu, Jul 6, 2023 at 1:01 AM Tim Hardisty
<mailto:t...@hardisty.co.uk> wrote:
Having got u-boot to actually do something, I now have a
LE_CMD_HISTORY=y
CONFIG_SYSTEM_COLOR_CLE=y
CONFIG_SYSTEM_NSH=y
CONFIG_SYSTEM_NSH_STACKSIZE=2048
CONFIG_SYSTEM_UNIQUEID=y
CONFIG_TTY_SIGINT=y
CONFIG_UART1_SERIAL_CONSOLE=y
CONFIG_USART2_BAUD=38400
CONFIG_USART3_BAUD=10
CONFIG_VIDEO_FB=y
CONFIG_WATCHDOG=y
CONFIG_WQUEUE_NOTIFIER=y
On 05/07/2023 18:45, Petro Karash
nt, right?
On Wed, Jul 5, 2023, 8:54 PM Tim Hardisty
<mailto:t...@hardisty.co.uk> wrote:
Sure. I think attachements get stripped out so I have pasted the
contents (I've "xxx"d references to the board name)
#
# This file is autogenerated: PLEASE DO NOT EDIT IT.
#
# You can use
odify lvgldemo_main and place print some message to console
+ sleep(1); in a loop just after it is entered? Not sure if that will give
us much, but worth of trying to get some information.
Best regards,
Petro
On Wed, Jul 5, 2023, 9:30 PM Tim Hardisty
<mailto:t...@hardisty.co.uk> wrote:
Yes
in a loop just after it is entered? Not sure if that will give
us much, but worth of trying to get some information.
Best regards,
Petro
On Wed, Jul 5, 2023, 9:30 PM Tim Hardisty wrote:
Yes (or "music") - so called by
nsh: lvgldemo music
It's a memory-type problem of some sor
ate bootloader, or use a simple designed-for-purpose program.
On 01/07/2023 10:56, Tim Hardisty wrote:
> Not directly related to NuttX but I hope you don't mind me asking here.
>
> Bottom line: has anyone used any bootloader other than u-boot to allow usb
> dfu or RNDIS-type fir
On 11/07/2023 18:28, Ed Sutter wrote:
Hi,
Are there any examples of application code accessing a SPI device on Nuttx?
Thanks,
Ed
Plenty - MAX31855 K-type thermocouple interface for example. Look at the
examples in the Applications setup within menuconfig.
SPI devices will be accessed via char
I am now cracking on with the app for my custom board, and in parallel
writing a production board-test app.
In trying to cover potential board faults, I have found that if there's
something that prevents a CAN message reaching an endpoint/destination,
the CAN transmitter (of course, as I under
ne some retry limit.
Please take a look:
https://forum.pjrc.com/threads/67435-FlexCAN-Infinite-Endless-TX-Retries
So, I'm not sure if it will make sense to implement a CAN TX timeout
on NuttX side, since this behavior could be HW dependent.
BR,
Alan
On 8/9/23, Tim Hardisty wrote:
I
issue.
If you implement the idea of resetting the CAN controller in the
can_close() you need to guarantee that it will be reinitialized correctly,
because in can_open() it expects the CAN controller in working state.
BR,
Alan
On 8/9/23, Tim Hardisty wrote:
Thanks Alan,
I can see that a timeout/retry
I am trying to get CDC/ACM working on my custom board so I can have a
USB console. I have finally worked out the arcane set of CONFIG options
needed, found the to-be-expected bugs/inconstencies with some of the
SAMA5 code, that I have worked around for now (most are covered by
disabling debug a
lem, it should be possible to fix.
Will you file a bug report so we can communicate there in public, and tag
us or send the url by email?
And then post your config there. I'll try it out and try to repro!
-adam
On Wed, Aug 16, 2023 at 10:56 AM Alan C. Assis wrote:
Hi Tim,
On 8/16/23, Ti
us or send the url by email?
And then post your config there. I'll try it out and try to repro!
-adam
On Wed, Aug 16, 2023 at 10:56 AM Alan C. Assis wrote:
Hi Tim,
On 8/16/23, Tim Hardisty wrote:
I am trying to get CDC/ACM working on my custom board so I can have a
USB console. I
can talk on email for now. Do you have one that doesn't
work? I'd love it if you can send it to me.
What I got working was CDC/ACM console and CDC/ECM ethernet over USB
on the same USB connection. Is that relevant to what you're looking
for? If so I can come up with a config tha
s.
The USB2.0 OTG host or device modes are handled 100% in the SAMA5D2
drivers and only handle the data transport, not the Power Delivery mode.
Ok, I'll give the CDC/ACM console thing a try and let you know.
-adam
On Wed, Aug 16, 2023 at 2:22 PM Tim Hardisty wrote:
Just FUSB302. It u
esn't play nicely with syslog...I'm investigating that now.
On 17/08/2023 10:20, Tim Hardisty wrote:
Hi Adam,
You are right - wasn't at my dev PC and was going from memory. The
FUSB302 does of course only manage PD and CC pullup/pulldowns - I know
I got confused at some point wh
sues for someone to pick up at some point in the future, maybe.
On 17/08/2023 16:06, Tim Hardisty wrote:
OK...progress.
CDC/ACM console behaves like this if CONFIG_CDCACM_NRDREQS is left at
the default 4. It needs a given keyboard key to be pressed 4 times to
work, and/or garbles the text sent
Thanks Greg, this helps me understand better how it all hangs together.
Regards,
Tim.
> On 17 Aug 2023, at 21:33, Gregory Nutt wrote:
>
>
>> On 8/17/2023 10:34 AM, Tim Hardisty wrote:
>> I have concluded that CDC/ACM will NOT play alongside SYSLOG - most likely
>>
This is, I'm sure, more a generic POSIX question than NuttX-specific but I am
still not that familiar with either!
When I wrote the SAMA5D2 ClassD audio driver I followed the methods appropriate
for using "apb" so it works well with nxplayer (for example).
But I want to play simple audio tones,
Thanks Gregory. I looked at that but it produces tones using PWM. The
ClassD of the SAMA5D2 is a PCM device, so not an immediately obvious match?
On 26/08/2023 23:17, Gregory Nutt wrote:
>
>>> But I want to play simple audio tones, from a sine look-up table,
>>> and filling a buffer and enqueuin
device at /dev/audio/pcm0
and have the driver manage the buffer and ready flags etc.
I will add other notes in an answer to Gregory's reply to this.
On 27/08/2023 05:59, Tomek CEDRO wrote:
On Sat, Aug 26, 2023, 20:18 Tim Hardisty wrote:
This is, I'm sure, more a generic POSIX question
nking of adding, but perhaps I'm am not understanding that
/dev/audio/pcm0 can't (shouldn't) actually be opened as a character driver?
Sorry for the dumb questions!
On 26/08/2023 23:10, Gregory Nutt wrote:
On 8/26/2023 12:18 PM, Tim Hardisty wrote:
This is, I'm sure, more a generi
Hz tone using 48 sampling for 500ms. Looks like there are similar functions
"out there" I could reference.
Is that more along the right lines perhaps?
On 27/08/2023 11:17, Tim Hardisty wrote:
Thanks Gregory. The existing ClassD driver is registered as /dev/audio/pcm0 and
is a PCM de
Or am I completely missing the point and I just need to use the nxaudio
system!!??
On 27/08/2023 12:25, Tim Hardisty wrote:
Looking a little more at the write function of audio_ops_s it is not used by
any existing driver and is documented to be for device-specific
information...so it is not
The classD driver DOES register itself as /dev/audio/pcm0, and works correctly
as such with nx_player.
The conversions are wav (or mp3 etc) to pcm.
Don’t if we’re talking cross purposes or the classd driver works in a way it
shouldn’t!!!
> On 27 Aug 2023, at 23:00, Gregory Nutt wrote:
>
> A
SAMA5D2 specific, I should add.
> On 27 Aug 2023, at 23:23, Tim Hardisty wrote:
>
> The classD driver DOES register itself as /dev/audio/pcm0, and works
> correctly as such with nx_player.
>
> The conversions are wav (or mp3 etc) to pcm.
>
> Don’t if we’re talki
On 28/08/2023 02:49, Nathan Hartman wrote:
On Sun, Aug 27, 2023 at 6:24 PM Tim Hardisty wrote:
SAMA5D2 specific, I should add.
On 27 Aug 2023, at 23:23, Tim Hardisty wrote:
The classD driver DOES register itself as /dev/audio/pcm0, and works
correctly as such with nx_player.
The
On 27/08/2023 23:56, Gregory Nutt wrote:
On 8/27/2023 4:24 PM, Tim Hardisty wrote:
SAMA5D2 specific, I should add.
There is no support for the Class D driver for any SAMA5D2 board in the
source tree.
Indeed - it's a custom/proprietary board which is why I added and
contribute
On 27/08/2023 23:53, Gregory Nutt wrote:
On 8/27/2023 4:22 PM, Tim Hardisty wrote:
The classD driver DOES register itself as /dev/audio/pcm0, and works
correctly as such with nx_player.
You are mistaken. The Class D driver does not register itself as a
character driver. grep -r
One of my many, no-doubt, dumb/inexperienced questions
NuttX has nxplayer for audio, with support for .wav files etc. But...
...is there a native/built-in way of playing video files (.mp4 for
example)? I know I can write a video file frame by frame, but hopefully
I don't need to? Can't fin
Hello helpful people. I am not sure if this is a POSIX or NuttX
question, so apologies it it's something I "should" know.
I am looking for a methodology - ideally portable (POSIX) - perhaps a
queue, to hold a list of messages (CANbus) that need to be transmitted
in the correct chronological or
single TX buffer.
>
> Best regards,
> Petro
>
> чт, 19 жовт. 2023 р. о 22:35 Tim Hardisty пише:
>
>> Hello helpful people. I am not sure if this is a POSIX or NuttX
>> question, so apologies it it's something I "should" know.
>>
>> I am
> first, so the mechanism how do you want to ensure that messages are
> transmitted with the chronological order is not clear to me, unless you use
> a special version of the peripheral driver that uses a single TX buffer.
>
> Best regards,
> Petro
>
> чт, 19 жовт. 2023 р.
someone
may use one without the other. But, nevertheless, it is your call...
If you provide me with a YAML parser, I believe that I can develop for you
a new settings storage that uses this parser.
Fotis
On Mon, Dec 5, 2022 at 12:12 AM Tim Hardisty
wrote:
I have interest in your settings st
opic. Please take your time and submit when
you are ready.
Best regards
Alin
From: Tim Hardisty
Sent: den 28 oktober 2023 12:10
To: dev@nuttx.apache.org
Subject: Re: Code donation
Hi, Did anyone else make any progress with porting your settings code to
NuttX Apps? It's taken a while bu
Hi,
I have an out-of-tree custom board (which lives resides in my main NuttX
folder as ./../CustomBoards/boardname). I use checkpatch.sh even on my
board software in that locations as I like to be consistent, but it
complains that the path (line 2 of the header comment) must begin with
the r
Hi,
I'm wondering if there is an "approved" usage of assert vs debugassert
for files/apps in the nuttx-apps repo?
My thinking is:
* use debugassert if a function in apps would only fail if the calling
code, probably (or possibly only) if other functions within apps,
rather than an unkn
Question first, then explanation.
How do I use losetup (which is what I think I need) with a character
memory device and mount an FS on it? SPI EEPROM and LittleFS specifically.
Yes, it's a bad idea, probably, but I just want to have a play and lack
of NuttX/POSIX/Linux knowledge has bitten m
e a spi flash driver, and change its read/erase/write
routines (and initialization) by copying code from a spi eeprom driver.
Sebastien.
Le 14/12/2023 à 19:13, Tim Hardisty a écrit :
Question first, then explanation.
How do I use losetup (which is what I think I need) with a character
memory devic
Hi,
What flash are you using out of interest?
But, the basic approach (in or called from your board bringup for
example) is:
spi_flash= sam_spibus_initialize(PORT); /* this call is arch dependent */
if(!spi_flash)
{
/* Do something */
}
#ifdefined(CONFIG_MTD_M25P)
mtd = m25p_initialize(spi_f
2:12, Janardhan Silwal wrote:
Hi,
I am using MT25QL, 1Gbit series flash memory.
Thanks for the template.
Would running in this format over the middleware running over nuttx also follow
the same approach?
Best Regards,
Janardhan
____
From: Tim Hardisty
Sent: Thursday, De
______
From: Tim Hardisty
Sent: Thursday, December 28, 2023 19:15
To:dev@nuttx.apache.org
Subject: Re: LittleFS Implementation using MTD for NOR flash
I have only ever used NuttX "directly" with my apps running over it
rather than any other middleware or anything, so I can't answe
ards,
Janardhan
____
From: Tim Hardisty
Sent: Thursday, December 28, 2023 19:15
To:dev@nuttx.apache.org
Subject: Re: LittleFS Implementation using MTD for NOR flash
I have only ever used NuttX "directly" with my apps running over it
rather than any other middleware or an
gin with.
> Aren't they supposed to be similar and autoprobing?
>
>>
>> From: Tim Hardisty
>> Sent: Thursday, December 28, 2023 20:18
>> To: dev@nuttx.apache.org
>> Subject: Re: LittleFS Implementation using MTD for NOR flash
>
n the mounted partition?
>
> Best Regards,
>
> Janardhan
>
> From: Tim Hardisty
> Sent: Thursday, December 28, 2023 20:36
> To: dev@nuttx.apache.org
> Subject: Re: LittleFS Implementation using MTD for NOR flash
>
> FYI - if you
My SAMA5 board has an LCD with variable brightness (pwm controlled).
arch/arm/src/chip/sam_lcd.c has a function called "sam_backlight) that
takes a level value, but it appears to be local to that file, and the
only call to it is in the LCD init functions in that file, complete with
a comment t
ubsystem:
https://docs.kernel.org/gpu/backlight.html
I think you could create a simple char device driver (at
drivers/lcd/backlight.c) that will receive IOCTLs to set the backlight
dimming.
Best Regards,
Alan
On Wed, Jan 3, 2024 at 3:03 PM Tim Hardisty wrote:
My SAMA5 board has an LCD with variable
If someone can post with a consensus/decision once there is one, it
would be most useful!
On 03/01/2024 17:35, Fotis Panagiotopoulos wrote:
Just to be clear, I am always referring to the standard C assert()
function/macro.
Not the unconditional NuttX ASSERT() macro. Notice the capitalization!
Would a variation on this proposal be to add app-specific
NXAPP_DEBUGASSERT etc.? This would then be "global" but unique to apps,
not overlap with O/S DEBUGASSERTs, and make for a simpler global
search/replace of current DEBUGASSERT in apps, and just need a one-off
new set of entries in the app
My board uses built-in SAMA5 TSD peripheral to interface with a
resistive touchscreen on a 5" TFT. Early on I implemented (and had
merged) an ioctl to allow the low level driver to scale the x/y data to
match the display resolution but I am now finding it actually needs a
multipoint calibration
make menuconfig
RTOS Features ->Tasks and Scheduling -> Application entry point
also
RTOS Features ->Tasks and Scheduling ->Application Name
On 18/03/2024 19:44, Gustavo Soares wrote:
Hello!
I've built an application to run on NuttX and I'd like to know if it's possible
to make it start whe
+1 non-binding. On my custom board:
NuttX 12.5.1-RC0 3fcd063148 Apr 9 2024 16:22:37 arm jti-xxx
arm-none-eabi-gcc -v
Supported LTO compression algorithms: zlib
gcc version 13.2.1 20231009 (Arm GNU Toolchain 13.2.rel1 (Build arm-13.7))
On 09/04/2024 08:40, Alin Jerpelea wrote:
Hello all,
I am getting in a mental pickle regarding LVGL (V9) and NuttX, in
conjunction with the SAMA5D2 with it's built in LCD Controller peripheral.
In the past - bare metal - I have simply set up two buffers so one can
be written to while the other is copied out to the actual display. But
now NuttX i
Thank you Gregory. I will read all of this and, so far, have skim read
the first you linked to and now understand it a little better already
and it confirms that the SAMA5D2 does indeed have a frame buffer
interface, that I register in my board bringup (so longer ago I'd
forgotten LOL) - but it
er as best as I can
tell.
I believe it needs a rework of the lvgl framebuffer driver - which is
probably down to LVGL rather than NuttX people to sort; but I may see if
I can create a custom driver using the LVGL guidelines for now.
On 14/06/2024 11:13, Tim Hardisty wrote:
Thank you Grego
+1 from me!!
On 21/07/2024 00:55, Daniel Appiagyei wrote:
Hi,
Is anyone opposed to:
- creating more specific github issue labels,
- encouraging everyone to use them, and
- setting up permissions on github such that anyone that has contributed to
the repo has the ability to add/remove labels?
Th
ll want to create a reliable
solution that works out of the box with no surprises right? :-)
Have a good day folks :-)
Tomek
On Sat, Oct 5, 2024 at 11:11 AM Tim Hardisty
wrote:
FYI you can no longer change LVGL version from Kconfig AFAIK, but you
can force the use of any version you want by check
ro.info
On Mon, Oct 7, 2024, 14:37 Tim Hardisty wrote:
FYI, I tried RC0 on my SAMA5D2 custom board with no issues. My app and
LVGL demos (with LVGL V9.1 - with known issues - and V9.2) run OK as
does the FB example app, so I would think any issues are possibly
arch-specific rather than 100% down
101 - 200 of 284 matches
Mail list logo
