Hello
I did that and it works in a consumer product with a stm32 since, well,
2018 I think. Also in an open source product.
my board uses a custom linker script that locates the start of the flash
a bit farther than the usual start (one stm32 block or 16k IIRC) . Then
I compile nuttx as usua
Sorry, forgot to say that of course, VTOR is updated by the bootloader
prior to jumping into the OS.
BOOTCODE __attribute__((naked, noreturn)) void __boot_app(void)
{
__asm__ __volatile__ ("\t"
/* load SP (from 08004000) */
"movw r0, #0x4000 \n\t"
"mo
On Thu, Apr 22, 2021 at 2:54 AM Alin Jerpelea wrote:
> Hi Brennan,
> I think that we should backport them and I will cut RC1
> Thanks
> Alin
If I'm not too late, I fixed up the ReleaseNotes a little bit in PR-3570
>
>
> On Thu, Apr 22, 2021, 08:30 Brennan Ashton
> wrote:
>
> > Alin,
> > I
It is perfect timing!
I will cut RC1 with the fixes tonight
Thanks
Alin
On Thu, Apr 22, 2021, 16:12 Nathan Hartman wrote:
> On Thu, Apr 22, 2021 at 2:54 AM Alin Jerpelea wrote:
>
> > Hi Brennan,
> > I think that we should backport them and I will cut RC1
> > Thanks
> > Alin
>
>
>
> If I'm not
Yes, I am getting this error.
NuttShell (NSH) NuttX-10.1.0
nsh> nsh: nsh_session: readline failed: 9
I haven't used NuttX on this board for a while, so I cannot say when
this broke. I have attached the .config file, should be the
auto-generated config file based on stm32f4discovery/configs/usb
Hi Max,
it appears you are using an outdated NuttX and/or board config
During the compilation using out .config I got some errors:
In file included from nuttxspace/nuttx/sched/mqueue/mqueue.h:38,
from group/group_leave.c:44:
nuttxspace/nuttx/include/nuttx/mqueue.h:103:26: error:
One of the best brief explanation of the Dali protocol is in Microchip TB3200
Technical Brief
(https://www.microchip.com/wwwAppNotes/AppNotes.aspx?appnote=en606182), also,
DALI introduction on page 8 of this (
https://download.beckhoff.com/download/document/automation/twincat3/TwinCAT_3_PLC_Lib
Both the Microchip solution and the example I've mentioned above uses the UART
to communicate with DALI Interface. I think we can consider the same.
On 2021/04/22 15:56:51, murat tologlu wrote:
> One of the best brief explanation of the Dali protocol is in Microchip TB3200
> Technical Brief
Both the Microchip solution and the example I've mentioned above uses the UART
to communicate with DALI Interface. I think we can consider the same.
A better design would be independent of the physical transport layer .
This topic is your expertise !
On 2021/04/22 16:49:30, Gregory Nutt wrote:
>
> > Both the Microchip solution and the example I've mentioned above uses the
> > UART to communicate with DALI Interface. I think we can consider the same.
> >
> A better design would be independent of the physical t
I forgot to say: Machester encoder is just an exclusive or gate, manchester
decoder is also an exclusive or gate ! If you ex-or the clock and the data then
you get the manchester encoded code. At the receiver side, if you start and
synchronize a same frequency free running clock with the negati
Hi, all,
I noticed that we need to backport the following PRs to the nuttx-10.0
branch.
https://github.com/apache/incubator-nuttx/pull/2540
https://github.com/apache/incubator-nuttx-apps/pull/521
https://github.com/apache/incubator-nuttx-apps/pull/523
So, I've just added the backport/10.0 label
Brennan, thanks for the updates.
On Thu, Apr 22, 2021 at 2:27 PM Brennan Ashton
wrote:
> On Wed, Apr 21, 2021 at 5:59 PM Masayuki Ishikawa
> wrote:
> >
> > Hi, Brennan
> >
> > Sorry to reply to the old email but I noticed that the following tags
> are missing in the github repositories.
> >
>
Just as a heads up Github has implemented a change to help combat spam
accounts using our CI resources for crypto mining and the like. I
don't know of any cases of this happening to this project, but many
other projects have been hit with this.
Going forward the first time someone submits a PR a
On Thu, Apr 22, 2021 at 11:26 PM Brennan Ashton
wrote:
> Just as a heads up Github has implemented a change to help combat spam
> accounts using our CI resources for crypto mining and the like. I
> don't know of any cases of this happening to this project, but many
> other projects have been hit
Thanks for sharing
Regards
Alin
On Fri, Apr 23, 2021, 05:31 Nathan Hartman wrote:
> On Thu, Apr 22, 2021 at 11:26 PM Brennan Ashton >
> wrote:
>
> > Just as a heads up Github has implemented a change to help combat spam
> > accounts using our CI resources for crypto mining and the like. I
> >
16 matches
Mail list logo
