This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Page writing to flash

Hey Guys, I am writing to my micro's flash one byte at a time using that APP note from NXP (AN10342_1), I saw that it is possible to write a page at a time. How do I go about writing a page at a time?

Thanx :)

Xarion

Parents
  • At least for the ARM chips, the UM does contain a lot of "only for xx" information, including the pinouts, part id codes, ... Basically everything a sw developer needs, with the exception of the ARM documents about the core and instruction set.

    It's just the ordering codes, electrical information (limits, static, dynamic, ADC precision...), temperature limits, mechanical tolerances, ... that are missing from the user manual.

    And the datasheets can have download names such as datasheet/lpc2364.lpc2365.lpc2366.lpc2367.lpc2368.pdf which clearly indicates that they are just as family-wide as the user manuals.

    The datasheets looks like "sell-in" documents, with a lot of bulleted lists with all features of the chips - something for an NXP application engineer to bring to a customer meeting to describe why the customer should select a specific chip or family.

    So in the end, it can lead to quite interesting times if a developer only gets the datasheet or only the user manual. Best practices always requires that a developer scoups up all documents (and sample code) that are available on the producers web site and quickly scan through them to figure out which documents that are applicable.

    In some situations, that isn't enough. The needed information may be missing but possible to deduce from the manuals from other processors (even from other families) from the same manufacturer.

Reply
  • At least for the ARM chips, the UM does contain a lot of "only for xx" information, including the pinouts, part id codes, ... Basically everything a sw developer needs, with the exception of the ARM documents about the core and instruction set.

    It's just the ordering codes, electrical information (limits, static, dynamic, ADC precision...), temperature limits, mechanical tolerances, ... that are missing from the user manual.

    And the datasheets can have download names such as datasheet/lpc2364.lpc2365.lpc2366.lpc2367.lpc2368.pdf which clearly indicates that they are just as family-wide as the user manuals.

    The datasheets looks like "sell-in" documents, with a lot of bulleted lists with all features of the chips - something for an NXP application engineer to bring to a customer meeting to describe why the customer should select a specific chip or family.

    So in the end, it can lead to quite interesting times if a developer only gets the datasheet or only the user manual. Best practices always requires that a developer scoups up all documents (and sample code) that are available on the producers web site and quickly scan through them to figure out which documents that are applicable.

    In some situations, that isn't enough. The needed information may be missing but possible to deduce from the manuals from other processors (even from other families) from the same manufacturer.

Children
No data