goes rogue, for example?
>>>> * Adding options for recovery (e.g. "insert USB memory stick now"
>>>> or use TFTP or whatever - but that's arch and board specific so
>>>> not really suited to generic enhancement of NXBoot, and needs
>>>> printf's. Uboot has loads of script-type options as well as
>>>> Kconfig driven choices, but overall Uboot is slow and clunky
>> and
>>>> not suited - in my opinion - to embedded products.
>>>> * Or perhaps this can actually be easily done with scripts of
>> some
>>>> sort and it is simply outside of my experience?
>>>> * But perhaps some Kconfig choices based on other NuttX features
>>>> (TFTP, DFU etc) would be OK...but which. So...
>>>> * Rather than NXBoot simply exiting - which is pointless as where
>>>> does it exit to? - or having Kconfig choices of what to do,
>>>> perhaps there could just be Kconfig option to spawn an
>>>> error-recovery task in the event of a boot fail. So the core
>>>> NXboot app allows for recovery, but the implementation of the
>>>> error task is personal choice (but could have an example).
>>>>
>>>> I'm willing to implement changes and enhancements - within reason lol -
>>>> so if there are other things it could benefit from add them to this list
>>>> and let's discuss :-)
>>>>
>>>>
>>>> TimH
>>>>
CONFIG_AUDIO_TONE?
Not sure if that’s exactly what you’re after but could be?
> On 22 Feb 2025, at 17:12, Kevin Witteveen wrote:
>
> Hi nuttx,
>
> I need an audio device that can generate sound using PWM on the RP2040. It
> appears nothing already exists for this.
> What would be a good way t
There is nuttx/drivers/input of course - only just remembered; I'll see if
anything "generic" fits there for this.
>-Original Message-
>From: TimH
>Sent: Wednesday, May 24, 2023 12:04 PM
>To: dev@nuttx.apache.org
>Subject: RE: Touchscreen scaling/LVGL
&
I'm thinking:
1) that the LVGL Gregory linked to is a contender for the graphical interface,
only for LVGL of course, to do the calibration
2) The existing calibration routines in nuttx-apps (e.g. ccalibration for NXWM
as suggested by Alan C. Assis) is a great alternative for non-LVGL
implement
> >> The TSD driver creates a generic /dev/input0 character driver,
>> >> which is what LVGL (set via Kconfig) opens. Scaling within the LVGL
>> >> code isn’t right either, I don’t think?
>> >>
>> >> I can only think of either:
>> >>
>> >> 1) creating a new character driver that does a translation –
>> >> registered as
>> >> /dev/input1 (or whatever) that LVGL uses, and this driver reads
>> >> input0 when required and returns translated values.
>> >>
>> >> 2) Enhance the chip's TSD driver after all, using a Kconfig setting
>> >> to enable X/Y scaling to the display's size (set in board-specific
>> >> files already).
>> >>
>> >> Both seem a little messy though so perhaps I’m missing something
>> obvious?
>> >> Can't be the first to need to do this?
>> >>
>> >> Thanks,
>> >>
>> >> TimH
>> >>
>> >>
>> >
>>
>From: Tomek CEDRO
>Sent: Friday, April 28, 2023 5:15 PM
>
>On Thu, Apr 27, 2023 at 5:27 PM Tim Hardisty wrote:
>> (..)
>> I have been investigating poor MTD performance with a GD25 memory on
>SPI0 of a SAMA5D27 processor.
>> (..)
>> I am very happy to work on the fix and a PR after some feedback.
In this case, it's not the low level interrupt handler. It's essentially the
"callback" routine that's registered to the generic PIO irq handler. I think!
I had hoped that the actually irq state (edge/level/whatever) existed in a
struct/argument/whatever and I just hadn't spotted it.
I should b
I see that a build using upstream/master reports its version as 12.0.0, despite
being over 400 commits ahead of the official release (of course).
Is there an argument to have "master" report its version as "release+" or
something like that, e.g. "V12.0.0+", like U-boot does I believe?
Not actua
Thanks for the support - another 2 PRs submitted now.
But one failed tests with multiple instances of:
" Error: Error response from daemon: login attempt to https://ghcr.io/v2/
failed with status: 503 Service Unavailable"
Do I need to do anything to get the tests to rerun and hopefully pass?
>-
Some may have seen I've been attempting multiple times to submit PRs for 2
issues (SAMA5D2 related) and have closed/cancelled/retried numerous times.
Bottom line - I am struggling with the whole rebase/squash/merge cycle.as
I'm a complete numpty. Code I can (mostly!) do, but this is the first time
A year or 2 ago I added flexcom SPI support to the SAMA5D2 but was not
confident enough to submit it via PR, and then had to put the project down
for a while anyway. I'm back at it now, but I see that since then the
underlying support for the main SPI has been changed a little to use, for
example,
+1
>-Original Message-
>From: Nathan Hartman
>Sent: 22 November 2022 13:30
>To: dev@nuttx.apache.org
>Subject: Re: New names of repositories
>
>After hearing back from Infra about the repository naming convention, all the
>recent feedback has been to stay with the default and just remove
+1 :)
>-Original Message-
>
>nuttx and nuttxapps
>
I see all the other two-word Apache repositories use hyphens not underscores,
and on GitHub they are URLs which as has been pointed out should ideally be
hyphenated?
To me the underscore looks wrong...but, in the grand scheme of things, it's
just a name and, like Sebastien, I will not lose slee
In the midst (still!) of sorting out the SAMA5D2 TSD and ADC support. It is
pretty much all working now, with quite a few errors addressed along the
way. Guess I'm the only one actually using this processor for real LOL.
The last thing I am addressing is a conflict between the interrupts used for
I meant esp32 not esr32. The naming is too similar lol
> On 29 Oct 2022, at 15:51, Tim Hardisty wrote:
>
> Thanks Alan! SAMA5D2 has RMII so definitely a possibility. EFR32 is a much
> better value device compared to SiLabs Bluetooth 5 module currently used, and
> has WiFi as a bonus - so I wi
I had similar problems trying smart FS with a large device. It was over a year
ago, and I put it on the back burner at the time, but I am sure there was
something that exceeded the max value of a 16 bit integer somewhere and it went
wrong. To me it seemed like it wasn't suited to large devices "
Short term, I've cloned apache:master afresh, copied my new files to that, then
committed it to a new branch in my own fork. No idea if that's the right thing
to have done, but the PR is now live, at least!
>-Original Message-
>From: TimH
>Sent: 12 October
I have created 2 rst files to document out-of-tree custom boards, and also how
to manage custom apps both in and out of tree, and would like to submit a PR.
This will be the first time I have submitted a PR, and I'm fairly new to using
GIT and I'm struggling to understand the (documented) workfl
d along with the built-in apps and examples? This would allow you
>> to include custom appss, and the built-in ones, but not have a problem when
>> merging future releases that might cause the building in of the custom apps
>> to fail?
>>
>> Perhaps I'm over th
>From: TimH
>Sent: 07 October 2022 17:45
>To: dev@nuttx.apache.org
>Subject: RE: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
>
>>-Original Message-
>>From: Nathan Hartman
>>Sent: 07 October 2022 17:28
>>
>>On Fri, Oct 7, 2022 at
>-Original Message-
>From: Nathan Hartman
>Sent: 07 October 2022 17:28
>
>On Fri, Oct 7, 2022 at 11:10 AM TimH wrote:
>>
>> Would you still like another non-binding +1 vote?
>>
>> I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom boa
for
>custom out-of-tree boards (PR #7103)
>
>On Fri, Oct 7, 2022 at 11:59 AM TimH wrote:
>>
>> As per request below, I’m happy to add a paragraph or two regarding this,
>but I am not sure where it should go?
>>
>> It could be a section in “guides” or I could
directory usage that could either be a source of info for a more
complete “custom environment” guide or is the actually the intended place for
the custom boards info I’ve been asked to add?
TIA,
TimH
From: hartmannathan
Sent: 22 September 2022 15:00
@TimJTi <https://github.
Would you still like another non-binding +1 vote?
I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom board and
have successfully built and run a Nuttx shell (after a few changes to my custom
make.defs).
>-Original Message-
>From: Alin Jerpelea
>Sent: 22 September 2022 1
Thanks Alin - I'll wait then :)
>From: alin.jerpe...@sony.com
>Sent: 07 October 2022 14:51
>
>Hi Tim
>We are waiting for the IPMC vote so that we can release RC2 as final Best
>regards Alin
>
>
>From: TimH
>Sent: den 7 oktober 2022 15:48
>Have been wait
Have been waiting for 11.0.0 to be released so I can merge into my 10.3
efforts. I see 11.0 is on GitHub under releases, but when I start the merge,
files appear to be tagged with nuttx-11.0.0-RC2. I also don't recall seeing
an email here about the release.
Before I continue, can someone confir
I would think that your variable (a) does not meet the requirement of the &
operator (The operand of the address-of operator can be either a function
designator or an l-value that designates an object that is not a bit field and
is not declared with the register storage-class specifier.)
If so
t; OK.
> Here is a blog introducing running NuttX graphics on SAMA5D3 Xplained with
> LCD display driver.
> https://blog.csdn.net/oldman147/article/details/73410473?spm=1001.2014.3001.5502
>
>
> Best Rds
>
>> On Mon, Sep 12, 2022 at 10:45 PM TimH wrote:
>>
>
FYI I will start to get involved with release testing but I have too many
in-progress new drivers, and fixes to 10.3 , for my board and arch for it to be
viable at this time.
And I’m on holiday 🙂
Regards,
Tim.
> On 19 Sep 2022, at 10:53, alin.jerpe...@sony.com wrote:
>
> Please test this r
>-Original Message-
>From: Nathan Hartman
>Sent: 16 September 2022 12:37
>
>On Fri, Sep 16, 2022 at 7:33 AM TimH wrote:
>
>> >From: Nathan Hartman
>> >Sent: 16 September 2022 12:31
>> >To: dev@nuttx.apache.org
>> >Subject: Re: ADC d
>From: Nathan Hartman
>Sent: 16 September 2022 12:31
>To: dev@nuttx.apache.org
>Subject: Re: ADC device close and IRQ
>
>On Fri, Sep 16, 2022 at 7:20 AM TimH wrote:
>
>> Actually a little more complicated as the detach and disable in adc
>> close then kills th
Actually a little more complicated as the detach and disable in adc close then
kills the touch screen driver as well (it uses the ADC). l'll figure out a way,
I'm sure!
>-Original Message-
>From: TimH
>Sent: 15 September 2022 18:48
>To: dev@nuttx.apache.org
&g
Makes sense! I searched other drivers for where they called the detach but
didn't think to see where those other drivers called the attach!
Thanks :)
>-Original Message-
>From: Michal Lenc
>Subject: Re: ADC device close and IRQ
>
>Hi,
>
>> The easy option is to comment out the two calls
I have sorted the touchscreen on the SAMA5D2 - minor errors in the init code
"as supplied" meaning a couple of registers were not set up right.
I have also found that priority inheritance is needed, at least for the ADC
example app: I've not sat back or read my books to see why, but it works fo
uspended waiting for a count.
>
>So this sound like the thread is waiting for an event that never occurs.
>
>
>On Wed, Sep 14, 2022 at 11:23 AM TimH wrote:
>
>> Trying to get the touchscreen on my board registered and tested. It
>> *seems* to register, and at one random poi
org
>Subject: Re: build board from custom directory
>
>There is an option for relative links. The you can pass the path to
>configure.sh
>Like configure.sh ../boards/custom-board/config/nsh
>
>On Thu, Sep 15, 2022 at 12:25 PM TimH wrote:
>
>> A few weeks ago I moved
A few weeks ago I moved my custom board out of the NuttX
"nuttx/nuttx/boards" tree to a folder "nuttx/CustomBoards".
Make menuconfig allows you to specify that folder
(CONFIG_ARCH_BOARD_CUSTOM_DIR=)
To try and rule out .config errors for some issues I have at the moment I
did a make distcl
Trying to get the touchscreen on my board registered and tested. It *seems*
to register, and at one random point the touchscreen example app did report
something that looked useful but I now cannot make any sense of it.
The ADC itself is registered and the ADC example app works fine, but when I
now about sama5, but probably it is done here: arch/arm/src/armv7-
>a/
>
>On 9/13/22, TimH wrote:
>> I will probably hit send then find it.but, right now, I can't see if
>> there's anything I need to do to enable DCACHE?
>>
>>
>>
>> My .confi
I will probably hit send then find it.but, right now, I can't see if there's
anything I need to do to enable DCACHE?
My .config has CONFIG_ARCH_DCACHE set, and that seems to "enable" all the
various cache functions, including up_enable_dcache, but I can't find any
calls to that function in sama
gt;D4 (which was based on the D3).
>
>On Mon, Sep 12, 2022 at 8:30 AM TimH wrote:
>
>> Aargh...too quick to retract. I think definitions for ATSAMA5D3 and
>> ATSAMA5D4 are swapped and there *may* be inconsistencies, based on a
>> comparison to datasheets. I don't think
t;-Original Message-
>From: TimH
>Sent: 12 September 2022 14:54
>To: dev@nuttx.apache.org
>Subject: RE: SAMA5D3 and D4 DMA
>
>Scrap that for now - was looking in the dma not xdma files
>
>>-Original Message-
>>From: TimH
>>Sent: 12 September 2
Scrap that for now - was looking in the dma not xdma files
>-Original Message-
>From: TimH
>Sent: 12 September 2022 14:14
>To: dev@nuttx.apache.org
>Subject: SAMA5D3 and D4 DMA
>
>I am reworking DMA to get it working for the SAMA5D2. It seems to me that
>t
I am reworking DMA to get it working for the SAMA5D2. It seems to me that
there are also errors and inconsistencies in the DMA code for the SAMA5D3
and D4 family.
For now I have added "# warning" pre-processor statements. I have no means
to check ATSAMA3 or ATSAMA4 devices - so unless someone c
>From: Nathan Hartman
>Sent: 09 September 2022 12:50
>To: dev@nuttx.apache.org
>Subject: Re: SAMA5D2 DMA
>
>> Rather than clutter sam_xdmac.h with loads of #if defined (SAMA5D2)
>> stuff would it be better to deal with this in the same way as the
>> memory and pinmap files, etc, and have:
>>
>> _s
>From: TimH
>Sent: 07 September 2022 12:14
>
>A quick dabble with DMA for the SAMA5D2 chip I'm using suggests the native
>NuttX support for this is incorrect and probably applies to SAMA5D3 chips
etc.
>There are refences in sam_xdmac.c to PIDS that simply don't exist i
Apologies for the long post, but given the absence of many/any voltage
regulator drivers - especially PMICs - I feel I need to get this all sorted and
agreed. So I have looked long and hard at the Nuttx files and Linux
documentation and to see if I have got it right I would like to see if the
f
Please correct me if I'm still missing something, as there are zero
>> clues I can find as to what each ops function (for example) is
>> actually supposed to do.
>>
>>
>>
>Here is two examples:
>https://github.com/apache/incubator-
>nuttx/blob/master/drivers/power/supply/regulator_gpio.c
>http
Looking further, I'm thinking that this driver template has never been used, is
undocumented, and is therefore bordering on unusable.
Please correct me if I'm still missing something, as there are zero clues I can
find as to what each ops function (for example) is actually supposed to do.
>From: Xiang Xiao
>Sent: 07 September 2022 13:40
>
>On Wed, Sep 7, 2022 at 8:13 PM TimH wrote:
>
>> >From: Alan Carvalho de Assis
>> >Sent: 06 September 2022 13:51
>> >I think for ACT8945A should be included a regulator at
>> drivers/power/supply
>From: Alan Carvalho de Assis
>Sent: 06 September 2022 13:51
>I think for ACT8945A should be included a regulator at drivers/power/supply/
>and will implement the functions from and will
>register itself with regulator_register().
Sorry for the dumb question, but do I use regulator.c directly, o
A quick dabble with DMA for the SAMA5D2 chip I'm using suggests the native
NuttX support for this is incorrect and probably applies to SAMA5D3 chips
etc. There are refences in sam_xdmac.c to PIDS that simply don't exist in
the SAMA5D2.
Can anyone confirm - or correct me if I'm wrong?
, it just assumes the device is there in the SPI/I2C bus and
>don't try to talk with it and goes on creating the device file. It makes the
>file of
>user hard because he see the device at /dev and think that everything is fine.
>
>BR,
>
>Alan
>
>On 9/6/22, TimH wrote
tchr.c to avoid mixing things and will export itself as
>/dev/bat0.
>
>But you will need to use spinlock when accessing the I2C bus inside these
>drivers to avoid both drivers trying to use it while a transfer is in progress.
>
>BR,
>
>Alan
>
>On 9/6/22, TimH wrote:
I'm writing a driver for the Quorvo ACT8945A device. This is a combined
7-output programmable regulator AND Li-ion battery charger, all in one.
I see there are existing "regulator.h" and "battery_charger.h" driver
templates.
Would my best approach to be to create a driver using a new (e.g.)
benign in 10.2 and not in 10.4.
Working again on Minicom with either readline or CLE.
Back to development now...until 11.0 comes along and I go through it all again
lol.
>-Original Message-
>From: TimH
>Sent: 18 August 2022 10:59
>To: dev@nuttx.apache.org
>Subject: RE: 10.3 merge
>-Original Message-
>From: Gregory Nutt
>Sent: 17 August 2022 19:16
>To: dev@nuttx.apache.org
>Subject: Re: 10.3 merge issues
>
>
>>
>> It all boots and I get the nsh prompt but I get continuous:
>>
>> nsh_session: cle failed: 22
>>
>> I'm assuming that's EINVAL, but I can't work out why?
>-Original Message-
>From: Nathan Hartman
>Sent: 18 August 2022 03:01
>To: dev@nuttx.apache.org
>Subject: Re: 10.3 merge issues
>
>On Wed, Aug 17, 2022 at 3:27 PM Tim Hardisty wrote:
>
>> I realise, now, I compared mine against 10.2 variants not 10.3...not
>> sure why, but there you go.
Re: 10.3 merge issues
>
>Hi Tim,
>
>Try to compile with verbose enabled:
>
>$ make V=1
>
>Probably your board is bringing some older definition that is causing a
>variable
>to be created incorrectly, because "-T/something" doesn't appear a val
Yes - I have CONFIG_NSH_CLE defined.
There are no .o files after a make clean
>-Original Message-
>From: Nathan Hartman
>Sent: 17 August 2022 19:10
>To: dev@nuttx.apache.org
>Subject: Re: 10.3 merge issues
>
>On Wed, Aug 17, 2022 at 12:56 PM TimH wrote:
>>
>-Original Message-
>From: Gregory Nutt
>Sent: 17 August 2022 19:16
>Subject: Re: 10.3 merge issues
>
>
>> 1. Final change that allowed a compile was when I changed the defconfig
>> to have the new:
>>
>>
>>
>> CONFIG_INIT_ENTRYPOINT="nsh_main"
>>
>> CONFIG_INIT_ENTRYNAME="nsh"
>>
>>
>>
Hi All,
My project has been in hibernation for 6 months for personal reasons but
today was the day I fired the custom board up again to restart porting work.
My 10.2-based "in progress" work behaves as before (which was a relief) so I
decided I would merge in 10.3 to make sure I restarted w
I've been aware that some of my emails haven't got through to people on
this list and, also, that I have not been getting every email from others.
Checking our mail server logs it would seem that any email from a sender
whose mail server uses DKIM is likely to be rejected by recipient
servers
figs/rndis/defconfig
boards/arm/stm32/stm32f4discovery/configs/rndis/defconfig
BR,
Alan
On 1/25/22, TimH wrote:
First attempt hasn't worked, but not I've investigated or checked my
.config yet; but, before I do, is it reasonable to expect NuttX to
support DHCP server and USB RNDIS such
First attempt hasn't worked, but not I've investigated or checked my
.config yet; but, before I do, is it reasonable to expect NuttX to
support DHCP server and USB RNDIS such that a connected PC gets an IP
address from the NuttX RNDIS "gadget" allowing connectivity without the
PC user having to
Definitely an option!
Still need a good way to get data on and off easily from
Windows/Linux/Mac but a copy-on-write type file system is more than
adequate for this product - thanks for the suggestion :)
On 22/01/2022 16:48, Tomasz CEDRO wrote:
Maybe LittleFS? Embedded, wear level and power
Now I have RNDIS working on Windows (Linux a work-in-progress) I am back
to thinking of the best way forward. If anyone has further thoughts on
the following I'm very interested:
- FAT/MSD/USB. Still seems the easiest for the customers (think
consumer, not necessarily tech-savvy), but FAT i
Are there any implementations of MTP using NuttX, or that could be
easily and legally ported?
On 19/01/2022 18:54, Frank-Christian Kruegel wrote:
Am 19.01.2022 um 19:40 schrieb TimH:
- an external PC (ideally Linux, Windows and MAC) needs to be able "see"
the data via USB (msd) and
esn't work fine
yet.
On 1/21/22, TimH wrote:
I guess I can try it on WSL too, but I'll also set up my Linux machine
to dual boot 20.04 and 18.04. All part of the "Tim gets to grips with
Linux" life experience :)
On 21/01/2022 16:30, Alan Carvalho de Assis wrote:
Hi Tim,
did you
I guess I can try it on WSL too, but I'll also set up my Linux machine
to dual boot 20.04 and 18.04. All part of the "Tim gets to grips with
Linux" life experience :)
On 21/01/2022 16:30, Alan Carvalho de Assis wrote:
Hi Tim,
did you try other Linux distro? Maybe it could be some incompatibil
Nope, doesn't show. So RNDIS is not working right on my board. What a
surprise!
On 20/01/2022 19:30, Alan Carvalho de Assis wrote:
Exactly, knowing Unix/Linux makes your live easier with NuttX.
Using "ip list" (or ifconfig) on Linux should display the new USB
RNDIS interface.
BR,
Alan
At home now, but don't recall USB settings of any sort there, just the
wired Ethernet adapter of my machine. I set that to the same subnet but
that's irrelevant. ifconfig on the Linux machine didn't show a USB
adapter, from memory.
I'll have to hunt around for USB adapter settings - they're pr
FAT seems broken for NOR flash devices. Spent days getting nowhere.
Since FAT and flash devices don't really play well together anyway
(already found s512 erases a flash sector at least 4 times when writing
a cluster), so I'm wondering, in parallel, if NuttX has other tricks up
its sleeve that
On 22/12/2021 15:55, Alan Carvalho de Assis wrote
This is why I always suggest to people getting started to NuttX to
create some blogs post to document their progress and discoveries, it
will pave the new to all new users.
If I want to share what I'm doing with the details of the project etc,
w
This is a custom board (SAMA5D27-D5M). I suspect what has happened is
that multiple "messing around" with configs has broken something basic.
To add insult to injury I have messed it all up so badly that the apps
directory won't compile in properly either now.
I will take your advice and retu
On 01/12/2021 18:08, Nathan Hartman wrote:
On Wed, Dec 1, 2021 at 11:29 AM Tim wrote:
OK, thanks - should have thought to check for any updates - sorry.
Yes, still got the 10.1 tree I think it is, from 7 or 8 months. Will need
to do whatever I need to do to get the latest but not a priority ri
On 20/11/2021 13:40, TimH wrote:
Hi,
I'm adding arch support for the sama5d2 Class D audio peripheral.
This has bass cut/boost and treble cut/boost capabilities which don't
fit (as best as I can tell) with the current set of audio driver
capabilities and are, quite probably, uniq
Hi,
I'm adding arch support for the sama5d2 Class D audio peripheral.
This has bass cut/boost and treble cut/boost capabilities which don't
fit (as best as I can tell) with the current set of audio driver
capabilities and are, quite probably, unique to this device and not
applicable to others
Hi Alan,
Thanks for the suggestion - I have GDB and J-Link and am using VS Code
as my IDE, which does have some "watch" limitations it seems :(
But I have found I was wrong about it being NuttX that's changing the
SFR register. It seems that U-boot doesn't set it despite being
configured for
My view on this...bit of a ramble.
I'm new to Nuttx, and have a new/custom board I'm porting it to. Nuttx
didn't play nicely/easily with either Windows or MAC for me and I
eventually went to Linux; and have no regrets as life is so much easier
as result. A full build takes no more than 10secon
On 07/06/2021 17:22, Tim wrote:
This is probably not really a NuttX question per se, but it relates to
getting the MCAN interface for a sama5d2 to work properly. And you are all
such knowledgable and helpful people :)
The MCAN controllers assume the base address of the message ram is at
0x2
eating an #ifdef for each board inside your driver is not a good/right
solution.
You can use some GPIO_CANXYZ_EN_PIN in your driver and inside your board
you #define GPIO_CANXYZ_EN_PIN GPIO_PIN_Px
BR,
Alan
On Sunday, May 30, 2021, TimH wrote:
Hi all,
My custom board has a number of GPIOs
Hi all,
My custom board has a number of GPIOs that are related to more generic
drivers. For example, the CAN implementation uses an arch. CAN driver
appropriate for the processor, but has custom GPOs associated to
enable/disable the CAN transceivers, and to enable/disable termination
resistor
84 matches
Mail list logo
