Hi Adam,
Thanks for sharing this! I will probably be working on this and I am sure
this will be helpful. As far as I understand Lars, his company is fine with
upstreaming the NuttX port to W5500-EVB-PICO.
Bye, Michael
On Tue, Apr 9, 2024 at 1:46 AM Adam Comley wrote:
> For whoever is working
Hi Christofer,
as Mainz is quite close to me I would definitely attend the event. I
presented twice at the NuttX International Workshop and would be willing to
give a generic introduction on NuttX in Mainz, if desired.
Thanks!
Michael
On Fri, Jan 5, 2024 at 8:46 AM Christofer Dutz
wrote:
> Hi
x
> programs that use smartcards?
>
> For the moment I am focused on uart smartcard support only.
>
> Thanks for your interest,
>
> Sebastien
>
>
> Le 17/05/2023 à 16:17, Michael Jung a écrit :
> > Hi Sebastien,
> >
> > one of the projects I am working o
Hi Sebastien,
one of the projects I am working on requires an EMV 4.3d level 1 compliant
smartcard reader on an STM32U5. So I would be very interested in the work
you are planning to do. I have a lot of background knowledge on EVM
compliant contactless card readers, but unfortunately not so for t
Hello Tim,
I was playing around with RNDIS a couple of years ago and could not get it
to work either. Which is why I started the CDC-ECM driver back then.
The right thing to do would probably be to create an CDC-NCM driver, as
CDC-NCM is supposed to be supported on Linux, MacOS and contemporary
t; 2011
>
> Sony = 116 + 113 + 75 + 73 + 53 = 430
>
> Espressif = 155 + 101 + 86 + 39 + 32 = 413
>
> Petro = 145
>
> Unikie = 139
>
> Raiden = 115
>
> PX4/Dronecode = 69
>
> CV-Bowen = (52)
>
> Jukka Laitinen = 50
>
> Zouboan = 49
>
> Ee
I think this is a great idea! Thanks for the offer, Alin.
Alin Jerpelea schrieb am Fr., 28. Okt. 2022, 08:10:
> If none has a better idea I can step in
>
> Best Regards
> Alin
>
> On Fri, 28 Oct 2022, 06:35 Nathan Hartman,
> wrote:
>
> > Ping... Folks, we need to choose a Vice President for the
Hello,
I did implement the w5500 device driver, but I am only using it on a
proprietary custom board at the moment. Alan is currently working on using
the w5500 with the STM32F4Discovery board. Apparently there are still some
issues, but I guess once those are resolved Alan will upstream the
res
Hi Sebastien,
I have this warning degraded to an informational message in my local
repository for the exact same reason. In my opinion it should just be
changed to informational. I.e. no need to make this configurable.
Bye,
Michael
On Thu, Jun 9, 2022 at 12:45 AM Sebastien Lorquet
wrote:
> Hi,
Hello everybody,
With pull request #6330 there is a call to net_driver->d_txavail() from
tcp_timer_expiry(), which is scheduled on the low priority work queue. To
my understanding this means that net_driver->tx_avail() is called without
the network being locked, correct?
At least in net/driver/s
Hello everybody,
With pull request #6330 there is a call to net_driver->d_txavail() from
tcp_timer_expiry(), which is scheduled on the low priority work queue. To
my understanding this means that net_driver->tx_avail() is called without
the network being locked, correct?
At least in net/driver/s
28, 2022, 12:35 AM Michael Jung wrote:
>
> > Hello,
> >
> > There is a include/nuttx/net/w5500.h header file for the WIZnet W5500
> > Ethernet Controller in the NuttX code base, but no accompanying device
> > driver. Does anybody know whether such a driver exists somewhere?
> >
> > Thanks!
> > Michael
> >
>
Hello,
There is a include/nuttx/net/w5500.h header file for the WIZnet W5500
Ethernet Controller in the NuttX code base, but no accompanying device
driver. Does anybody know whether such a driver exists somewhere?
Thanks!
Michael
Hello everybody,
I am currently experimenting with buildroot to create a NuttX SDK, which
includes a GCC toolchain build using NuttX as the C library and basically a
sysroot environment that contains static libraries (for e.g. libwebsockets,
sqlite, etc...), which can optionally be linked by users
Hello Alan and Petro,
I have used libwebsockets on NuttX a couple of years ago. This is an
awesome piece of Software and meanwhile it is MIT licensed. I an planing to
usw it again.
Bye,
Michael
Alan Carvalho de Assis schrieb am Di., 5. Apr. 2022,
12:15:
> Hi Petro,
>
> Please take a look o
for your help
Michael
Am Fr., 25. März 2022 um 17:50 Uhr schrieb David Sidrane <
david.sidr...@nscdg.com>:
> Does the CPU busfault if write the GPIOI MODER? Do the values stick when
> written?
>
> -Original Message-----
> From: Michael Jung
> Sent: Friday, March 25
,
>
> Odd. Did you check the defines? How are you verifying it? Have you JTAG-ed
> it, could it be bad SVD? Have you just printed the value to be set and the
> result ?
>
> David
>
> -Original Message-
> From: Michael Jung
> Sent: Friday, March 25, 2022 9:07 AM
&
Hello,
This is more about STM32 than it is about NuttX, but I know there are
experts here: STM32U585 does have 8 GPIOs on Port I. However, setting bit
8 (GPIOIEN) in RCC_AHB2ENR1 seems to be ignored (i.e. GPIOIEN remains at
0). For the other eight IO ports (GPIO[A-H]EN) it works just fine. Any
t Mr. Greg ported to NuttX some years ago?
>
> BR,
>
> Alan
>
> On 3/1/22, Michael Jung wrote:
> > Hello,
> >
> > I am playing around with ncurses on NuttX and would like to set a TERM
> > environment variable to xterm-256color via setenv() before the
> a
Hello,
I am playing around with ncurses on NuttX and would like to set a TERM
environment variable to xterm-256color via setenv() before the application
is started (I would like to run unmodified ncurses example applications),
but am not quite sure where this would best fit in. It seems that
CONF
sage from NuttX mailing list...
>
> Many people replied your email and Michael Jung submitted the support
> to STM32U5.
>
> Please take a look at NuttX's github repo.
>
> BR,
>
> Alan
>
> On 2/24/22, Aaron Rito wrote:
> > Just following up on this as we ha
business and would be willing to do some
contracting work, if that would be an option for you.
Bye for now
Michael
Am Fr., 11. Feb. 2022 um 20:30 Uhr schrieb Michael Jung :
> Hello,
>
> I have NuttX running on the STM32U585 (B-U585I-IOT02A DevKit). Currently
> only UART and SP
Hello,
I have NuttX running on the STM32U585 (B-U585I-IOT02A DevKit). Currently
only UART and SPI macros are supported, but I will continue to work in this
port.
I will do some clean-up and open a pull request in the next couple of days.
I would love to join forces on this effort.
Bye,
Michael
2:21 PM Xiang Xiao
> wrote:
>
> > It's better to let kernel thread skip the duplication of caller's file
> > handler, here is the patch:
> > https://github.com/apache/incubator-nuttx/pull/5379
> > Michael, could you try it?
> >
> >
> >
gt;
>
> On Mon, Jan 31, 2022 at 12:59 AM Michael Jung wrote:
>
> > Hi Xiang, Hi Matthew,
> >
> > Thanks for your responses.
> >
> > Matthew wrote:
> > > Creating a kernel thread in an ioctl "lower-half" would probably cause
> > the fi
maintain file descriptors.
Thanks!
Michael
Am Fr., 28. Jan. 2022 um 23:38 Uhr schrieb Matthew Trescott <
matthewtresc...@gmail.com>:
> On Fri, Jan 28, 2022 at 7:43 PM Michael Jung wrote:
> > specific ioctl command implementation
>
> Creating a kernel thread in an ioctl "lowe
Hello everybody,
I am developing a device driver, which is exposed as a character device
(i.e. /dev/pcd) and which mostly uses ioctl for device control. Within a
specific ioctl command implementation I am starting a new kernel thread via
kthread_create_with_stack. Once this thread's main functio
Hi Peter,
good finding!
There is actually a comment in this regard in include/nuttx/net/netdev.h:
> The d_buf array must be aligned to two-byte, 16-bit address boundaries in
order to support aligned 16-bit accesses performed by the network.
W.r.t. to your proposed fix I think it would be more ap
>
> I would head the direction of splitting them up unless there are only minor
> pin map differences and then do those as wrapped includes (see the
> stm32F412).
>
> The decoupling adds maintenance overhead but prevents the breakage that we
> endured in the stm32.
>
>
>
Hello everybody,
I have started to work on STM32U5 support for Apache NuttX and would like
to get some feedback on how this should be integrated. Realizing that
support STM32F0, STM32L0 and STM32G0 is all handled within
/arch/arm/src/stm32l0g0f0, I would like to rename /arch/arch/src/stm32l5 to
/
Hello everybody,
I would like to start upstreaming my work on STM32L5 support. It is heavily
based on available code for STM32L4. I would like to use the ASF copyright
header wherever possible. Is there a list of people who have signed a CLA
publicly available?
Thanks!
Michael
Hi Xiang,
thanks for your reply and for your work on armv8-m.
Bye,
Michael
Am Do., 10. Dez. 2020 um 15:40 Uhr schrieb Xiang Xiao <
xiaoxiang781...@gmail.com>:
> On Wed, Dec 9, 2020 at 10:48 PM Michael Jung wrote:
>
> > Hello,
> >
> > I recently bought an STM3
Hello,
I recently bought an STM32L52E-DK development kit and I am playing around
with ST's port of ARM's TrustedFirmware-M (see ST's UM2671). I would like
to basically leave this untouched, but replace ST's 'non-secure'
demo-application with a NuttX image. It would be nice if you could give me
s
33 matches
Mail list logo
