nd a driver will be
needed, is a generic Linux driver a good place to start were I to look to
add/create one to NuttX? Or maybe someone has already done this?
Thanks,
Tim.
> Am 24.03.2021 um 18:34 schrieb Tim:
>
> > I can also build in Bluetooth support and the demo app, but as far as
> > I can tell there are no actual Bluetooth host drivers in NuttX to
> > properly support a detected Bluetooth device. My custom board actually
> > ha
> Hi Tim,
>
> It depends on what you refers to Bluetooth: is it Bluetooth Classic or BLE ?
>
> If you want BT BLE maybe it is better to use a MCU with BLE.
>
Thanks Alan
Bluetooth LE, which is why I put a SiLabs module on the board and have it
working, but thought "
> >> Hi Tim,
> >>
> >> It depends on what you refers to Bluetooth: is it Bluetooth Classic
> >> or BLE ?
> >>
> >> If you want BT BLE maybe it is better to use a MCU with BLE.
> >>
> >
> > Thanks Alan
> > Bluetooth
d? Be kind
to me :)
Thanks,
Tim Hardisty
On Wed, Apr 21, 2021 at 9:04 AM Tim > wrote:
>> I am in need of a driver for an FUSB301 USB C Controller/PD device. I see
>> there are drivers for the FUSB301 and FUSB303 but not the FUSB302.
>>
>>
>>
>> Before I have a stab at porting the outline code
> > Thanks Nathan. I only found this reply on the mail archives - I never
> > had a notification of a reply for some reason :(
>
> Are you subscribed to the mailing list?
I got this reply and see many other emails coming in, and unsubscribe from most.
>> Perhaps something is misconfigured -- loo
oard-specific
code (sam_can.c) I am using is based on the code for the sama5d2-xult board
and seems pretty trivial, and largely similar to many other architectures
and boards.
Many thanks,
Tim.
Pulling my hair out here!! So apologies for the lengthy brain dump and plea
for help!
All this starts from the CAN init code crashing (SAMA5D27) when it makes any
call to print debug messages. Printf itself is fine.
I need to debug it. I will need to get to that point regardless.
The on
>From: Gregory Nutt
>Sent: 11 May 2021 18:33
>
>> All this starts from the CAN init code crashing (SAMA5D27) when it
>> makes any call to print debug messages. Printf itself is fine.
>These kinds of crashes are often due to stack overrun. It might be worth
>increasing the stack size of the task t
>Brennan Ashton Tue, 11 May 2021 13:12:50 -0700 wrote
>So back to your root issue, you said you were having issue setting
>breakpoint and getting that to line up with the code, did you enable the
>debug symbols in menu config?
Yes:
- Enable Debug Features checked
- Enable Error Output checked
- E
> Disruptive Solutions Tue, 11 May 2021 09:50:53 -0700 wrote
>Maybe I can try to help you concerning this matter. How can we
>connect? Do you have telegram?
WhatsApp, Signal, email, FB Messenger...but not Telegram :) Email me if you
like and we can go from there - guess you will need to remove t
Further to my question relating to the CAN example crashing I have found
that the issue is more generic.
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().
2) Any (valid and enabled) call for a debug info/war
nation, but is this documented anywhere? Can't find that level of
syslog stuff using make menuconfig?
Also now, at least, I know that the board is crashing in can_hwinitialize when
it calls can_putreg(priv, SAM_PMC_PCR, regval)...so next week's task is to find
out what's up wit
tasheet
section on this at all!)?
Thanks!
Tim.
ithub, along with some notes that may assist anyone
else using this family in the mean time? Or just wait until it's all done
and dusted and do my PRs in one hit with/without raising them as actual
issues? Can't find guidance on this in the "Contributing" notes.
TIA, Tim.
Thanks for everyone's help on this. All working now.
It transpires the msgram can be in SDRAM not just in ISRAM so the solution is
much more like the samV71 using cached memory, but it is handled a little
differently in a few places of course.
No thanks AT ALL to the Atmel datasheet which says:
this.
Any suggestions of how to find where/why/how this is being changed?
Thanks,
Tim.
An earlier screen shot showed a compiler warning for the function being
implicitly declared - so no lower driver function is actually present/included?
Surprised it's just a warning though.
>-Original Message-
>From: Alan Carvalho de Assis
>Sent: 18 August 2021 12:38
>To: dev@nuttx.apac
need to (auto)mount it in my bringup or app
init code, but I'm stuck :(
"CONFIG_HAVE_M25P" is as far as I have got.
SAMA5D27 device.
TIA,
Tim.
environment variables with no issue, but I can't
find the way to either mount it, or "probe" it, or anything, from nuttx. It
doesn’t appear as a /dev.
No doubt it's in some documentation somewhere
>
>On 8/24/21, Tim wrote:
>> Does anyone have any pointers
Hi Alan,
>Hi Tim,
>
>On 8/24/21, Tim wrote:
>>
>>>Then before try to setup the NXFFS you need to confirm that the Flash
>>>NOR was detected correctly.
>>
>> How, in code or from the nsh, do I do that? I know the chip works as
>> I've use
The more time I spend with nuttx the more I think I just haven't found some
treasure trove of documentation somewhere. All I seem to end up doing is
searching every single file for some kind of clue as to what to do!
I have an SPI EEPROM device. Menuconfig allows me to set it up, lovely! I
end
No, it's not in the system map. Having now searched for it I see there's a
possibly useful example in stm32_appinit.c so I will wade through that.
How was I supposed to know what to look for!!??
>Ok, did you open your System.map and searched for m25p_initialize() ?
>
>Few days ago I gave someone
There is support for MT25Q128 and I have now added the MT25Q256
It is in nuttx/drivers/mtd/m25px.c and I will add to the list of PRs once I
have everything sorted on my board.
Subject: Re: nxfss on MT25Q nor flash
BTW, do we have a driver for MT25Q? I can't see one. Is it compatible wit
I seem to have got over most of my SPI flash and EEPROM issues now and my
256Mb SPI flash is properly recognised.
I think I am at the last hurdle. Here is the console output, along with my
question of the day :)
Successfully initialized M25P SPI
m25p_initialize: dev: 0x2005b970
m25p_readi
Emails from Sara have not come through, or are garbled, I don't understand why.
So I can't quote and have had to look at the archives. Mine get tagged as if my
email is "INVALID", which it isn't. Sigh.
But...I had a typo in the "mount" call and had "nxfss" rather than "nxffs" (I
didn't copy/pas
this if I'm missing something! A
search through all files suggests flexcom SPI has only been done for NXP
LPC54x processors.
Thanks,
Tim.
board_ioctl commands are
>> relevant as it is chip specific not board specific.
>>
>> This could be a case of I'm the only one who ever wants to expose this
>> so I could go down that route but assuming it's not technically the
>> right approach, what is, pl
Thanks David - I saw that my emails are in the archive but since my email
address always seems to get a .INVALID suffix applied in the From: field
(really got no idea why!) I was not 100% sure they were being
distributed/reflected reliably.
>Hi Tim,
>
>Emails are getting to the list.
ations are doing my head in at the moment lol.
>-Original Message-
>From: Alan Carvalho de Assis
>Sent: 22 November 2021 12:45
>To: dev@nuttx.apache.org
>Subject: Re: Custom audio capabilities
>
>Hi Tim,
>
>Since some audio codec supports these features, I think t
>On 11/22/21 5:38 AM, Tim wrote:
>> My thinking now is perhaps to add some sub-feature #defines (e.g.
>>AUDIO_FU_SUBEQUALIZER_BASS_BOOST_PLUS6) to be used as subtypes when
>>capabilities are queried for AUDIO_TYPE_FEATURE and for the audio_configure
>>function to make
There are some drivers for the OnSemo USB C FUSB301 and FUSB303 devices
available in the NuttX tree, and they will make a good basis for me to
create a driver for the FUSB302 device I chose to use.
But there's a copyright notice in each saying:
* Copyright (C) 2019 Haltian Ltd. All rights reser
/pull/4831
>https://github.com/apache/incubator-
>nuttx/blob/master/drivers/usbmisc/fusb301.c#L1-L19
>
>On Wed, Dec 1, 2021 at 5:08 PM Tim wrote:
>>
>> There are some drivers for the OnSemo USB C FUSB301 and FUSB303
>> devices available in the NuttX tree, and they will ma
My POSIX knowledge is still somewhat limited, but I believe it's this:
https://nuttx.apache.org/docs/latest/reference/user/07_signals.html
>-Original Message-
>From: Swapna Iyer
>Sent: 09 December 2021 17:25
>
>Is there any example I can look at?
>
>Swapna Iyer
>swa...@lightmatter.co
>
>
attach).
If anyone can point me in the right direction I'd appreciated it!
Tim.
is, um, scary!
I'm hoping I've just not configured something else it needs; and I can't
seem to find any relevant debug options to assist - USB MSC MM DEBUG seems
to cause it all to hang up at a printf statement in the msconn app.
Any thoughts, kind people?
Thanks, Tim.
mental stuff that, to me, just "should work"
quite often doesn't :(
Thanks,
Tim.
>-Original Message-
>From: Alan Carvalho de Assis
>Sent: 22 December 2021 12:22
>To: dev@nuttx.apache.org
>Subject: Re: USB MSD problem
>
>Hi Tim,
>
>I don't
>Here the issue is your ramdisk size. You need at least 64 sectors to be able to
>format as FAT, try it:
>https://acassis.wordpress.com/2020/08/23/how-to-use-ramdisk-as-filesystem-
>on-nuttx/
That is the guide I followed Alan:
nsh>mkrd 64
nsh>ls /dev
/dev:
console
null
ram0
ttyFC0
ttyFC1
tt
>
>Try to spot the exact place where it is happening, also enabling the DEBUG FS
>could help to spot issues.
Well, here's an odd thing.
I already had FS debug on of course, but not the informational output. Turn
that on, and I can now actually create a FAT volume on /dev/ram0.
Cannot explain t
>Tried running msconn with /dev/ram0 but it still crashes.
>
>It *seems* to be printf statements in the msconn system app itself!!??
>
Comment all the printf statements out of msconn and it runs...but it now
crashes during nxtask_exithook().
This SCREAMS of a basic nuttx RTOS/THREAD/SOMETHING con
Usb_msc_main.c
If I add a "return OK" as the first line of main, msconn runs and returns.
If I put a printf statement before it, I get a crash.
If I do the same in an example app I've written, it is fine.
If I put a breakpoint at the printf statement and step over it, into there it
gets to "vo
Update on my issues.
msconn crashing was, as suggested, inadequate stack size. Default was 768, and
changing to 2048 and it no longer crashes. This was my first experience of
stack issues with NuttX.
I have now merged the 10.2 release and building and running OK.
Msconn now allows my board to
>Any thoughts, anyone?
Stack again. Not enough for the main thread. Guess I need to go back to school
to learn about stacks :(
Yep, me again!
USB device is working. I can create a ram disk, format it as FAT, set it as
a LUN device and Windows and Linux see it as an MSD device. I can read and
write to it, reliably.
I have an MT25QL256A device (32Mbyte) which is correctly connected to the
SAMA5D17 via SPI0, has a block dr
er the first 16k boundary on the msd.
I don't think this is FAT12 vs FAT16.
Uboot tests show this memory is OK. I have ordered a 1Gbit device to try (in
case the device on this board is damaged, or NuttX just doesn't like 256Mbit
M25P devices for some reason!!).
But still hopeful of s
As I still get deeper and deeper into why FAT doesn't work on my MT25Q NOR
flash device, I have found a minor error in m25px.c
The M25P devices have a bulk erase command (0xC7) but this is not supported
by the MT25Q, which has a "die erase" command (0xC4) instead and 0xC7 is
meaningless.
There is
>-Original Message-
>From: Arie de Muijnck
>Sent: 19 January 2022 22:34
>> 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
>> writ
>emails are not always coming through to the mailing list... So re-sending.
>
This happens a lot for me too. I always check
https://www.mail-archive.com/dev@nuttx.apache.org/ to see if I've missed
anything.
Following suggestions relating to FAT/MSD/USB I have been playing with RNDIS
following the NuttX Channel video by Alan C. de Assis (thank you Alan -
only just found all of your videos!!).
It all builds OK and ifconfig suggests all is good:
nsh> ifconfig
lo Link encap:Local Loopback at UP
>From: Tim Hardisty
>Sent: 21 January 2022 11:15
>[ 3399.339551] rndis_host 1-2:1.0: dev can't take 1558 byte packets (max
>1364), adjusting MTU to 1306
Easily fixed:
CONFIG_NET_ETH_PKT_SIZE=1518
But RNDIS still doesn't work, having checked every option I can find.
W
telnet from Windows.
Linux remains an issue, but I'm looking at whether there are any RNDIS driver
updates for Ubuntu or something like that.
But, for once, I at least have *something* working :)
>-Original Message-
>From: Tim
>Sent: 21 January 2022 14:14
>To: dev@nuttx.ap
Just a "thumbs up" from me if you do this (or find something that exists
that'll do it) - it's a perfect fit for my current project :)
>-Original Message-
>From: Matthew Trescott
>Sent: 17 March 2022 05:55
>To: dev@nuttx.apache.org
>Subject: Abstract "channels" driver model
>
>Hi everyon
I am sorting out flexcom support for the SAMA5D2 as there are issues with the
arch files as well as Kconfig. In doing so, I would like to do it “right”.
If flexcoms are assigned as USARTs is the correct philosophy to register them
sequentially or as per flexcom port number? For example, if (o
Thanks Alan - those are already set but don't seem to produce any output on the
console so may be the error output itself isn't configured right. I'll take a
look.
On 07/05/2021, 18:49, "Alan Carvalho de Assis" wrote:
>Hi Tim,
>Try to enable the debu
>> Is there any description somewhere about this example ?
>>
>There is some in apps/examples/README.md, but not a lot of info.
Not much, no, but the example code is pretty self-explanatory!
ee on the Windows
side perhaps. It is a few more things to try at least, so thank you.
>Hi Tim,
>
>I don't use Windows or MacOS, but some time ago just tested NuttX on
>WSL to help other to get started to NuttX on Windows, I documented the
>proc
sted NOT fixing it!) and I had thought it time to
jump ship to Mac...but Linux seems even more appealing right now!!
On 11/05/2021, 18:24, "Flavio Castro Alves Filho"
wrote:
Hello Tim,
What I do here to implement a NuttX application is to use an Ubuntu
Server VM (in my ca
I have the board booting from AT91bootstrap and Uboot, from QSPI no problem.
Downloading code using JLink from Windows/eclipse is fine, but the debugging is
broken/mis-configured. I will probably have another go at a Windows-hosted
development environment and have the arm cross compilers install
Hmm...do need Windows for my schematic capture and 3D design applications, but
Mac little used as yet...I'm thinking dual boot Mac/Ubuntu is probably the way
to go!
On 11/05/2021, 20:30, "Alan Carvalho de Assis" wrote:
Also, if you are not dependent on Windows, just install Linux on your
I see from https://www.mail-archive.com/dev@nuttx.apache.org/ that others have
replied. These have not got through to me so apologies for not yet taking up
the offers of assistance.
I will try and sort whatever the email issue is and then reply!
>From: Alan Carvalho de Assis
>
>Did you enable CONFIG_DEBUG_CAN_INFO in your menuconfig?
>
> │ -> Build Setup
> │
> │ -> Debug Options
> │
> │ -> Enable Debug Features (DEBUG_FEATURES [=y])
> │
> │ -> CAN Debug Features (DE
>On 5/12/21, Tim Hardisty wrote:
>>>From: Alan Carvalho de Assis
>>>
>>>Did you enable CONFIG_DEBUG_CAN_INFO in your menuconfig?
>>>
>>> │ -> Build Setup
>>> │
>>> │ -> Debug Options
>>
>>From: disruptivesolution...@gmail.com
>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?
Nope, nothing. It simp
s
at my disposal. And once fixed and proven I will then work out how to do
pull requests to get the fixes made available...I'm nearly coding in the
21st century now lol.
On 21/05/2021 20:51, Flavio Castro Alves Filho wrote:
Hello Tim,
I use VSCode with GDB and Segger.
But Ubuntu doe
On 07/05/2021 17:48, Tim wrote:
Hi,
SAMA5D27 (custom board) - trying to complete the port and also check that
the CAN interface works on the board, so I'm trying to use the CAN example
app
As per my other thread, Linux+VS Code+Segger all up and running so I can
see what'
On 07/06/2021 20:45, Gregory Nutt wrote:
I will, I believe, need to declare - place - MCAN related structures
such
that they (or at least some elements of them) are in SRAM.
You will need to exercise care. SRAM (called isram in the linker
scripts) is already used for other things including
On 07/06/2021 19:06, Nathan Hartman wrote:
On Mon, Jun 7, 2021 at 12:24 PM Tim wrote:
I will, I believe, need to declare - place - MCAN related structures such
that they (or at least some elements of them) are in SRAM.
Yes. It is possible. It is done by adding attributes in the code which
lash.ld#L179-L184
You can check it the arm-none-eabi-nm -C nuttx.elf | grep g_mcan0_msgram
David
-Original Message-
From: Tim Hardisty [mailto:t...@jti.uk.com]
Sent: Tuesday, June 08, 2021 4:23 AM
To: dev@nuttx.apache.org
Subject: Re: Memory locations
On 07/06/2021 19:06, Nathan Har
lash.ld#L179-L184
You can check it the arm-none-eabi-nm -C nuttx.elf | grep g_mcan0_msgram
David
-Original Message-
From: Tim Hardisty [mailto:t...@jti.uk.com]
Sent: Tuesday, June 08, 2021 4:23 AM
To: dev@nuttx.apache.org
Subject: Re: Memory locations
On 07/06/2021 19:06, Nathan Har
On 08/06/2021 14:18, Sebastien Lorquet wrote:
what I would check here (just a live thought process)
* check that the ld file is actually used (ld file is pointed by main
Make.defs IIRC) (easy: just add garbage in it and verify build actually
breaks)
You, sir, have earned the cigar! Garbage
My custom board has a Lin/K-Line interface using a TJA1021 transceiver, but
software support is low on the priority/roadmap at this time.
Nevertheless, I would be happy to be involved in testing (I have a CAN/LIN
analyzer/stream generator) if it helps.
-Original Message-
From: Pavel Pi
? Documentation on audio support in general seems rather
lacking so any pointers in the right direction would be appreciated (even just
a suggestion of another processor with similar capability I can use as a
reference).
TIA,
Tim.
=y
./sama5d4-ek/configs/nsh/defconfig:CONFIG_DRIVERS_AUDIO=y
./sama5d4-ek/configs/nxwm/defconfig:CONFIG_DRIVERS_AUDIO=y
These, however, used I2S for interface to an WM8904 DAC.
On 8/19/2021 12:41 PM, Tim Hardisty wrote:
Working through the remaining driver support I need for my custom
That’s AT24 I2C not AT25 SPI EEPROM unfortunatel, and from a quick look it
“just worked” ☹
From: Alan Carvalho de Assis
Reply to:
Date: Tuesday, 24 August 2021 at 18:01
To:
Subject: Re: SPI EEPROM
Hi Tim,
You are right, Documentation is one of our "Achilles tendon"
is not aimed at you, Alan, as I know you are trying hard to help.
From: Alan Carvalho de Assis
Reply to:
Date: Tuesday, 24 August 2021 at 19:42
To:
Subject: Re: SPI EEPROM
Hi Tim,
The process to get AT25 SPI is similar, but for SPI you need to get
the CS pin configure besides
AT24 is I2C and this is well supported in NuttX. AT25 is SPI and is what I have
(AT25128) and it is not well supported, with no example code or boards that
support it (that I can find)
From: Gregory Nutt
Reply to:
Date: Tuesday, 24 August 2021 at 20:11
To:
Subject: Re: SPI EEPROM
Thanks Vadim – that’s pretty much the conclusion I had come to.
Tim.
Subject: Re[2]: SPI EEPROM
Hi Tim,
You could search for any spi device being initialized. Search for spi_dev_s
being declared in boards folder for some board, use it as an example and do the
same
Thanks Alan – all my SPI pins are configured. That was easy to work out :)
I will follow this tomorrow and I’m sure it will all seem easier in the morning!
From: Alan Carvalho de Assis
Reply to:
Date: Tuesday, 24 August 2021 at 20:59
To:
Subject: Re: SPI EEPROM
Hi Tim,
It is very
That isn't quite right, Alan, as the mtd at25_initialize routine is for
SPI FLASH not SPI EEPROM - it tries to read an ID.
I have replied to my other thread with the solution for AT25 SPI EEPROM,
for others to refer to if they want
On 24/08/2021 20:59, Alan Carvalho de Assis wrote:
H
how to "automount"
my SPI flash as a file system - maybe SMART or maybe MXFSS; right now,
any file system mounting from my board or app init function would be good :)
On 24/08/2021 16:53, Alan Carvalho de Assis wrote:
Hi Tim,
It seams like MT25Q uses the m25px.c driver, so I assu
out over USB or Bluetooth LE,
on an occasional basis.
One file open for write is fine with what I currently envision, but who knows.
SmartFS has much appeal as a “just in case”. I have more DRAM than I know what
to do with :)
Tim.
From: Ken Pettit
Reply to:
Date: Wednesday
years ago!.
You have provided the “magic bullet” I need, and I am confident I will now get
it working quickly in the morning.
Tim.
From: Gregory Nutt
Reply to:
Date: Wednesday, 25 August 2021 at 18:14
To:
Subject: Re: which filesystem?
m25p_initialize() does not generate a
I am only just getting the point of having the luxury to think about what FS to
use lol. My 1st thought was indeed FAT and USB MSD for sure…but I made the
randome decision to put a USB-C connector and FUSB controller on the board and
haven’t got that working yet.
The beauty of NuttX is it gi
Cunha Monteiro de Souza
Reply to: "dev@nuttx.apache.org"
Date: Wednesday, 25 August 2021 at 19:15
To: "dev@nuttx.apache.org"
Subject: Re: which filesystem?
Em qua., 25 de ago. de 2021 às 15:12, Sara da Cunha Monteiro de Souza <
saramonteirosouz...@gmail.com> escre
Today's dumb question!
Having got a mounted nxffs spi flash "drive", I had a quick try earlier today
to store some data.
If I did:
nsh> ls > /mnt/flash/file1.txt
there was a major crash.
If I enabled the startup scan it sat there for 20+ minutes before I gave up and
halted it (it was still d
(no insult intended…naffs was a typo!)
From: Tim Hardisty
Today's dumb question!
Having got a mounted nxffs spi flash "drive", I had a quick try earlier today
to store some data.
If I did:
nsh> ls > /mnt/flash/file1.txt
there was a major crash.
What sort of agenda, or purpose, Alan?
Sounds like a good idea but some suggestion of what to expect would be good :)
On 22/09/2021, 18:20, "Alan Carvalho de Assis" wrote:
Dear NuttXers,
We want to do monthly meets with our developers and users.
The first online meet will be t
Needs a LinkedIn login?
From: Alan Carvalho de Assis
Reply to: "dev@nuttx.apache.org"
Date: Friday, 24 September 2021 at 20:20
To: dev
Subject: Poll: Which OS are you using to compile NuttX?
Hi Everyone, Please help us to discover which OS people are using most to
compile NuttX:
https://ww
nding.
BR,
Alan
On 9/24/21, Russell Haley wrote:
> The link gives me “This post cannot be displayed”. I am logged into the
> Microsoft data collection site known as LinkedIn.
>
> Sent from Mail for Windows
>
> From: Tim Hardisty
> Sent
On 22/12/2021, 20:15, "Alan Carvalho de Assis" wrote:
>On 12/22/21, TimH wrote:
>> On 22/12/2021 15:55, Alan Carvalho de Assis wrote
>> If I want to share what I'm doing with the details of the project etc,
>> where might you suggest I do this?
>If you want share your progres
Yes, I now think so. I know I looked at stack settings but (without benefit of
access to my Linux work machine from home) if I recall they are spread around
the place and I suspect - from other advise here - that it is the app stack
size that is inadequate.
Hopefully a break from it all will ma
sure there are
no regressions.
Thank you,
Sebastien
Le 18/01/2022 à 16:41, Tim a écrit :
As I still get deeper and deeper into why FAT doesn't work on my
MT25Q NOR
flash device, I have found a minor error in m25px.c
The M25P devices have a bulk erase command (0xC7) but this is not
s
Thanks Alanm - my lack on Linux knowledge failed me again. Never used
dmesg...luckily I like learning lol.
From Linux machine:
[ 3399.181365] usb 1-2: new high-speed USB device number 21 using xhci_hcd
[ 3399.337980] usb 1-2: New USB device found, idVendor=584e,
idProduct=5342, bcdDevice= 0.0
>From my own struggles to get a board (custom board as it happens, but like
>others that were there) I found:
Board support was often incomplete. Look at other boards to see where and how
SPI is initialised and registered. You may find something basic is missing.
Stack size. Random errors occu
I realise, now, I compared mine against 10.2 variants not 10.3...not sure why,
but there you go. I'll give that a try tomorrow - thanks!
On 17/08/2022, 20:19, "Nathan Hartman" wrote:
On Wed, Aug 17, 2022 at 3:15 PM Nathan Hartman
wrote:
>
> On Wed, Aug 17, 2022 at 2:38 PM TimH w
>>> 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/d
>> Please: what are the purpose of:
>>
>> set_voltage_sel
>> get_voltage_sel
>>
>FYI: https://www.kernel.org/doc/html/v4.12/driver-api/regulator.html
Alan to the rescue again :-)
Perhaps Nuttx needs a warning to newcomers: "enter without Linux knowledge at
your peril" LO
On Wed, Sep 7, 2022 at 1:03 PM Tim Hardisty wrote:
>>
>>
>> >>> Please correct me if I'm still missing something, as there are
zero
>> >>> clues I can find as to what each ops function (for exa
On 08/09/2022, 18:07, "Xiang Xiao" wrote:
On Fri, Sep 9, 2022 at 12:19 AM TimH wrote:
>> unsigned int apply_uv;/* ?? SEE BELOW [1] */
>Yes, bool is more suitable than int for apply_uv.
Thanks for confirming/agreeing - once 11.0 is released and I rebase my own
1 - 100 of 313 matches
Mail list logo
