On Wed, Jan 22, 2025 at 3:26 PM Matteo Golin wrote:
> I did not even realize it would be possible to get a shell over the debug
> probe; that would be quite a useful feature for bringing up new boards! I
> might read into that if I have success with the UART later.
Modern debug probes usually pro
Thank you Alan, it appears I had a naive misunderstanding about changing
the clock value in the build :) My first time using STMs with NuttX, but
excited to see what we'll be capable of with it! I'll take a look into
calculating the registers properly and doing out out-of-tree build properly
as Seb
Hi Matteo,
So I think you found the issue: when you change the crystal you need to
find other divisor registers to fit the firmware frequencies, otherwise the
serial baud rate will be wrong.
Some people use the ST Cube to calculate these registers values
automatically (easy way), others do it man
Thank you as well Sebastien! We are planning to do an out-of-tree build, I
was just hoping to minorly modify an existing build locally to see about
booting NSH first. Perhaps it's more worthwhile to just start by doing it
the right way.
On Wed, Jan 22, 2025 at 10:57 AM Matteo Golin
wrote:
> Hell
Hello Alan,
Thank you for the insights, I will take a look at the video resource you
mentioned. Would the Weact image still not work if I modified the crystal
frequency value defined in the board source tree? We are using 24MHz, so I
changed the `BOARD_XTAL` to 24MHz from 25. Maybe my understandin
Hello,
The way we did it for our product, was to copy a canned board and modify
it for our hardware.
The resulting config can be out of tree, which is useful, even more so
when you do a custom project that is not sold and cannot be bought by
others.
Usually we have a separate git repo wit
Hi Matteo,
You cannot use the firmware binary from some random STM32H743 board on your
custom board, unless it is using the same clock frequency and same UART
console.
Looking at the board.h from weact-stm32h743 shows it is using a 25MHz
crystal, so I suppose you are using this same crystal value
Thank you for the help so far. I have attached a second TTL cable to
attempt to read the UART1 NSH Shell, but I don't see anything appear. I did
change the default RX/TX pins though and there are maybe other settings I
need to change for them (like alternate function select). I will review the
MCU
On Wed, Jan 22, 2025 at 2:48 AM Matteo Golin wrote:
> I have attempted flashing the chip with an STLink using the openocd
> commands suggested here, and the binaries can be flashed and verified
> properly. I am attempting to flash the chip with the configuration for the
> weact-stm32h743:nsh since
Hi Matteo
for my NUCLEO-H743ZI2 board I'm using the following script to flash the
SW using openocd, with few differences to your command:
simply launch:
flash_h7 nuttx
==
#!/usr/bin/sh
INSTALL_DIR=/usr
OPENOCD_DIR=$INSTALL_DIR/share/openocd/scripts
FLASH=$INSTALL_DIR/bin/openocd
Dear community,
I am wondering if anyone knows how to use a NuttX SDK exported via `make export`
from nuttx repository for apps development in non-kernel mode?
In kernel mode, I am using it everyday like below:
```bash
$ cd nuttx
$ tools/configure.sh rv-virt:nsh
$ make -j
$ make -j export
$ ls -
11 matches
Mail list logo
