LCD operator finished?

I had a lot of trouble deed the LCD operator to work. Everything seems to be fine leave off that when I try to write to the storage device address range diffident for the LCD's letter of the alphabet tables, it doesn't register. It's as if no measure or no tactical manoeuvre hadn't gotten reversed on or something. Therefore, aft ratio openiboot from iBoot, the screen gets no screwed up.

However, if you load iBEC from iBoot, the screen doesn't get screwed up: you can still use bgcolor and everything deeds. I belief that meant at first here was something wrong with my LCD init encrypt. I worn out a frustrative day carefully auditing it for errors, and I did find deuce bugs that I fixed, but unfortunately it did not have some effect on the piping question. I got as right as I could with still methods so I definite to carry out a series of experiments.

First, I had no trouble chainloading iBoot and iBEC from openiboot. Here was a series of fails that I fixed along the way: trouble with USB send (just a tike literal error in the case), trouble deed the resultant thing to execute in storage device (you've gotta turn off the CPU caches, disenable MMU and interrupts for it to work properly. It also can't be run as part of an ISR because, well, iBoot expects to be able-bodied to receive interrupts, so I had to move the command business onto the piping thread and just have the ISR line up up commands for the piping thread to process). Anyway, those were eventually fixed.

My experiments showed that aft openiboot did its inits, chainloaded iBoot and iBEC was able to reinit the LCD properly (they had the European question). I constricted the question down to the place in power.c where I "turn off" the LCD mortal. This happened in the 114 iBoot, so I belief it was necessity. Analyzing the newer 2.x iBoots, that procedure was actually removed. Since I am reasonably self-confident that my syrah_init is functionally selfsame to their merlot_init and this that power init that when present, causes LCD init to fail in no cases and when abstracted, allows LCD init to win in no cases, I'm beautiful sure that's the problem.

So I went in the lead and removed it. This Gregorian calendar month or Gregorian calendar month not mean I am actually depending on the iBoot that I chainloaded openiboot from for the LCD init. We'll see aft I try to exchange iBoot entirely in the bootchain.

Anyway, USB is solid as a rock nowadays seemingly and chainloading seems to be excavation quite well. I'm actually able-bodied to load iBoot from NOR, patch it in storage device, and point execute it from openiboot. This probably instrumentation I'm ready to try flashing the thing again.

Point we'll see how well it truly deeds.

LCD operator finished?

I had a lot of trouble deed the LCD operator to work. Everything seems to be fine leave off that when I try to write to the storage device address range diffident for the LCD's letter of the alphabet tables, it doesn't register. It's as if no measure or no tactical manoeuvre hadn't gotten reversed on or something. Therefore, aft ratio openiboot from iBoot, the screen gets no screwed up.

However, if you load iBEC from iBoot, the screen doesn't get screwed up: you can still use bgcolor and everything deeds. I belief that meant at first here was something wrong with my LCD init encrypt. I worn out a frustrative day carefully auditing it for errors, and I did find deuce bugs that I fixed, but unfortunately it did not have some effect on the piping question. I got as right as I could with still methods so I definite to carry out a series of experiments.

First, I had no trouble chainloading iBoot and iBEC from openiboot. Here was a series of fails that I fixed along the way: trouble with USB send (just a tike literal error in the case), trouble deed the resultant thing to execute in storage device (you've gotta turn off the CPU caches, disenable MMU and interrupts for it to work properly. It also can't be run as part of an ISR because, well, iBoot expects to be able-bodied to receive interrupts, so I had to move the command business onto the piping thread and just have the ISR line up up commands for the piping thread to process). Anyway, those were eventually fixed.

My experiments showed that aft openiboot did its inits, chainloaded iBoot and iBEC was able to reinit the LCD properly (they had the European question). I constricted the question down to the place in power.c where I "turn off" the LCD mortal. This happened in the 114 iBoot, so I belief it was necessity. Analyzing the newer 2.x iBoots, that procedure was actually removed. Since I am reasonably self-confident that my syrah_init is functionally selfsame to their merlot_init and this that power init that when present, causes LCD init to fail in no cases and when abstracted, allows LCD init to win in no cases, I'm beautiful sure that's the problem.

So I went in the lead and removed it. This Gregorian calendar month or Gregorian calendar month not mean I am actually depending on the iBoot that I chainloaded openiboot from for the LCD init. We'll see aft I try to exchange iBoot entirely in the bootchain.

Anyway, USB is solid as a rock nowadays seemingly and chainloading seems to be excavation quite well. I'm actually able-bodied to load iBoot from NOR, patch it in storage device, and point execute it from openiboot. This probably instrumentation I'm ready to try flashing the thing again.

Point we'll see how well it truly works.