Wordpress operation

This period I have installed copy of Wordpress at home and remuneration a way how to combine iMatrix encrypt to each post automatically. Process is simple. If you like to add this to yours - contact me. Soon, operation guide will be availalbe online...

One of democratic communicate united to test it twenty-four hour period 4-hour interval:)

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.

Boot agenda project is a go!

Aft a Brobdingnagian come of exertion and in-situ enquiry with iBoot (basically a positional notation large positional notation search done the encrypt, disqualifying no functions to see if I could figure out wherefore my LCD operator wasn't excavation properly), I managed to get it fully excavation. The question was three-fold: first, I forgot to write the first and last bytes of my letter of the alphabet tables: oops, but easily fixed. The second question was that apparently iBoot changes the SDIV of the measure in the middle of the data formatting process. I'm not even sure yet how galore inclination the change in measure relative frequency affects. It certainly unnatural the LCD, because before here was no sorts of flickering scanline unfamiliarity as one would reckon from a misconfigured clock.

Anyway, I converse the procedure that denaturised the SDIV and unenforced it. Seems to work fine nowadays. It's been ages since I looked into the measure speed stuff (beautiful little right when I first started this) so I can't say for certain, but I'm beautiful sure doing this increases the measure speed (which would make sense).

The LCD operator worked aft those fixes and I went onto write a simple framebuffer in a couple of time period, so we can finally get text-mode indefinite quantity on the iPhone screen. It was beautiful influential to me to get the screen excavation because even if we can boot a meat, I wanted the layman to feel like a full-fledged OS was running on the tactical manoeuvre, and that instrumentation display and I/O of no sort.

For a final cry, I also wrote no encrypt that lets us notice when the physical buttons (Home, Hold, etc.) were organism pressed down. From these pieces, it will be possibility to construct a in writing boot agenda restricted by those buttons. You could have one derivative to boot into the iPhone OS, and one derivative to go into openiboot command-line modality with that text-mode display.

The icon I posted is the electric current development exposure running on a first generation iPhone, with oibc (openiboot case) adjacent and running on my screen background computing machine. If you have a 2G iPhone or a first-gen iPod touch, you can try it out yourself by checking out the encrypt from Github and collection it (It's lone premeditated to be shapely on a UNIX machine. You'll be wanting no UNIX headers other). I wrote no alkaline notes on how to get it running inside the source tree, but this is not something you're anticipated to work with unless you're a fairly experience software engineer yourself.

Poorlad's agenda unenforced; Porting issues resolved

Twenty-four hours night, I integrated in a branch I was excavation on for poorlad's agenda. A turning of that aesthetical agenda is nowadays in Stinker. His agenda included a turning string at the bottom. We didn't have some way to keep track of versions and builds before, so this was actually a good persuasion that I had to compel. Because I didn't want to compel support for non-fixed dimension fonts, or add other space-consuming font, I just old the comfort font I was already victimisation for that part. I also had to change the spatial relation on the bottom of the screen, since it was basically inconspicuous right to letter of the alphabet issues otherwise.

The border between the spatial relation and the "black" is clearly perceptible on my tactical manoeuvre. This is probably because of a letter of the alphabet issue. When poorlad comes back, we can ask him to measure it more.

Other, it looks beautiful good! In order to make this possibility, I added in stb_images.c, a great petite little image edifice that can read PNG, JPEGs and even PSD files and does zlib compression as an added fillip. This will be a great help if we determine to change belongings or requisite to add more than stuff that consumes a lot of space. I also added in a alkaline function to carry out letter graduation (albeit comparatively slowly).

Sadly, spell I was engaged component these changes, ius from IRC actually begun to compel poorlad's agenda without me intended about it, so we ened up duplicating each other's efforts. He was able-bodied to collect in zlib and libpng, but the monetary value was to modify the final positional notation to 347 KB. Whereas pickings out the old agenda images, and adding small, shut PNGs and the stb_images edifice instead actually ready-made openiboot small than it was before! His result to preblend the images, rather than law-breaking letter graduation on the tactical manoeuvre, was probably more than best from a demonstration perspective.

Steven Troughton-Smith told me on Chirrup that he has actually unenforced his personal boot agenda as well. I'm not sure if he old the new PNG encrypt or not, but the new encrypt makes it beautiful easy for a workmanlike software engineer to add in some agenda they would like. I'd tell everyone to skin away, but we should keep as small indefinite quantity wild branches of this project as possibility, since everyone randomly commencement openiboot just for kicks (especially a restricted turning) and point reaching to us (read: me, ultimately) for support is something we don't have the resources to handle at this moment.

On the porting side, the issues with facility, optimizing NOR access on iPhone 3G, NAND access on a small indefinite quantity inclination no be to have been fixed, so we can basically scratch the first deuce items off of the list I put up in the last post. I'm pleasantly dumbfounded at how relatively easy it was.

Anyway, nowadays for the meat. Well, if I don't get brainsick by activity to NAND.

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.