Change log

See the following list for an overview of changes from previous versions of this document.

Table 1. Change log
Version Date Change
nRF52832 Engineering A v1.2 05.07.2016
  • Updated: No. 11. “Device is unable to stay in System OFF mode”
  • Added: No. 84. “ISOURCE not functional”
  • Added: No. 86. “Triggering START task after offset calibration may write a sample to RAM”
  • Added: No. 87. “Unexpected wake from System ON Idle when using FPU”
  • Added: No. 88. “Increased current consumption when configured to pause in System ON idle”
  • Added: No. 97. “High current consumption in System ON Idle mode”
nRF52832 Engineering A v1.1 17.02.2016
  • Updated: No. 16. “RAM may be corrupt on wakeup from CPU IDLE”
  • Updated: No. 30. “STOP Task is not functional”
  • Updated: No. 57. “NFC Modulation amplitude”
  • Updated: No. 70. “Not able to wake CPU from System ON IDLE”
  • Updated: No. 73. “Event lost”
  • Updated: No. 78. “High current consumption when using timer STOP task only”
nRF52832 Engineering A v1.0 19.01.2016
  • Created separate document for IC revision Engineering A.
  • Added: No. 57. “NFC Modulation amplitude”
nRF52832-PAN v1.2 11.12.2015
  • Added: No. 67. “Some events cannot be used with the PPI”
  • Added: No. 68. “EVENTS_HFCLKSTARTED can be generated before HFCLK is stable”
  • Added: No. 70. “Not able to wake CPU from System ON IDLE”
  • Added: No. 71. “RCOSC calibration”
  • Added: No. 72. “TASKS_ACTIVATE cannot be used with the PPI”
  • Added: No. 73. “Event lost”
  • Added: No. 74. “Started events fires prematurely”
  • Added: No. 77. “RC oscillator is not calibrated when first started”
  • Added: No. 78. “High current consumption when using timer STOP task only”
nRF52832-PAN v1.1 09.10.2015
  • Added: No. 31. “Calibration values are not correctly loaded from FICR at reset”
  • Added: No. 58. “SPIM clocks out an additional byte when RXD.MAXCNT = 1”
  • Added: No. 63. “DC/DC does not automatically switch off in System ON IDLE”
  • Added: No. 64. “Only full bytes can be received or transmitted”
  • Added: No. 65. “RAM[] registers mapping of RAM block and sections is wrong”
nRF52832-PAN v1.0 15.06.2015
  • Added: No. 1. “I2S not functional”
  • Added: No. 2. “PWM not functional”
  • Added: No. 3. “PDM not functional”
  • Added: No. 4. “MWU not functional”
  • Added: No. 7. “Cache is not functional”
  • Added: No. 8. “Increased current consumption in system ON-IDLE”
  • Added: No. 9. “Some features are not functional”
  • Added: No. 10. “RTC2 is not functional”
  • Added: No. 11. “Device is unable to stay in System-Off mode”
  • Added: No. 12. “Reference ladder is not correctly calibrated”
  • Added: No. 15. “RAM[x].POWERSET/CLR read as zero”
  • Added: No. 16. “RAM may be corrupt on wakeup from CPU IDLE”
  • Added: No. 17. “The EVENTS_FIELDLOST is not generated”
  • Added: No. 20. “Register values are invalid”
  • Added: No. 23. “END event is generated before ENDTX”
  • Added: No. 24. “The FIELDPRESENT register read is not reliable”
  • Added: No. 25. “Reset value of SENSRES register is incorrect”
  • Added: No. 26. “NFC field does not wakeup the device from emulated system OFF”
  • Added: No. 27. “Triggering NFCT ACTIVATE task also activates the Rx easyDMA”
  • Added: No. 28. “Scan mode is not functional for some analog inputs”
  • Added: No. 29. “Incorrect bits in ERRORSRC”
  • Added: No. 30. “STOP task is not functional”
  • Added: No. 32. “Debug session automatically enables TracePort pins”
  • Added: No. 33. “Code RAM is located at wrong address”
  • Added: No. 34. “Code and Data RAM are not mapped from the same physical RAM”
  • Added: No. 35. “HFCLK can draw current when not requested”
  • Added: No. 36. “Some registers are not reset when expected”
  • Added: No. 37. “Encryption engine is slow by default.”
  • Added: No. 38. “Enable/disable tasks for channel group 4 and 5 cannot be triggered through PPI”
  • Added: No. 39. “The automatic collision resolution does not handle CRC and parity errors”
  • Added: No. 40. “The FRAMEDELAYMODE = WindowGrid is not supported”
  • Added: No. 41. “PIN_CNF[x] registers not reset after pin reset”
  • Added: No. 42. “FORK on the fixed channels is not functional”
  • Added: No. 43. “SPIS0 is not functional”
  • Added: No. 44. “Read after flash erase is unpredictable”
  • Added: No. 46. “EasyDMA list not functional”
  • Added: No. 47. “Trace is not functional”
  • Added: No. 48. “SWO only works if Trace is enabled.”
  • Added: No. 49. “RTC is not functional after LFCLK is restarted”

Documentation feedback | Developer Zone | Subscribe | Updated 2016-07-05