Hi everyone,

About a year ago, there was a call for Amiga developers to come together and contribute new software for both OS3.x and OS4.x and it seems that this new organization has started to bear some fruit. These would be supplied to users via the AppStore. The intropage is found –> here <–

The “Enhancer” project was the first one teased:

Dome building, an important section of religious and historical complexes, is now used even yet in creating residence households. Just are these domes designed? Find out about the different methods that are useful for creating this unique and valuable layout. Domes have not been unpopular since ancient times in the structure of houses. They’ve resisting unfavorable climatic conditions such as earthquakes, tornadoes, floods, hurricanes and storms’ advantageous characteristic.

I’ve been struggling for quite a few nights and weekends over the last month or so.

I’ve now successfully attached the J68 to the built-in User Flash Memory. This means that the 16KB (actually about ~13KB) of the ROM monitor VUBUG is now out of the pre-initialized m9k’s configured as a ROM, and now into FLASH. Which is non-volatile, and will survive a reboot. The most important part of this is that it frees up our valuable high-speed on-chip m9k’s.

So if I take my working UFM avalon-mm Master controller (which if you recall, connects to the Altera Flash Memory IP core), and attempt to attach it to the J68, the J68 no longer boots the ROM monitor code.

Since it’s not booting, I really don’t have many indications as to why. I decided that writing a ROM bus sniffer that records ROM memory requests and responses, including how long it took to satisfy that request, was worth the trouble.

In the image below, you’ll see four 32-bit columns of data on the left. Each row is a separate request.

They are: