0

Memory problem [solved]
Moderators: altitude, adafruit_support_bill, adafruit, phono, hamburgers

Please be positive and constructive with your questions and comments.

Memory problem [solved]

by kroffe on Fri Jan 23, 2009 2:41 am

So I successfully built my selfsourced x0xb0x - I thought. :(

I turns out that I can't save any patterns. When I use pattern edit mode (stock OS 1.5) and program a pattern, "Done"-LED flashes like it should but when I press it and choose another pattern, the pattern I just save is lost.

The x0xb0x behaves just like it doesn't recognise the AT25320 EPROM. I actually tried running it without the EPROM in the socket it verify this. I've also looked for bad soldering, shorts and checked continutiy around this circuit IC2.

Could I've overlooked something? Is the AT25320 EPROM supposed to be "initialized" in some way before use???

thanks,
kroffe
Last edited by kroffe on Tue Feb 10, 2009 2:55 am, edited 1 time in total.
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by guest on Fri Jan 23, 2009 3:46 am

you should make sure that the eeprom chip is the right one
i have a 25c33p in mine
but there are a lot of equivalents out there
so yours might be the same
guest
 
Posts: 3155
Joined: Fri Feb 17, 2006 5:35 am

Re: Memory problem

by kroffe on Fri Jan 23, 2009 4:32 am

Off course, but my buddy who also built a selfsourced x0xb0x with the same EPROM (AT25320) got his to work... so ...

Will try to test swapping chip with his x0x to verify that the chip itself is not faulty.

Other thoughts?
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by guest on Fri Jan 23, 2009 4:44 am

swapping chips is a good idea
you can also double check all the connections with a multimeter
remove the eeprom and the microncontroller
and measure the resistance
between the various places the traces are supposed to run
and then make sure there are no shorts
between adacent pins or ground

if that all turns out fine
and it doesnt work with the other eeprom
then id try reflashing the firmware
or swapping micrcontrollers as well
just to see if the problem is on the spi lines

do the buttons and lights work as they should

the only other thing it could be is ic1
that switches the spi line between the buttons and the eeprom
guest
 
Posts: 3155
Joined: Fri Feb 17, 2006 5:35 am

Re: Memory problem

by kroffe on Fri Jan 23, 2009 4:57 am

OK, since I've already checked continuity of the traces between IC2-socket and everything else, I guess swapping chips and reflashing firmware is the way to go.

All buttons and LEDs work as they are supposed to.

Thanks for pondering this issue. :)
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by kroffe on Mon Jan 26, 2009 2:57 pm

Now I've flashed my x0x with SokkOS, which is working great, aside from the fact that it still doesn't remember patterns. Will try getting another EPROM. :(
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by guest on Mon Jan 26, 2009 3:06 pm

did you try swapping eeproms
guest
 
Posts: 3155
Joined: Fri Feb 17, 2006 5:35 am

Re: Memory problem

by kroffe on Mon Jan 26, 2009 3:56 pm

Haven't met up with my buddy with the working selfsourced x0x of same sources yet.. :wink:
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by kroffe on Sat Jan 31, 2009 12:09 pm

Today I borrowed my buddys x0xb0x for tuning and control of his EPROM which functioned fine in my x0xb0x. It turns out that the EPROM I got and his were to slightly different kinds. His was named ATMEL724 25320 PI A while my nonfunctioning chip was named ATMEL726 25320 PI. Strange, considering both chips comes from the same distributor.
Haven't had the time checking exactly what 726 vs 724 means in terms of speccs but I guess I found the source of error...

I also did a little x0xb0x vs TB-303 movie that I put onto the tube:
http://www.youtube.com/watch?v=Y2a4SaZ1bx8

/kroffe
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by kroffe on Sun Feb 01, 2009 9:55 am

Here's a picture of the two different AT25320 32K EEPROMs.
Apparently the one called ATMEL724 25320 PI seems to work with my x0xb0x, but the other does not.
I still haven't figured out why? :?:
Attachments
724vs726.jpg
AT25320 32K EEPROMs
724vs726.jpg (32.79 KiB) Viewed 3403 times
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Re: Memory problem

by guest on Sun Feb 01, 2009 10:16 am

i think 724 vs 726 is the datecode
and isnt the problem between the two

the main issue is that one is an at253320a
and the other is an at25320
this is probably due to the maximum clock rate
of the at25320 being 3MHz
whereas the other is 20MHz
im not sure what the x0x clocks at
but its probably above 3MHz
guest
 
Posts: 3155
Joined: Fri Feb 17, 2006 5:35 am

Re: Memory problem

by Sokkan on Sun Feb 01, 2009 10:42 am

The 'b0x uses a 16MHz resonator. You need the 25320a(or b). edit:WRONG!

It is strange that you got the two in the same batch, unless 25320s without suffix was ordered... :(
Last edited by Sokkan on Sun Feb 01, 2009 1:16 pm, edited 1 time in total.
Sokkan
 
Posts: 240
Joined: Sat Sep 01, 2007 12:56 pm
Location: Stockholm

Re: Memory problem

by guest on Sun Feb 01, 2009 12:25 pm

i just checked my x0x
and the spi line runs at 1MHz

so im not certain what the problem is
perhaps the chip was just bad
guest
 
Posts: 3155
Joined: Fri Feb 17, 2006 5:35 am

Re: Memory problem

by Sokkan on Sun Feb 01, 2009 1:21 pm

guest wrote:i just checked my x0x
and the spi line runs at 1MHz


Yep, you're right, I was wrong. 8)
The manual also indicates that the 162 runs its internal EEPROM at 1MHz independent of the clock frequency of the CPU.

Kroffe, the 25320 you got is borked, just try to buy a new one. :(
Sokkan
 
Posts: 240
Joined: Sat Sep 01, 2007 12:56 pm
Location: Stockholm

Re: Memory problem

by kroffe on Sun Feb 01, 2009 5:37 pm

OK. Thanks to everyone for helping me getting to the bottom of this. I'll order a new IC a soon as I can... :)
kroffe
 
Posts: 37
Joined: Wed Jan 21, 2009 3:04 am

Please be positive and constructive with your questions and comments.