Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Scripts to support NXP LPC chips
#6
If that's the purpose then we can skip it. The length of the buffer is always equal to the length of the changes in the sector. If the sector is just half filled then EBlink will skip all trailing 0x00 (the erase value set by the device API) because it's already cleared by the sector erase.

Sometimes a MCU needs a full sector size to program and with the
Code:
DeviceApi::setFlashDontTrim()
  option we can disable the sector trimming. But even then a sector will never be written with some lefts over of buffers. On sector erase the internal sector cache is reset to the earseValue and the content of the sector cache is passed by the EBuffer.
Reply


Messages In This Thread
Scripts to support NXP LPC chips - by jdubois - 12-04-2023, 05:18 PM
RE: Scripts to support NXP LPC chips - by embitz - 12-04-2023, 06:26 PM
RE: Scripts to support NXP LPC chips - by jdubois - 12-04-2023, 06:54 PM
RE: Scripts to support NXP LPC chips - by embitz - 13-04-2023, 09:09 AM
RE: Scripts to support NXP LPC chips - by jdubois - 16-04-2023, 08:28 PM
RE: Scripts to support NXP LPC chips - by embitz - 17-04-2023, 08:17 AM
RE: Scripts to support NXP LPC chips - by embitz - 17-04-2023, 08:23 AM
RE: Scripts to support NXP LPC chips - by jdubois - 17-04-2023, 03:15 PM
RE: Scripts to support NXP LPC chips - by embitz - 17-04-2023, 09:39 PM
RE: Scripts to support NXP LPC chips - by jdubois - 18-04-2023, 12:43 AM
RE: Scripts to support NXP LPC chips - by jdubois - 20-04-2023, 04:20 PM
RE: Scripts to support NXP LPC chips - by embitz - 20-04-2023, 07:01 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)