I hope to god you're not trying to get this working without a timing diagram and Logic analyzer ?
Why didn't you post the timing diagram ?
This is way beyond the level of a forum post. Even if there are members with years of logic analyzer experience (and that's what this project would require), to troubleshoot it via forum posts seems near impossible.
First of all, everything you have said is only theoretical until you can post logic analyzer screenshots that show that any of those signals are what you say they are.
Second, with clock signals of 13.3 Mhz and 16.6 Mhz, I don't see how an arduino fits into any of this.
Do you have any logic analyzer screenshots ?
so the configuration is relatively complicated since it contains alot of multiplexers , latches , memory cells , a couple of processors and an atmega328 with arduino bootloader to load a mini bootup software from a permanent (so it's arduino related in some sort) .
I think your professor was right, you should have picked something less complex. Most companies would spend thousands of man hours getting something like this working reliably. I think you may have bit off more than you can chew. I know how you feel. I did the same thing for my senior project. I built a mini "mars rover" from a an RC car. I modified the suspension, added an embedded single board computer, put a metal base on it with custom pick and place robot arm with 192 tooth gear driven by a geared motor allowing +/- 90 degrees motion in the horizonal axis and +/- 45 degrees in the vertical axis with an Erector set servo driven gripper and an ultrasonic sensor and a laser range finder. In the end only the motors worked because I ran out of time before I could build the I/O interface board. There was also a wire wrapped working 68000 uprocessor base station with a wire wrapped working monochrome video circuit driving an RGB monitor with the menu displayed on the screen. I don't know what I was thinking when I thought up the idea for the project but my lab partner was too inexperienced to know any better so he went along with it thinking that if I said we could do it that we could. In the end, the presentation day was both dissapointing and pleasantly surprising because we thought we were screwed and would have to repeat the lab class but so many visitors from companies who were the judges said we couldn't win because it didn't work but they told our professor that we shouldn't get an F because we had the guts to try something really challenging while everyone else picked easy projects that were a slam dunk to pass the course. At first the professor came over and told us he was changing our F to a D, but this went on all day long and then later he came over and told us he was changing our D to a C and before the day was over he change the C to a B- . We still can't believe it but we not only passed, it didn't ruin our GPAs
I understand the professor's viewpoint. He can't just let the students pick difficult projects and change them at the last minute because they failed. It doesn't work that way in the real world and he doesn't want his students to think they can get away with making poor decisions.
You know what they say"
"Good decisions come from experience. Experience comes from making bad decisions..."
now that should explain everything . the main problem is the fact that the analog switches are too slow in practice as they mess everything up , the multiplexers and latches are fine but the switcher chips are inefficient and wasteful , they must then be replaced by other components or more efficient logic .
what do you this of the whole setup Mr Reschemmel ? how can i improve it ? and how can i replace the switches ?
Part numbers ? (WHAT analog switches ?)
It's hard to comment because I don't know the part numbers and I don't know how committed you are to this design. Can't you slow everything down ?