Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
09/07/06 13:53
Modified:
  09/07/06 13:55

Read: times


 
#123831 - there is no mystery, just information or lack of
Responding to: ???'s previous message
Erik Malund said:
Jan, do you really want a datasheet that bend everything in neon or cut it out in cardboard making the datasheet 1247 pages long.

The SST datasheet is not more than 91 pages long and much more clear than the Philips' on many aspects of the - apparently same - chip.
Of those 91, 8 pages deal with every aspect of FLASH programming, both IAP and parallel, and is absolutely crystal clear. They even didn't bother to include details on ISP itself, as those are available in form of separate appnotes, related to the bootloader (and associated toolset, including SoftICE) rather than the chip itself, IIRC.

Erik said:
If you can not understand from the statement above that "occupying 0--- of code memory" will make interrupts a no-no, then it is "bible time"

I see nothing in "bible" nor in the datasheets preventing me to put the interrupt vectors and appropriate service routines into both parts of flash, nor that if the appropriate vectors are set and the service routines are present in the "boot flash", those interrupts won't work.

Now, Erik, some two years ago you complained on the P89V51RD2 bootloader that it does not support programming over RS485. That was the impulse why I started to look closer at these chips at all, and today I use them for most of my hobby work. And, of course, the modified bootloader supporting RS485 programming is available from my website, please, try it.

My only concern is, that this all was worked out from the suspicion - and all the evidence point into that way - that the SST and Philips parts are the same. So, until Philips admits that this is the case, or until they produce a datasheet equivalent (or hopefully better) in content to SST's, I cannot say "that's it, 100%". This is also the reason why I am using them only for hobby - I simply don't like poorly documented chips (especially if I know that better documentation IS around...)

Jan Waclawek


List of 23 messages in thread
TopicAuthorDate
IAP and serial port receiving problem            01/01/70 00:00      
   Who knows!            01/01/70 00:00      
      IAP and serial port receiving problem            01/01/70 00:00      
         Need a better protocol!            01/01/70 00:00      
            if it's e.g. a datalogger, he can't change it...            01/01/70 00:00      
               Jan, do you really want            01/01/70 00:00      
                  there is no mystery, just information or lack of            01/01/70 00:00      
            DIsable            01/01/70 00:00      
               Partial solution            01/01/70 00:00      
                  If i            01/01/70 00:00      
                     Not necessarily            01/01/70 00:00      
   problems with interrupts in IAP            01/01/70 00:00      
      if and if not            01/01/70 00:00      
   Did not someone tell, ...            01/01/70 00:00      
      as in life, only if you follow the rules            01/01/70 00:00      
         Oh yes it does!            01/01/70 00:00      
         What I meant...            01/01/70 00:00      
            it does, when he does not interrupt            01/01/70 00:00      
      serial IAP?            01/01/70 00:00      
   If data is coming from PC            01/01/70 00:00      
      I doubt the OP would ask if he could            01/01/70 00:00      
         how does address vector can be copied into Block1            01/01/70 00:00      
            block1            01/01/70 00:00      

Back to Subject List