??? 07/08/08 18:29 Read: times |
#156539 - Erik Responding to: ???'s previous message |
I have those, read those, and have been aware of the structures um (bible)......for years. Show me where in the bible where C is explained.....it isn't.
My issue at hand is how to tell C to use arrays in RAM for my array variables so that they won't get corrupted. I need the data saved, I don't have any external RAM or storage, so it HAS to be internal. I obviously can't do a volatile in code space, basics 101 (bible), so my issue is what is the best way to write/tell/force C to put these arrays in spots that hopefully won't get corrupted.......or would it be a better idea just to have these arrays as global variables. My issue is not the asm commands (which are useless > Bible), or the hardware architecture.....its the "C" component. All of my work in the past was assembly and mnuemonic programming. C was not. That is why I keep faultering. I've gone through and watch the how to code C and C++ videos. That is all well and great until I actually have to code my specific examples for my specific process. Its not like I haven't tried, its just not completely clear. The last I checked I NEVER ASKED FOR GIMMIE CODE, just help. I thought, this was a place to come and ask questions and ask for guidance.....I wasn't aware it was www.rtfm.com even though, in our opinion, you don't know every single detail therefore you must not know the basics.......BS. I believe the questions I'm asking are far from basics, go stop a person on the street and ask them what the accumulator or B register is......THAT is a person that doesn't know "the basics"...... If you have the book "C and the 8051", pick it up and go to page 48 were arrays start and end of page 56, where in there does it explain about array corruption, or any of the questions i've asked thus far, again it doesn't. It is fortunate that many have the proper debuggers, hardware ICE, and experience to know these pitfalls. If one does not wish to help, posting about rtm is not going to solve or help anyone.....that is just the way it is. I could read those back and forth, it [I]still[/I] doesn't solve the problem....but that is JMO. Believe me when I say, I'm not mad, upset, or moved either way, as I mentioned before, there have been quite a few great people on this site who have helped me privately (gee, I wonder why that is), I'm just commenting on what seems to be an apparent trend NOT to help and look down and point to the manual......<must be tough being that good eh?> But thanks for the links anyway, even though it still doesn't solve my problem and/or "basics" understanding. Just think about it.....no response is required. Best Regards, |
Topic | Author | Date |
Data Array getting corrupted after init | 01/01/70 00:00 | |
OnePossibleIdea.... | 01/01/70 00:00 | |
I did not do anything with the stack | 01/01/70 00:00 | |
As Michael said.... | 01/01/70 00:00 | |
How do you test and debug code? | 01/01/70 00:00 | |
Keil is the only thing in place | 01/01/70 00:00 | |
'crap'?? | 01/01/70 00:00 | |
Is this the book you refer? | 01/01/70 00:00 | |
nope | 01/01/70 00:00 | |
Erik | 01/01/70 00:00 | |
So where is the code | 01/01/70 00:00 | |
do NOT "put them" | 01/01/70 00:00 | |
Focus | 01/01/70 00:00 | |
Simulator | 01/01/70 00:00 | |
So this is on a simulator? | 01/01/70 00:00 | |
Post your duff code | 01/01/70 00:00 | |
Finding Cause of Corruption | 01/01/70 00:00 | |
Get the C right, then look at the target CPU | 01/01/70 00:00 | |
Optimizing Compilers | 01/01/70 00:00 | |
In my experience..... | 01/01/70 00:00 | |
Keil C 51 Optimizations | 01/01/70 00:00 | |
Use IAR then | 01/01/70 00:00 | |
different approaches | 01/01/70 00:00 | |
sometimes, depends | 01/01/70 00:00 | |
Thanks![]() | 01/01/70 00:00 |