AmpBenzScientist @AmpBenzScientist@qoto.org

It's going to be pointless unless everything is going work well with the RTOS. At least upgraded internet is going to make this not infuriatingly slow.

So my plan to analyze the firmware went off fairly well when I didn't know what ARM version it was. A good place to stop. I think this can be ported but I just need to learn more about it and how it was implemented.

So a few things that lead me to think this can be ported.

1. This was used for wifi on a couple wifi chipsets.

2. Tensillica used the dumb Azure Waves or whatever it's called on the ESP32 but implemented their own wifi stack.

3. This has it's own wifi stack with code from Tensillica that is open source. This is completely open source code.

4. There's already a Bluetooth stack that's open source I think for this chipset or it will be.

5. This is how many times I will quit before I find results.

6. It might be as simple as taking the assembly and addresses from the existing one and plugin the open source code.

Getting it to work will be the difficult part but it will be open source.

Part of this wifi stack is Tensillica licensed.

I'm happy for Twitter users to discover what true Free Speech looks like.

If I can get past my 72 kbps internet connection without breaking everything, I will stay up long enough to port this.

Else if I will at least compare the binaries of this wifi stack against the BL602 and hopefully report back.

I need to start documenting my work like I said I would several times before. I love hardstyle.

So I am about to compile this firmware just so I can compare it to the BL602. Maybe it will be easy to port.

I found a wifi stack that should work but it is written in Low C and for ARM. Look up asm and convert to RV32 mapping, rinse and repeat. I think I already have it compiled so I could possibly uhm. I will find something.

Oh my goodness, RTEMS has config for RV32IMAC and RV32IMAFC. So what if it was originally named something else? I see no code involving Missile System operations or at least no guidance, pressure, barometric pressure or targeting. I feel better about this and might try to port this BSD 2 Clause and GPL v2 beast to a Buffalo. The secret sauce comes later if I can actually port it.

So I think I will try to port a Missile guidance system to the BL602 because it's GPLv2 and also maybe 🤔 it would be useful to show that wireless stacks are not very important to functionality. The K210 would be a better candidate based on power alone but maybe this could work. Idk, it's too cool of an opportunity to ignore.
(It's not really a missile guidance system, that's just what it was designed for and previously named after. Legally not a guidance system I think 🤔)

If I don't, maybe I will try a similar RTOS.

I've been adjusting to not being on my medication for ADHD and women are more distracting to me lately. It's almost as if I'm a young man and not a machine now. Carpe Diem?
Perhaps I can have something else going on in my life than tech.

RTEMS and eCoS are both used in embedded systems. The latter was the full stack Qualcomm Atheros wifi embedded SoC. The source is there, open and ready to be ported to this little menace.

After many hours of feeling like an idiot, I have found that my earlier intuition was more valuable than I thought. I thought that the code was too different to be ported. I see now that is not the case. I'm not doing reverse engineering on the overhyped future proof code that was developed to make cheaper iot devices.

I've got 2 separate RTOS that I can port to the BL602. They have their own implementations of a hal and were doing this work long before Rivierawaves. Mission critical applications are where they were developed and still used

I need to rest now, it's been a rough day. I know that these systems will work because they were used on previous generations of hardware for the same or a similar purpose.

I finally understand how the BL602 uses Rivierawaves IP. It's not blatant plagiarism nor something I would have thought about. It's the Wifi and Bluetooth implementation together. This is hardware and code RE. It uses an SDR effectively. The IP has diagrams showing where open source code is used. It only appears to be easy to RE full stack and OS.

I remember hearing President Kennedy speak about going to the moon. "We do these things not because they are easy but because they are hard."

I still feel dumb for not getting it sooner and this has been an effort before now. Now I'm still without the goal, my best wasn't good enough and it's been over a year.

It wasn't pointless as I made progress. I'm going back in for another round.

I've stayed up for days while working on this RE project. For me it has been going on for a little over a year. Some might say that it's bad for me to be doing this work as much as I am. I live to be absorbed by my work. Perhaps I am just a Mathematician doing different work. ;)