Air105 / Air32F103 - New chinese arm chips

[bingo600]

@bingo600
Thank you, you are welcome!

The DAPLink firmware is for their
black board https://wiki.luatos.com/chips/air32f103/board.html
and tiny DAPLInk https://wiki.luatos.com/chips/air32f103/daplink.html
more details can be found at https://wiki.luatos.com/chips/air32f103/index.html

PCB of the black board:
https://cdn.openluat-luatcommunity.openluat.com/attachment/20220605164915340_AIR32CBT6.pdf
https://wiki.luatos.com/_static/bom/Air32F103.html

I haven't tried V2 but this should be the same as V1, what I know is it fixed the onboard LEDs and improved the download speed.
The source code can be found at https://gitee.com/openLuat/daplink

Pinout as a DAPLink
PB13: SWCLK
PB14: SWDIO
PB0: RESET
PA2: TX
PA3: RX

Thanx 

I have the "Black board"

/Bingo

[5U4GB]

What I don't get is they claim "compatible STM32 For Arduino". But the screenshots are showing Keil, and the AIR105 is clearly a completely different beast from the STM32F103.

It's a translation error, what they mean by "compatible" is that if you put them on the table next to each other they won't squabble or fight.

[bingo600]

Have any of you tried the new daplinkv2 hexfile from the above link ??
I'm preparing for my first daplink setup, and don't want to be hit by "bugs" if/when making my first baby steps w. daplink.
/Bingo

Well i tried the AIR32F... daplink v2 hexfile , and it didn't work.
Everything looked "normal" I think ...
Well except for this message: 0000680 W Board ID 0001 is not recognized [mbed_board]

But program doesn't work after programming , not even if i disconnect the AIR daplink , and Powerreset the PY32F002 board


I loaded the AIR32F... daplink v1 hexfile , and it worked. ... AKA the "Blinky" began to blink on the target.

Code: [Select]

China DAPLINK - Works
$py32f0-template$ pyocd list
  #   Probe/Board              Unique ID      Target 
------------------------------------------------------
  0   jixin.pro CMSIS-DAP_LU   LU_2022_8888   n/a     
$py32f0-template$ make  flash
pyocd erase -t py32f002ax5 --chip --config ./Misc/pyocd.yaml
0000812 I Erasing chip... [eraser]
0001081 I Chip erase complete [eraser]
pyocd load ./Build/app.hex -t py32f002ax5 --config ./Misc/pyocd.yaml
0000820 I Loading $py32f0-template/Build/app.hex [load_cmd]
[==================================================] 100%
0002136 I Erased 4096 bytes (1 sector), programmed 1792 bytes (14 pages), skipped 0 bytes (0 pages) at 1.34 kB/s [loader]
$py32f0-template$



Air32 V2  - Program dowsn't work (run) on target after programming
$py32f0-template$ pyocd list
  #   Probe/Board           Unique ID                                          Target 
---------------------------------------------------------------------------------------
  0   Arm Air32 CMSIS-DAP   000100011a5a5bb50000000001d2b777a5a5a5a597969908   n/a     
      LuatOS                Air32 MINI DAPLink                                         
$py32f0-template$ make  flash
pyocd erase -t py32f002ax5 --chip --config ./Misc/pyocd.yaml
0000684 W Board ID 0001 is not recognized [mbed_board]
0000750 I Erasing chip... [eraser]
0000913 I Chip erase complete [eraser]
pyocd load ./Build/app.hex -t py32f002ax5 --config ./Misc/pyocd.yaml
0000680 W Board ID 0001 is not recognized [mbed_board]
0000740 I Loading $py32f0-template/Build/app.hex [load_cmd]
[==================================================] 100%
0001140 I Erased 4096 bytes (1 sector), programmed 1792 bytes (14 pages), skipped 0 bytes (0 pages) at 4.39 kB/s [loader]
$py32f0-template$



Air32 V1  - Works
$py32f0-template$ pyocd list
  #   Probe/Board           Unique ID                                          Target         
----------------------------------------------------------------------------------------------
  0   Arm Air32 CMSIS-DAP   070000011a5a5bb50000000001d2b777a5a5a5a597969908   ✖︎ stm32f103rb 
      STMicroelectronics    NUCLEO-F103RB                                                     
