Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
DM72 has joined #openocd
Haohmaru has joined #openocd
<DM72>
Hi all!
<DM72>
I need some information about HDSC / XHSC microcontroller HC32F460 and OpenOCD connection with it.
<DM72>
Have anyone heard about this MCU?
<DM72>
It's a Cortex-M4 based Chinese MCU. I hoped, that it is a replica of some STM32F4x and STM32F1x MCUs, but peripheral registers are completely different.
<DM72>
So i have two questions:
<DM72>
1. Does anyone know if HC32F460 is a replica of smth or an original MCU?
<DM72>
2. Does anyone know if OpenOCD supports flash programming for this MCU?
<DM72>
There is no (or at least i couldn'd find) any english reference manuals for this MCU.
DM72 has quit [Quit: Client closed]
DM94 has joined #openocd
<gamiee>
DM94 are you DM72?
<karlp>
DM94: openocd almost definitely doesn't support flashing it out of the box, but debug should work just fine.
<karlp>
heh, didn't even notice the number hcanged, just tab completed :)
<karlp>
RM_HC32F460_F45x_A460SeriesReferenceManual_Rev1.5.pdf is the doc you want, but I don't hav ea login, you can probably just email them
alkane has quit [Ping timeout: 272 seconds]
alkane has joined #openocd
<karlp>
page seems to want a us phonenumber contact.
<DM94>
Yes, it's me, i was disconnected and then reconnected with another numbers
<DM94>
karlp yes, thanks, i've got this document - it's in Chinese so i have translated it with Google to english. That's how i have discovered, that this MCU is not a STM clone =(
<karlp>
yeah, st doens't own the "<companyid>32<somethign> part numbering system :)
<karlp>
there should still be enough in there to do flash programming, if you really want to.
<karlp>
I'd be evaluating what my real goals are :)
<DM94>
yes, there is FMC registers descriptions in the RM, but that means that i have to write uploader for OpenOCD and then build it.
<DM94>
Or maybe there are some other ways to teach OpenOCD flashing new MCU?
<DM94>
As of "<companyid>32<somethign>" - i understand that, but i had hopes...
<DM94>
I mean, patch and build OpenOCD
<gamiee>
DM94 : you would need to write flash driver for OpenOCD, else openocd cannot flash it at all.
<gamiee>
Debugging should work just fine though, as karlp says
<gamiee>
If you like to learn something new, then writing flash driver is the way. Although, if you do not have enough time, it's easier to somehow nicely integrate into your debug flow flashing firmware through ISP/BootROM mechanisms
<DM94>
Well, no problem with debug, of course, since it's a Cortex-M4 MCU, i understand that.
<DM94>
gamiee yes, thanks for advice. I have some experience writing flash drivers for OpenOCD, but that was long long time ago... I was hoping i wouldn't need to do it once again =)
<gamiee>
DM94 , no problem :) well, if you already worked with flash drivers, it shouldn't be that big issue to make new one, but of course, it's always a challenge, mainly in poorly documented MCU
DM94 has quit [Quit: Client closed]
DM61 has joined #openocd
DM61 has quit [Quit: Client closed]
<karlp>
there's always the "slow" way of doing flash support, just writing it word by word from the host, without writing a loader stub or anything, but it's noramlly too slow for people to feel like they succeeded with :)