Air105 / Air32F103 - New chinese arm chips

[IOsetting]

Just found that I2S peripheral works on AIR32F103CBT6 and CCT6 too. The datasheet says I2S only works on 64pin RPT6, but actually works on all types.

[Utherbone]

Hello, sorry for coming on the forum so suddenly and posting on a topic already.
short story, I was researching a project that would transform my copy of stm32f103t8, the cs32f103t8. After much searching I found the project:
https://github.com/amitesh-singh/FASTUSBasp
1 - I was excited and then I was going to download it, but before I decided to prepare my copy of the stm32 and when I went to program it with the "fastusbasp.bin" firmware I had the bad news that it messed up, when I pressed the reset button the led wouldn't blink, probably it was static, I certainly didn't take the necessary care.
2 - This is where I went looking for another one to buy and that's when I found out I had a copy and decent even according to the post no:
https://hackaday.com/2020/10/22/stm32-clones-the-good-the-bad-and-the-ugly/
But unfortunately my copy was damaged when I went to upload "fastusbasp.bin
3 - Since I was going to have to buy one then I went looking for one with USB C because it is very convenient and I could use the cable from my smartphone...
and I came across some copies that you could see the screen printing of the encpsulamento very ugly, there is a copy ch32f103 this seems to be problematic in boot, I was wondering if this copy ch32f103 would work with the firmware of FASTUSBasp.
4 - So I came to this forum, it seems to be very cool and fun, in this post and decided to buy the air32f103 to test and also buy an arduino nano with usb
I am very anxious to receive and test mine, I ordered from the same link

It cost me 1.80 EUR converted from 10.65 BRL

fanoush Can you make a test of this FASTUSBasp firmware?

I don't know English, so I used a translator.

[fanoush]

https://github.com/amitesh-singh/FASTUSBasp
1 - I was excited and then I was going to download it, but before I decided to prepare my copy of the stm32 and when I went to program it with the "fastusbasp.bin" firmware I had the bad news that it messed up, when I pressed the reset button the led wouldn't blink, probably it was static, I certainly didn't take the necessary care.

it is possible your board is still OK, why would any led blink after flashing fastusbasp.bin  and pressing reset? if the flashing went wrong it can always be recovered over SWD

It cost me 1.80 EUR converted from 10.65 BRL
fanoush Can you make a test of this FASTUSBasp firmware?

If you don't have any SWD programmer you can also buy two for that price and keep one as programmer. I flashed fastusbasp.bin from https://github.com/amitesh-singh/FASTUSBasp/releases/tag/v1.0.0 to my Air32F103 board and it seems to work. It gets detected as 'fastusbasp' usb composite device with one COM port and one unknown device. I did not try avrdude.

[Utherbone]

it is possible your board is still OK, why would any led blink after flashing fastusbasp.bin  and pressing reset? if the flashing went wrong it can always be recovered over SWD

Nothing happens nor can even upload, now I'm thinking it may be my ft232rl, reading your response, I will do some tests, I will test the ft232rl with the arduinio to see if it is able to flash the arduino nano.

If you don't have any SWD programmer you can also buy two for that price and keep one as programmer. I flashed fastusbasp.bin from https://github.com/amitesh-singh/FASTUSBasp/releases/tag/v1.0.0 to my Air32F103 board and it seems to work. It gets detected as 'fastusbasp' usb composite device with one COM port and one unknown device. I did not try avrdude.

This is already promising, I was thinking that can not even record, makes me even more anxious, if you can test let me know the result kindly.

In the meantime I will do more tests with the stm32 and see if I can flash it using the arduino nano.

Content separation line none, below
Updates, I am not sure if it is my ftd232rl that is dead or partially ported because it is recognized, but fails to send code, and the stm32 decent copy CKS as I said before, does not flash in any way when I press reset on it, I do not know if I had already recorded some program on it before, but boot 0, boot 0 it start in Linux ttyACM0, so I think it may be good and it is my ftd232rl that may be defective or whatever, But I remember I used it sometime, I will only be able to test it better when I get the new chips I ordered, besides the arif103 I ordered a decent copy of the stm32, a decent copy of the st-link-v2 too, at least according to the seller's confirmation, he also said that the stm chip from the st-link v2 is original, I will confirm when the order arrives, I ordered everything from this store here: https://www. aliexpress.com/store/1916536

[skys2000]

In fact, it is the M4（not M4F）core,Just register be compatible with stm32F103.
it's coremark 1.0 scores :
CoreMark 1.0 : 733.8372
35 / GCCClang 13.0.0 (ssh://ds-gerrit/armcompiler/llvm-project
1f5770d6f72ee4eba2159092bbf4cbb819be323a) -O3 / STAC
K
" alt="" class="bbc_img" />

[Utherbone]

Nice skys2000, Sorry, I didn't understand what you meant by: "Just register be compatible with stm32F103".
Would it be using the firmware from the STM32F103 on the AIR32F103?

So it is not a Cortex M3 like the STM32f103, is it really a Cortex M4 the AIR32F103?

fanoush you are right  , my STM32 or my FTDI are not broken my euphoria made me reverse the RX and TX pins  .

In the college I am attending (Computer Engineering) I am taking programming classes in C language and logic gate classes in digital electronics and several other cool subjects as well.

As soon as I get further into the studies I will share on a site that I will host on GitPages and in a thread here on the forum.

[GromBeestje]

An STM32F103 clone with a Cortex M4 core? I've seen that before. The FlashChip FCM32F103 has a Cortex M4 core

[IOsetting]

The ArteryTek AT32F4 series, AT32F413, AT32F403, AT32F403A are M4F core with FPU are compatible with STM32F103

[GromBeestje]

