AmpBenzScientist @AmpBenzScientist@qoto.org

@trinsec Standard Deviation 100.

@Exsangus Have you tried ephedrine? I'm not a doctor.

@Amikke What is a better solvent for this?

@lupyuen We ran into this during disassembly and decompiling. That's why I needed to make a custom processor to help decompile the code more accurately. It's a very odd core. Seemingly RV32GC, and is RV32GC, with some oddities.

There is a good reason why the computer I did my work on is setup exactly the same way as it was when I released the last code revision. All that work, all the documentation and the results of that effort are still intact. Is it the human readable version? Absolutely not. That would come later from you and even now it is an impressive work.

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.

@Pat This makes me blush. In the context of what I said lol.

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.

@kreyren Curiosity is suspicious.

@Pat Where do I enlist?

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. ;)

I couldn't get the specific SiFive GCC binutils to work a little over a year ago. I did know how to use GCC back then, not rigging a sketchy GCC version by a company to be called like it was a kosher version to cross disassemble. I did it to do it and for hardware addresses/black box.

I ran a few utilities on the objects to determine what architecture, calls to existing code and other fun information.

I discovered how it has dual existence. Waveforming is being used and this is the first I've heard of it being used for this frequency range. That's fascinating but most likely patented.

Many files that are required to build the blobs are in the release or available. Some code is custom made and Mr. Wang is a beast with his code. I'm still trying to put everything together so I can get some documentation out for clean room.

This has been a very long and infuriating project. I've learned a lot. Hopefully I can find enough information.

I'm had some recent developments on the BL602. One being the community, bella gerant alli.

I have been digging through the official source code and found many things. The Atcommands are Haynes Instructions and more importantly, required for the other blobs. The atcoms link the entire system together. This isn't news to the few people who deal with modems.

I did some more RE work recently too. I finally managed to get the archives to disassemble.

My device died and I had to recover so many accounts. More to go but at least I'm back. I have a lot of good news and a new device.