bl_docs
Datasheets and Reference Manual for BL602/BL808 (by bouffalolab)
linux
Linux kernel source tree (by openbouffalo)
| bl_docs | linux | |
|---|---|---|
| 6 | 3 | |
| 132 | 6 | |
| -0.8% | - | |
| 2.5 | 0.0 | |
| about 1 year ago | 12 months ago | |
| HTML | C | |
| - | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bl_docs
Posts with mentions or reviews of bl_docs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-23.
-
What does inter-core communication look like?
I'm browsing through the documentation of bl808 SoC and I've got some questions, and I would be glad to have some answers as it is something new to me and I'm just trying to finally get my head around it. While answering, please bear in mind that if you don't know this SoC but have knowledge from other solutions I will be also supper happy, because I'm trying to grasp the general idea. This SoC is just an example.
- What does the inter-core communication look like?
- Use SIMD from C
-
The $8 Linux Computer
Stay tuned, according to the Bouffalo Lab BL808 SoC datasheet (page 90) series numbering system that the board is based on, they will probably have more RAM and ROM capacity in the later versions of the SoC:
https://github.com/bouffalolab/bl_docs/blob/main/BL808_DS/en...
- $8 Linux SoC with 64MB RAM, 16MB Flash, WiFi, Bluetooth, Zigbee, USB, Ethernet
linux
Posts with mentions or reviews of linux.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-23.
-
What does inter-core communication look like?
The "IRQ router" is handled as a nested interrupt controller in linux. There are some memory mapped registers where we can mask/unmask/clear which interrupts we want to route to D0 from M0. Once one of these unmasked interrupts gets triggered, D0 will get `WL_ALL_IRQn`. And then you have to go look at those memory mapped registers to figure out which M0 interrupt got triggered. Look for function ` GLB_DSP_Get_MCU_IntStatus` and siblings. This functionality is completely undocumented and https://github.com/smaeul figured out how it works. Linux driver is here(https://github.com/openbouffalo/linux/blob/bl808/all/drivers/irqchip/irq-bflb-mcu.c)
-
Why is it so difficult to find a device that is not supported by Linux?
If you want to get into other aspects - the bl808 from bouffalo labs is a Triple core ASP (not SMP!) CPU with 64MB of ram (!) for $8. It can run Linux and but still needs a lot of drivers written, from areas like clocks through to SPI/I2C etc. https://github.com/openbouffalo/linux
What are some alternatives?
When comparing bl_docs and linux you can also consider the following projects:
riscv-p-spec - RISC-V Packed SIMD Extension
M1s_BL808_example - M1s_BL808_example
proot - An chroot-like implementation using ptrace.
esp-now - A connectionless Wi-Fi communication protocol
toolchain_gcc_t-head_windows