This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Coldfire/M68K 32 bit RAM access?


I'm working on a custom embedded Coldfire processor board that has 512K of SRAM on it.
This SRAM only allows 32 bit reads and writes, and the lower two address bits do not connect to the coldfire.
There is nothing on the board to try to compensate for this either. I had worked with other boards that had an EDAC that would do a read-modify-write operation for 8 or 16 bit operations.


Am I correct in thinking that GCC compiled code will not run on this?

I see immediate problems when I move the stack from internal ( on chip ) SRAM to this on-board SRAM.

I tried the -malign-int option and that seems to help with the stack alignment, but I cant see how I could constrain GCC to never do anything other than 32 bit word accesses?
Does this sound right?


Thanks,
Alan Cudmore


------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]