AmpBenzScientist @AmpBenzScientist@qoto.org

I found something that gives me a sense of power. This code I am working on porting is so elegant and absolutely tiny. I have memory maps and a simple layout. The code is also much different than the code it will replace.

This will take time to get right and it might function more like a WNIC than a MCU. I plan on a port to the ESP MCUs too. There's no reason why one multinational should control 90% with a stack that implements an open standard.

This is going to hurt.

I had a second thought about the port and my induction hypothesis. I need to get passive scan working first. Transmission is too easy to mess up and cause interference. For passive mode the modem would need to be initiated and communication established.

All of this could prove that the stack isn't magical.

So I had an allergic reaction and anaphylaxis for the first time last night. Swollen throat and full body rash.

Okay so the port is going very well. The code being ported isn't full of features and it uses a different RTOS. I really don't want to have to deal with capstones or integration into that RTOS.

If this has a USB or PCI connection, there would be a WNIC in a short period of time. I haven't noticed anything in the proprietary stack that would prevent me from ignoring it exists and controlling it with good code.

This has taken many edits to get rid of most of the insults.

I haven't gotten the port to work yet. It was nothing that would normally affect progress. An allergic reaction to something from some source and gastritis.

The good news is that I didn't do a faulty port.

My projects are going well. The communication stack is a bit different but similar. The firmware being ported is from a WNIC to a MCU WNIC thing. The stack is similar and shouldn't be difficult to get going.

The other project is the analysis part of a scrapped project. I just need to run it on the code of each device. I really hope this works.

One of my projects is coming back from the grave and it will be used in the port I am attempting.

If I can get this MCU to work with the modifications and operate the subsystem in the desired way, this will be a success.

If it was just as simple as Hello World. There will be a lot of code for just a recognizable sign of success. I'm still confident that this is the best bet.

I ended a day of working on computers and configuring them by getting a blue screen of death from a Video Driver.

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.