emusonacid!

om wrote: but can we please kill this thread cuz I'm not going to die on this hill.

It's a dead issue. If this makes me a fanboy then I'd rather wear that then kill myself with this kind of bitterness.

...never stop dreaming !

MFPhouse wrote:

om wrote: but can we please kill this thread cuz I'm not going to die on this hill.

It's a dead issue. If this makes me a fanboy then I'd rather wear that then kill myself with this kind of bitterness.

...never stop dreaming !

I've been doing some preliminary research into reverse engineering EOS 4.7. This would be challenging to say the least since there are custom chips in there.

However, there are some fairly reasonable Coldfire processor development tools including some seemingly ok emulators, embedded micro linux variants and lots of libraries for general purpose processing, and some good papers on FIIR filters using the coldfire native multiply-add- instruction features in some of the variants.

The challenge is understanding if this can be fixed is:

1. Being able to get a clean build/compile/re-assemble of the code to a binary bit for bit compatible load file for flash download from floppy.
2. Understanding if the RFX issue is hardware or software related. If its hardware, its probably in FPGA type code and we are ^&()ed. If its software, its determining the exact behaviour of the OS and DSP management code. This is likely to be very complex but not impossible.
3. Alternative: throw out EOS and code from scratch using uLinux as a kernel from which to build on a hardware management and processing set of tasks. Very complex requiring complete reverse engineering of hardware platform - very tedious but not impossible, but would be multi man year effort.

I've reverse engineered code in the past and its possible, and not so hard if the tools are good for disassembly and re-building a binary, but I would imageine the EOS build is a few hundred thousand lines of C and coldfire, possibly DPS assembly code.

It would be a massive help if we could determine if compilers were used, what development environment, what memory maps exist, and what data is available on the IC's beyond the obvious coldfire support family.

Anyone attempted an research into this ? I know there is extensive debugging at least from a behaviour perspective of the RFX/Emu OS, but not at a bus/logic or otherwise level.

Lastly, not sure how many read/write cycles the Emu Flash could take - would be handy if there was a dev platform handy on ebay or some kind of debug eprom chipset......any former emu guys out there with a garage full of gear ? :-)

Mark

The RFX-32 uses a driver that was added to EOS to support the newer R-Chip. The driver is likely where the bug lies. Rewriting the OS from the ground up would be a total waste. EOS kicks ass.

If only a former EOS developer would leak v4.8 and the programming tools. It has full sysex for the RFX.

hi everybody,

can anybody help me get eSMDId_b2.zip? the link

http://www.leetradio.com/eSMDId_b2.zip

does not work, and my CD is damaged, cant work withou it. Anybody please send it to ramon27@azet.sk

thanxx

just to make sure this thread do not die.


emu developers!!!! fix THE RFX-32 xmas is closing in!!!!!!!!

Hi there !!
Just an idea to fix that f....G problem with the RFX, I will try it : maybe the problem could come from the banks stored on the internal IDE hard-drive formatted in FAT32 so the right test should be to load a specific bank with the bug from a cd and from the hd and compare. I will check it anyway...
I don't think we will fix the bug, we can only try to avoid it

Can anyone help me get the RFX "effects" or "effect presets" files? "Grungulatorfx.e4b", for example? I can't seem to find them on the E-mu systems site. Help would be deeply appreciated.

Try here
http://www.emusonacid.co.uk/forum/viewtopic.php?f=1&t=2080&p=14772&hilit=+Grungulator.+e4b#p14772
I don't know if the links still work?

Thank you, no, they don't work, probably since the latest make over of the site.
I hoped someone here might have downloaded and archived them.
It would be really useful, I guess, to have these kind of files that were originally shipped with the Emus compiled back from the users of emus on acid and made available in the "Files" download section, seeing that Emu systems no longer offers them.

VirusTacut wrote:Thank you, no, they don't work, probably since the latest make over of the site.
I hoped someone here might have downloaded and archived them.
It would be really useful, I guess, to have these kind of files that were originally shipped with the Emus compiled back from the users of emus on acid and made available in the "Files" download section, seeing that Emu systems no longer offers them.

I have most of this stuff archived. I'm planning to set up a small site to host as much as I can get hold of.

Feel free to send me PMs to hassle me about this so I don't forget!