$py32f0-template$
$py32f0-template$ make flash
pyocd erase -t py32f002ax5 --chip --config ./Misc/pyocd.yaml
0000873 I Erasing chip... [eraser]
0001117 I Chip erase complete [eraser]
pyocd load ./Build/app.hex -t py32f002ax5 --config ./Misc/pyocd.yaml
0000872 I Loading $py32f0-template/Build/app.hex [load_cmd]
[==================================================] 100%
0001776 I Erased 4096 bytes (1 sector), programmed 1792 bytes (14 pages), skipped 0 bytes (0 pages) at 1.95 kB/s [loader]
$py32f0-template$


Btw:
Daplink sees the v1 as a "stm board" , and the v2 as an Air32 board.

The v2 has this daplink message

0000680 W Board ID 0001 is not recognized [mbed_board]

Might have something to do with it .... But it still shows a erasing & programming 


Edit: I programmed the Air32 w. a jlink , specifying taget as : STM32F103CB


/Bingo

[Jack70]

It seems like one of my AIR32F103 boards might be experiencing issues, though I'm not completely certain yet. The ST-Link loses its connection after around 10 seconds. I've tested the ST-Link with another STM32 board, and there are no problems there.

After 10s I get, Error: Unable to get core ID
I can read and program the Flash, but only within the first 10 seconds.

It's possible that it's not actually broken, and the issue might be due to something I've done.
I was trying to get spi3 working and was testing the remapping options, maybe that has broken something that can't be fixed with a full erase?
I know that remapping has some limitations on the air32, but I don't think they say something about losing connection after 10s, right?

Did someone else experience the same problem?

Edit: To be clear, I've used this board for a couple of months without any problems.

[IOsetting]

It seems like one of my AIR32F103 boards might be experiencing issues, though I'm not completely certain yet. The ST-Link loses its connection after around 10 seconds. I've tested the ST-Link with another STM32 board, and there are no problems there.

After 10s I get, Error: Unable to get core ID
I can read and program the Flash, but only within the first 10 seconds.

You recalled me a similar issue I met with STM32F407 some years ago. It later turns out the "WDG_SW" flag in Option Bytes were unchecked, which made the chip reset itself every several seconds.

[Jack70]

I will check it when I get back home, but the chip doesn't reset every 10 seconds; it runs stable. However, when connected to the ST-Link, it resets one time after 10 seconds and then runs stable for hours without any further resets.

I've tried this last night;
I had a brand new board, so I soldered some pins on the program header and tried it. Same problem - it resets once after +-10 seconds every time the st-link is connected.

Next, I tried a different programmer. I have a discovery board with an ST-Link, and that works just fine with the air32, no resets. So I thought it must be the programmer, but the programmer works just fine with an STM32H750, STM32FEB, etc.

The discovery board has an older firmware, so I tried the older firmware V2J40S7, but it made no difference.

I ordered two new ST-Links, a V2 and a V2.1, and I also ordered a DAP-link, maybe one of those will work normally.

Update:
Sometimes I'm just stupid, the AIR32F103 is already a DAP-link, and I have a second one, so I already have a working DAP-link. 😅
And I no longer suspect the AIR32F103. The CSK32F103 also had the same problem, but not all clones. I've checked 4 different clones and 3 original STMs, and only those two stopped working correctly last night. 
This issue doesn't seem to be specific to AIR32. If I discover any interesting insights or if others encounter the same problem, I may start a new topic.

[DavidAlfa]

Are both STlinks using the same FW version?

[fanoush]

1. AIR32F103x is an OEM product, the original type is Mega Hunt MH32F103x, you can still find MH32F103 chips on Taobao, they are the same.

I just spotted some boards having MH2103A CBT6 clone chips https://www.hlkpint.com/product6_1.php?lm=102 are these related to MH32F103x?
The datasheet says 216 MHz too.

Visible here https://ae01.alicdn.com/kf/A611cf33089f74830b00823becb2412c8A.jpg as part of STLINK V2 clone in this shop aliexpress.com/item/1005001621626894.html

EDIT https://www.hlkpint.com/kindeditor/attached/file/20230926/20230926121850_72307.pdf - migration from so called SXX32F103 with differences, clock multipliers ...

[IOsetting]

Visible here https://ae01.alicdn.com/kf/A611cf33089f74830b00823becb2412c8A.jpg as part of STLINK V2 clone in this shop aliexpress.com/item/1005001621626894.html

They are the the same chip.

[fanoush]

Oh, great, thanks for confirmation. For some reason I like this usb dongle form factor of those ST Link V2 clones so will get a few with this chip