Hello!
I seek to find help here, because we across a problem we don't seem to be able to solve. But perhaps has an idea...
Following: for a power supply we sell we use AT89C51CC03 as main controller. It has 64k flash. The bootloader is mapped into the addressable memory at 0xF800. In order to be able to update the microcontroller firmware (i.e. ISP), we used to send a command from outside, which let our code jump to the bootloader by API calls. With the time, the code grew. Some versions earlier, jumping into bootloader worked fine. It means, we just sent the command, the controller jumped into bootloader, initialised the UART (which is connect to USB, making a VCOM port on the PC side) and we could then instantly access the Atmel chip via FLIP. In some newer versions, the code grew bigger and now has 63.2k, making its end address being around 0xFD30. We didn't realize so far, because we usually only test the code itself, but not if the update still works. And now, neither jumping to bootloader nor setting the BLJB via API calls works anymore.
Did we cross a magic border? A border which is at 0xF7FF?
I read the UART bootloader documentation and the AT89C51CC03 manual, I found no hint about that using up all of the 64k flash memory could result in such a problem. But it seems, it's exactly caused by now having code with end address >0xF7FF.
Question now is: how to access the bootloader and how to update the firmware without forcing the chip to bootloader with PSEN?
Thanks for any advice.
You don't have to be rude. Thanks for your help.
I think I need to elaborate why I have gotten rude:
Besides: the uVision F1 help is a CHM (uv4.chm) file that is called from the help menu. Since it is quite big, it's not to easy to find the right page.
I think it is not difficult to find the right page. Because I read the entire thing before I ever got the idea to waste other people's time on my problems. I haven't read everything in detail (i.e. I skimmed a lot of parts), but still I looked over everything and have a firm idea of what I can find in there.
This is the standard I ask anyone else to meet. Otherwise you are just a parasite. People invested a lot of time into creating that documentation and you're spitting into their faces.
When someone posts something that can be found in the manual in reply to a question I asked, I'm deeply insulted. Because it means people think I am that kind of person.
Now would be a good idea to calm down a bit.
Well, the solution was here, on Keil's website, not in the documents that come with UV. The BL51 solution still does not work, but is given by Keil for UV4 and BL51. So I'm in doubt whether I was wrong or them.
See, Dominic, as I said above: you can read as much as you want and they could have spent a lot of time writing such documents - all doesn't matter if the information is wrong.
My job is to write technical documentation for the power supplies we produce. People often phone us about things that is all written in the documents, but they don't read. Sometimes I want to shout Please read the manual! But we don't do, of course. Being lazy is in the nature of man. Asking people who know is easier than learning all yourself. Else we all would be highly trained specialists and that wouldn't work either.
So what I posted didn't work?
Because that's all from the documentation that came with µV and I tested it.
"parasite", "idiot", what's happening here recently...?
For the OP the problem is (one of) his biggets issue(s). For a responder it is taking time away from his day job.
An OP wants his problem solved NOW!! regardless of his description being incomplete e.g. 90% of the posters with code snippets do not follow instructions and do not consider it their fault. Also, quite a few posts are of the nature "it is faster to ask here than to read the documentation".
A responder may take time away from his paid job to reply and does thus have no desire to try to help OPs that e.g. are too lazy to read the documentation.
so the responder posts "Please read the manual" and the OP goes ballistic.
The responder does not appreciate being called whatever the OPs chosen expletive is and, Tamit, that is what is "happening here recently".
Erik