I have received the AIR32F103 boards I've ordered in the mail yesterday.
The Microcontroller is labelled AIR32F103C8T6
On initial inspection, they show up as

Code: [Select]

Info : [stm32f1x.cpu] Cortex-M3 r2p0 processor detected
Info : [stm32f1x.cpu] target has 6 breakpoints, 4 watchpoints
Looking at the ROMTABLE, All the Peripheral ID fields read 0.
This looks like a part I haven't seen before.

As I've been reading about an M4. are we talking about the same part? Or are there various parts marked AIR32F103?

[thm_w]

As I've been reading about an M4. are we talking about the same part? Or are there various parts marked AIR32F103?

The AIR105 is the M4 part, skys2000 must have been talking about that.

[IOsetting]

Should it be AIR32F103CBT6?

I have received the AIR32F103 boards I've ordered in the mail yesterday.
The Microcontroller is labelled AIR32F103C8T6

[GromBeestje]

Should it be AIR32F103CBT6?

I have received the AIR32F103 boards I've ordered in the mail yesterday.
The Microcontroller is labelled AIR32F103C8T6

Looking closer in the light, what I mistook for an 8 is indeed a B,

[IOsetting]

Hedley Rainnie found there are actually 97k ram available on air32f103cbt6.
http://www.hrrzi.com/2022/12/the-air32f103.html

[DavidAlfa]

I screwed my Air by playing with the PLL hack.
I wondered what would happen by setting that bit to 1:

Code: [Select]

    AIR_SysFreq_Set(Multiplier, FLASH_Div_0, 0, 1);
                                             ^

Damn! Now the flash code is write-protected!
The protection bits can't be removed! The chip can't be erased!

But I noticed it was failing after 0x400 so there was some hope!
So I removed all the possible, emptied main, everything, also non-critical vectors, so the code could fit in less than 0x400.

Code: [Select]

g_pfnVectors:
.word _estack
.word Reset_Handler
.word NMI_Handler
.word HardFault_Handler
.word MemManage_Handler
.word BusFault_Handler
.word UsageFault_Handler
Then

Code: [Select]

void SystemInit (void)
{   
    AIR_SysFreq_Set(1<<18, 0, 0, 0);  /* Hopefully this will fix the screw up lol */
}

Then the issue was fixed and I was able to write to it again.

[DavidAlfa]

So this is what the bootloader does to unlock the PLL "magic":

Code: [Select]

uint16_t *hack = (uint16_t*)0x40022214;
*hack = (*hack & 0x3FF8) | 1<<14 | FLASH_Div_2;    // Add 1<<15 to write-protect the flash



[Kenjutsu]

Anyone know where I can get the daplink firmware that come with the Air32F103?

[IOsetting]

Anyone know where I can get the daplink firmware that come with the Air32F103?

The latest daplink firmware can be found at
https://gitee.com/openLuat/luatos-soc-air32f103/tree/master/AIR_Jlink_Keil
air32_daplink.hex  -  for normal xxlink upload
air32_daplink_iap.hex - for virtual u-disk upgrade

If you want the original one that comes with the board, check out the earliest commit of air32_daplink.hex

[Kenjutsu]

The latest daplink firmware can be found at

Thank you @IOsetting.

I see the latest firmware no longer lights up the 3 LEDs to indicate status. After the flash, I initially thought something went wrong, since none of the LEDs lit up, but it is recognized by pyOCD as a CMSIS-DAP device and works as expected 

[Kenjutsu]

Regarding the Air103/Air105: Currently, can they only be used with the luatos environment, or are there some free/open source toolchains etc available?

[fanoush]

https://gitee.com/openLuat/luatos-soc-air32f103/tree/master/AIR_Jlink_Keil

BTW  it is also synced to github, may be easier to access
https://github.com/openLuat/luatos-soc-air32f103

[IOsetting]

My apologies, the additional flash is fake. By further testing, I found it's just a repeat of the first 128K flash. I must have got mixed up cbt6 with cct6. 

[fanoush]

That's interesting. With real STM chips devices <=128KB are medium density devices with 1KB flash pages, devices over 128KB are  high density devices with 2KB pages. So what the page size is before unlocking and when you unlock it? 1 and then it changes to 2KB?

[IOsetting]

That's interesting. With real STM chips devices <=128KB are medium density devices with 1KB flash pages, devices over 128KB are  high density devices with 2KB pages. So what the page size is before unlocking and when you unlock it? 1 and then it changes to 2KB?

The flash page size of cbt6 is 1KB.
Sorry, the flash hack is fake. 

[bingo600]

Anyone know where I can get the daplink firmware that come with the Air32F103?

The latest daplink firmware can be found at
https://gitee.com/openLuat/luatos-soc-air32f103/tree/master/AIR_Jlink_Keil
air32_daplink.hex  -  for normal xxlink upload
air32_daplink_iap.hex - for virtual u-disk upgrade

If you want the original one that comes with the board, check out the earliest commit of air32_daplink.hex

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.

@IOsetting
Thank you for taking your time to describe the many MCU's , and  THANK YOU for the "Templates" you have made for them. 

I have just compiled & loaded your AIR32F103 "blinky" 

Is there a special linux daplink program , or do you just use pyOCD or OOCD , and specify daplink as "programmer/protocol" ??
I have never used pyOCD , but have used OOCD quite a lot , back in time. And have just build OOCD from GIT.

I'm warming up to use it on a py32f003.
I also have st-link, and jlink-ob , but think i read that daplink is the way to go with those generic Cortexes.

Edit:
Anyone knows what pins are SWDIO and SWCLOCK on the Air32F103 daplink firmware ?


/Bingo

[IOsetting]

@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