All the CFM registers (e.g. CFMPROT, SACC, DACC) are zeroed or have what seem like very friendly values, where appropriate.
The eval board has a system clock of 48mhz, so the CFMCLKD is 0xce (scaled by 8, divided by 15 (0xe + 1)).
First problem:
Example code and tortured reading of the "documentation" seems to indicate that one would, say, check whether the flash is erased or not by doing something like this:
*((uint32 *) 0x1000) = 0xFFFFffffLU;
MCF_CFM_CFMCMD = MCF_CFM_CFMCMD_RDARY1; // _RDARY1 is 0x5
MCF_CFM_CFMUSTAT = MCF_CFM_CFMUSTAT_CBEIF;
Then wait for the CBEIF and CCIF bits to come high and see whether the BLANK bit is high (at any time).
With a completely erased flash, the BLANK bit never comes high. In fact, using similar logic to erase the flash or to program a word in the flash seems to have no effect on the flash.
Second problem:
That assignment statement to the flash memory causes a bus error. An rte interrupt handler seems to stop the fuss, but you gotta wonder.
So, I'm kinda out of ideas, here. Can anyone help with this?
Thanks,
Alex
Whoa! Thanks. The odd-ball address did the trick.
Yes, your code verified my guess that to start the ball rolling, one must write something to a flash address.
AND, your code gave me pause and triggered yet more reading until I found the note about halving the system clock rate before calculating the clock divisor. The note was at the end of the EZport "documentation". In fact, that seemed to be the only place that the system clock was mentioned in the "documentation". Elsewhere, it speaks of an undefined "internal Flash bus clock".
AND, your code jibed with the EZport "documentation" clock divisor calculation, as opposed to (if I read it right, which would be trick in itself) the CFM "documentation"'s clock divisor calculation. The two calculations appear different for clocks evenly divided by 200k.
But, I have no idea what manual you've got with a section 6.6. I'm using MCF5213RM.pdf for "documentation".
Anyway, thanks much!
Felix
Yes, your code verified my guess that to start the ball rolling, one must write something to a flash address.
AND, your code gave me pause and triggered yet more reading until I found the note about halving the system clock rate before calculating the clock divisor. The note was at the end of the EZport "documentation". In fact, that seemed to be the only place that the system clock was mentioned in the "documentation". Elsewhere, it speaks of an undefined "internal Flash bus clock".
AND, your code jibed with the EZport "documentation" clock divisor calculation, as opposed to (if I read it right, which would be trick in itself) the CFM "documentation"'s clock divisor calculation. The two calculations appear different for clocks evenly divided by 200k.
But, I have no idea what manual you've got with a section 6.6. I'm using MCF5213RM.pdf for "documentation".
Anyway, thanks much!
Felix
