| Rob Stoffels 06/10/09 12:46 Read: 260 times Westerlo Belgium |
#165995 - Going to try something different Responding to: Andy Neil's previous message |
Andy Neil said:
That sounds really strange: as far as loading the code into the Flash is concerned, it should just be a blob of data - so the content of the code shouldn't make any difference whatsoever!
Are you sure that it is really not getting written to the flash? Are you able to load programs correctly that don't use "external ram features" ? no i'm have not, the funny thing is as soon as the code gets "bigger" then setting 2 output ports it won't go into the device... I've been breaking my mind about this issue like crazy, 7 lines of code, won't get programmed.i feel like a µc retard 8-)... If i find that FLIP gnome messin up ma code ;)... anyway, These development boards do have been lying around for 5+ years without use, is there a chance they are broken? Since this code is eventually meant to be implemented in a at89c51cc03 (which we currently have only embedded in an application) i am considering 2 options: 1. just write code for the cc03 and flash it in there and look what happens. we've got spares so... 2. Make a new development board for the cc03 and do tests on that one. (will result in waiting time for the PCB) I'll do the first one straight away tomorrow, if it's able to flash, then I will write some code using XDATA and take into acount the large memory model. and proceed tests. At the same time i'll just design some sort of test pcb for the cc03 since it will be needed in a later stadium. David Prentice said:
I would commonly use all ports for i/o and use no external memory at all. But if you want to use xdata you need to generate the requisite MOVX instructions. In the end there should be a bus of 16 parallel programmable devices, with this method you only need to write a parameter to a certain address and all the rest will be taken care of (read, write, ale,...). thanks for the support so far! I'll keep you informed! |
