CubeCell HAL anyone?
-
@boozz said in CubeCell HAL anyone?:
What does HAL stand for?
Hardware Abstraction Layer. It is a middle piece (sort of translator) in the software where the characteristics of the hardware you are goint to use are defined so the software developers can use the same code for different architectures... and be aware I am very low in the coding chain, so this definition is my pure and ignorant understanding of the concept :face_with_rolling_eyes:
https://github.com/mysensors/MySensors/tree/master/hal/architecture -
Yes, exactly.
Well, I think we would have to write the HAL functions (which is not too hard as I imagine) as a first step. I hope we could use the RFM95 drivers in a first step, but the Framework compiles with a LoRa and a LoRaWAN app. If we have luck, we have no collisions.
In a further step, I would test if it is worth while to implement a new transport and use the native LoRa-stack.Well, I think I fork the github-repository and start to play around...
-
Ok status update after a short night:
- HAL for the CPU/Boards is working, but:
- ASR506x printf is broken, for example hhu is not working
- ASR506x Serial.flush is broken, it skips the last 8 bytes in the buffer
- I can't get the RFM95 transport to work, and CubeCell
- Somehow, [underscore][underscore]linux[undersocre][underscore] always seems to get defined, but I can't figure out where
- documentation/source code is horrible. I think I'm going to write a new transport based on LORA_App
Regards, Edi
-
New status update: IT WORKS!
I have to implement sleep and ATC, then I will upload it to GitHub for testing, if anyone is iterested... -
