CH32V3xx Faster development by doing everything ram

 

Debugging the CH32V3xx (and V2xx)

The CH32V3xx chips are rather good, they are pretty fast, cheap with tons of peripherals.

Swindle supports the CH32V3xx chips (CH32V2XX as well but they are less interesting imho).

Debugging with them is not so great :

- They completely lack watchpoint (some revisions of WCH riscv cores do have them, but not the CH32V3x  it seems)

- Only 4 breakpoints

- Writing to flash is really slow compared to other similar chips ( from STM or Gigadevice)

Shadow Flash ?

The chip has 'shadow flash' i think. 
It is using slow flash ( or RRAM/MRAM)  and shadowing them with  RAM. 
At reset , it copies the flash to ram and execute from there. That way you get low cost and fast execution time.

The option bytes  allocates the physical ram between shadow flash area and ram area. 
But the total cannot exceed the physical amount of ram, ~ 256+64 in my case.

Debugging in bigger RAM

Similarly to what was done with the RP2040, we can debug things in RAM and when it works switch to the real location in flash.

The shopping list is the same :

- In flash, just loop in the reset vector

 _start:
    j _start
- Change the RAM/Flash layout so that we have more ram. On the CH32V303 i'm using,  it means going from 256 kb Flash / 64 kb Ram to 192 kB flash / 128 kB ram
This is done by writing the User part of the option byte :

Careful, bit 0 must be set to 1 and value 0b110 (6)  is not available on most chips.
Reset and you know have 128 kB of Ram.
Then : 
- Use a modified  linker script to put everything in ram
- When debugging don't do "run" but do "continue" with gdb (you may have to change the PC to the proper location of ram i.e. set $pc=0x200000000)


and bingo, you have now unlimited amount of breakpoints and very fast upload time.




I'll probably add that as "monitor" command to swindle so the user byte can easily be changed.

Nb: The above is generic enough but you'd want to use a debugger that supports so called software breakpoints.







Comments

Post a Comment

Popular posts from this blog

Component tester with STM32 : Part 1 ADC, Resistor

Image
I was always  fascinated by the so call "transistor testers" that identify and report pin out, features of pretty much whatever you throw at it. They are based on Atmel 328p chip, the same as arduino nano. So why not do the same thing with a STM32/Bluepill ? The STM32 is faster, has a better ADC accuracy, more memory, can do float etc... and is not more expensive. Warning : I'm doing this for fun & to learn, it might contain error & plain misunderstanding So, i watched a couple of video on the general principle on how they work. This is not a "port" but a rewrite from ~ scratch. When something is weird, i check what the original one does for comparison. Measuring resistance So first thing first :  Resistance & Capacitance. These 2 will unlock the other ones. So how do we measure resistance ? What we do is a resistor divider with a know resistance value: Measure = Vcc*(RtoTest/(RtoTest+Rknown)) As far as the ADC goes, it means ADC=
Read more

Fixing the INA3221

Image
It 's not too complicated to change the board we have seen  previously . You 'll need to cut some tracks, i did it with a dremel and i'm not very handy, so you'll do better. Red =Cut tracks Blue = Add wire 1- You'll need to separate the bottom connector from the ground, cut the 3 connectors BOTH SIDES. 2- Remove the small red area below the middle resistor to isolate each channels from each other Last, connect right side of each connector to the now isolated pad. Mine looks like this after the operation (ugly i know): Be wary of the small track on the left connector that leads to the left side of channel3 resistor. I cut it while isolating the right pad. Now it works, we can go back to the charger.
Read more

INA3221, weird wiring

Image
Continuing my "smart" battery charger, i've finally received the INA3221 module. It is the purple one you can find on ebay for ~ 5 bucks I soldered a couple of pins to be able to connect it so that i could test it and something immediately caught my attention. It is supposed to be a high side current/voltage sensor, typically in a setup like that : So you can measure the voltage supplied to the load, and the current going through it. Now, let's have a look at the module, look at the top of the following pic, where the sense connectors are. CH3/GND/CH2/GND/CH1/GND ? Wait ? What ? Yes, all the IN- pins are connected to ground, so it is a bottom current only sensor. Additionally, the - side of the shunts are ALSO connected to the ground, no only the connectors. The actual layout is like that : That raises two problems :  The voltage is meaningless as we are only measuring Current x ShuntValue, not the supply volt
Read more