madbrumie

thats right, choas was made for the problems that was with the 2110 boxes, the grape and prune is fun card and the redneck is atmega. you will see in the files how to make your own .HEX as well, but will have to do your fixes first.

thanks nozzer as well mate, was trying to put the problem in as simple form as possible (not because i think anyone is thick but to help people understand it) and sometimes its hard to explain.

there is alot of info within the last few pages in this thread that will help to fix the problem, buti would say dont try and guess your way there just try to understand some of the code and what it does as this will help alot!
then also when you have some understanding and get stuck you can post up the info that your having problems with, and i am sure there are a few people that will be happy to help :-)

MB

cg010169

as i have before and im sure others would agree, the time, effort and information you and others have shared is very helpfull, as you didn't have to do anythink.


Had my little break now, while having a read over the guides again on how the card and box talk with each other.

I'm i right in thinking it's the Send ATR to IRD part of the code that needs to be changed.
Odds are it's wrong, butas im reading more, im seeing things a bit different each time lol

__________________

neorage

might i suggest reading here:
3_7 funcard fix here

i know its outside dw but theres a hell of a lot of in depth discussion there..

as far as im aware its nothing to do with the atr or the ird.. but the time in which it takes the card to respond..

similar to how the 2110 didnt work wit the net id setter

3.6 over looked these time problems and waited where as 3.7 is sticking to correct responce times

__________________

nozzer

Ok, as I suggested above, your going to have to investigate this problem by understanding how the system works and knowning what can go wrong. Pointing out relatively randon pieces of code and hoping thats whats wrong isn't going to work.

So, lets start right from the beginning !

Initially the processor is reset. This causes the processor to stop everything its doing, reset all its registers to a known state and then start executing from the reset vector location (Reset vector is at Address $0000).

In the assembly, you will find the reset vector easily enough as its the first real instruction. It may be proceeded by an assembler pseudo-op which tells the assembler to start producing code from address $0000

So, you have something like -

Now, as reset vector exists as the first entry within a table of vectors the instruction itself is usually only a jump instruction to real code. Notice that there may be other vectors defined within the table that give the addresses of routines that are called when certain hardware events occur.

So, lets look at Ext_RST

Here we have a few things happening. Various hardware registers are set up to the conditions we need them to be in, RAM is cleared to a zero state, I/O pins are setup, Stack is setup etc.....

After this you start to get to some real work. The ATR loop outputs the ATR on the cards ISO-I/O line at the predefined rate of 372 clks/bit. After that there's a little bit more initialisation of various values, specifically CmdC0/C1 response bytes. After that theres a little bit of initialisation for a timer. After that, your finally into the main loop, often called something like "Roll". After that, you basically just sit going round that loop waiting for something to happen.

Trace it through, make sure you can follow what i've described.

Now, from what i've described above, can somebody move forward and describe how serial Input is detected and captured ?

nb. I may not be working from the same source as you so what i've described above may have minor variations.

madbrumie

Nozzer beat me to it...lol

Pimped

Cool another learning thread.

Which source and which file should I be looking at nozzer? I had a look at autoroll.asm from Redneck, but that's just for rolling of keys.

__________________
Wars come and go but my soldiers stay eternal

nozzer

I think I was looking at an older version of the Prune stuff but tbh, it really doesn't matter as they are all pretty much the same general layout. If you want to suggest a particular source so everybody stays on the same page then go ahead.

Dont think i've got any source for the latest Fun/Mega AU methods so if anybody does then that would be the version to use.

Alternatively, just run the latest hex through a disassembler to give you something to work with. Not as pretty as the source code but if you work with both then you'll see what your doing easily enough

Pimped

I just opened up what madbrummie attached a few posts up. I would like to go for RedNeck as that was the choice in the Atmega Challenge thread, I'm reading up on StuntGuy's faq at the moment, so I doubt I'll be a model student at the mo. I'll be following things closely though

__________________
Wars come and go but my soldiers stay eternal

jasperconran

what could i use to do that with, And where is it found pls.

nozzer

IDApro is complex but it does a nice job of disassembling for just about any processor you would ever come across. You can usually find a version on newsgroups etc.