That is what I am beginning to think.
I now have the 2022 version of u-boot actually running with a console I
can get to. That's a major step forward and was only done by starting
again as I could not see the difference in the device tree or code no
matter how long I stared at it!
I can even attempt a dfu, in as much as it recognises the command and
starts to do "something"...then crashes out big time. Not found how to
debug u-boot (VS Code/J-link) and really don't fancy prodding around the
Internet to see if I hit lucky.
The code that Gregory pointed out is, indeed, basic, but will allow the
board to boot my app without u-boot as an intermediatary. DFU and RNDIS
(etc) exist already so are easy to incorporporate, so this has a great
appeal. Although it does feel a little like re-inventing the wheel so I
will take a long hard look at MCUboot too.
I am going to give up on u-boot now as I have to get on with the actual
app as this has been a BIG and unwanted distraction.
On 01/07/2023 16:38, Xiang Xiao wrote:
Why not develop a nuttx based bootloader?
We have produced more than ten million devices, all run nuttx with
different configurations 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, Jul 1, 2023 at 5:56 PM Tim Hardisty <t...@hardisty.co.uk> 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 firmware updates, and that easily boot NuttX?
My board uses the usual SAMA5 methodology of AT91
bootstrap->u-boot->NuttX. It all works as expected, as far as running code
is concerned, but I simply cannot get u-boot to enable the USB port for DFU
or RNDIS functions and I need the product to have user-friendly in-field
updates, ideally without me having to write any PC update software.
U-boot has defeated me for over 2 weeks now, and simply refuses to even
"activate" the USB (i.e. a PC never even sees the connect let alone any
functionality: yes, the USB port does work for NuttX and sam-ba code
flashing); device trees are the invention of the devil; and an unholy
apparent mish mash of driver model and "legacy" modes; no SAM boards in the
u-boot trees appearing to have relevant config options I can copy. Add to
that: using latest u-boot rather than the 2020 version I currently have
"working"means it won't even find a console serial port any more, the lack
of response on the relevant AT91 u-boot github to questions, and I am just
about ready to give up :(
But I need a bootloader!
