Longan Nano, freeRTOS, drivers

 

Things are progressing nicely.

I now have freeRTOS , Serial (with DMA), SPI (with DMA) and basic LCD support. The goal is to remove all dependencies toward the GD32 fw lib and the longduino externals ultimately.




Why do that ?


First, the low level GD32 library is just a wrapper on top of the registers.

It does not do consistency check, it does not bring features/optimization/...

The library i'm doing is a little bit higher level. You setup the DMA parameters and that''s it. In a single call. No need to do X calls to setup all registers one per one.

Additionally, the coding style is a bit different. The GD32 firmware lib is using C macros so that

SPI_CTL(SPI0) is the "Control" register of SPI0

I'm using a structure defining all the registers of a given SPI

To get the same thing, i do

spi0->CTL

But it's basically the same thing, no ?

Almost. The main difference is , under gdb, i can just do 

p /x *spi0

to see all the registers of SPI0 and check everything is alright. Same for DMA etc...

i.e.

(gdb) p /x *aspi0
$2 = {CTL0 = 0xc004, CTL1 = 0x0, STAT = 0x2, DATA = 0x0, CRCPOLY = 0x7, RXCRC = 0x0, TXCRC = 0x0, I2SCTL = 0x0, I2SPSC = 0x0}

Additionally, it is much less error prone.

Multitasking

The 2nd difference is that since we are using FreeRTOS, all the interrupts are just unlocking the underlying task with a semaphore/mutex/whatever upon completion

But it's not faster, it's most of the time slower ?

True, it is a bit slower, but you can do something else meanwhile. For example having a low priority task doing ADC measurements whenever the main task is doing SPI transfer. The chip is running at 108 Mhz, so even 1 us is a lot of cycles ( 108 :) )


Task switching within freeRTOS

I made a stupid mistake when using QQxiaoming FreeRTOS port, so i had to look into it to debug that.

Usually freeRTOS wraps all the syscall/Irq with store context/restore context over pxCurrentTCB sp so that whenever a task switch is caused by an interrupt, pxCurrentTCB changes and the restore part restores the new task context.

So nothing special to do, when exiting the interrupt/exception you'll resume operation on the appropriate task.

QQxiaoming does something different : It does nothing  special as far as interrupt store/restore is concerned BUT it triggers an exception when a rescheduling is needed. 

That exception is not processed preemptively.

So you'll finish your current interrupt normally, and just after that, another interrupt/exception will happen that will just switch the task

It is a little bit more expensive in terms of cycles, i.e. a second exception to handle.




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