several layers of management, which takes time.
If you like to receive some Geehy boards,
just send me your address.
Kind regards,
Kristof
- Oorspronkelijk bericht -
Van: "j. m. norris"
Aan: "openocd-devel"
Verzonden: Woensdag 25 oktober 2023 14:25:09
Onderwerp:
Kristof,
I can understand 'big company mentality'. However, if they can't afford to
'donate'
a board(s) for the purpose of developing the needed changes to OpenOCD, then
asking someone to purchase a board and donate their time to do the changes
is probably expecting too much.
I was in a similar
> Unfortunately, the patch was not accepted. I don't know why exactly
It's explained in the review comment from Tomas Vanek:
Thanks for the patch.
Unfortunately the flash driver is a copy of stm32 original with a couple of
changes.
We cannot accept such huge duplicity of code. Imagine we would
Dear developers,
Alan, Tommy, Paul, Tomas and Liviu,
First of all my apologies for this late reply. I was ill for more than a week.
I'm in contact with the Geehy engineers. It seems that one of them tried to
push this APM32 chip support:
7421: Geehy: add APM32 support | [ https://review.ope
Hi Tommy,
I think the basic support for APM32F0 was also in that patch that was
abandoned (rejected) here:
https://review.openocd.org/c/openocd/+/7421
There is an explanation for the rejection in the thread.
Maybe new chip versions will depart from STM32 and could need a
separated driver, let's
Not sure if anybody mentioned this patch already just in case it's relevant
here?
https://sourceforge.net/p/openocd/mailman/message/37753998/
Hi,
I didn't remember anything about that but
https://review.openocd.org/q/message:geehy
gives some hints.
On Sun, Oct 15, 2023 at 11:24:01AM +0200, kristof.mul...@telenet.be wrote:
> > What happens if you use stm32f0x.cfg config?
> Error: Cannot identify target as a stm32x
Apparently with
On 15/10/2023 11:24, kristof.mul...@telenet.be wrote:
Hi Paul and Liviu,
> What happens if you use stm32f0x.cfg config?
Then I get the following problem:
** Programming Started **
Error: Cannot identify target as a stm32x
Error: auto_probe failed
embedded:startup.tcl:1524: Error: *
On Sun, Oct 15, 2023 at 11:24:01AM +0200, kristof.mul...@telenet.be wrote:
> Hi Paul and Liviu,
> > What happens if you use stm32f0x.cfg config?
> Then I get the following problem:
> ** Programming Started **
> Error: Cannot identify target as a stm32x
OK, so the flash driver isn't compati
> Great! But where can I find the ID for the MCU? How do I change it in the
> config file?
What happens if you try autoprobing?
See section 10.7 - Autoprobing of the OpenOCD User's Guide:
https://openocd.org/pages/documentation.html
Once you know the IDCODE for the APM32F0 you can try making a
Hi Paul and Liviu,
> What happens if you use stm32f0x.cfg config?
Then I get the following problem:
** Programming Started **
Error: Cannot identify target as a stm32x
Error: auto_probe failed
embedded:startup.tcl:1524: Error: ** Programming Failed **
in procedure 'program'
in procedure
11 matches
Mail list logo
