diff --git a/dependencies/tensorflow b/dependencies/tensorflow
index 0271523..e8e05bb 160000
--- a/dependencies/tensorflow
+++ b/dependencies/tensorflow
@@ -1 +1 @@
-Subproject commit 02715237c1fc0a23f465226364d206277f54ebce
+Subproject commit e8e05bb3b5909855702f6efee70d8672816ff293
diff --git a/docs/sections/timing_adapters.md b/docs/sections/timing_adapters.md
index 7ca7076..5db38c6 100644
--- a/docs/sections/timing_adapters.md
+++ b/docs/sections/timing_adapters.md
@@ -1,9 +1,9 @@
-# Building timing adapter with custom options
+# Timing adapter
 
-The sources contain the configuration for a timing adapter utility for the *Arm® Ethos™-U* NPU driver. The timing
-adapter allows the platform to simulate user provided memory bandwidth and latency constraints on platforms that
-support it. The timing adapter driver aims to control the behavior of two AXI buses used by *Ethos-U* NPU. One is for
-SRAM memory region, and the other is for flash or DRAM.
+The sources contain the configuration for a `Timing Adapter (TA)` utility for the *Arm® Ethos™-U* NPU driver. The
+timing adapter allows the platform to simulate user provided memory bandwidth and latency constraints on platforms that
+support it. It aims to control the behavior of two AXI buses used by *Ethos-U* NPU - one is for SRAM memory region, and
+the other is for flash or DRAM.
 
 The SRAM is where intermediate buffers are expected to be allocated and therefore, this region can serve frequent read
 and write traffic generated by computation operations while executing a neural network inference. The flash or DDR is
@@ -19,6 +19,8 @@
 > benchmarking for different bandwidth and latency conditions, we recommend using the Arm® Corstone™-300
 > implementations.
 
+## Building timing adapter with custom options
+
 The CMake build framework allows the parameters to control the behavior of each bus with following parameters:
 
 - `MAXR`: Maximum number of pending read operations allowed. `0` is inferred as infinite and the default value is `4`.
@@ -140,14 +142,17 @@
 Corstone-310 **FPGA** implements timing adapter blocks differently and those are placed on each of the main
 memories present on FPGA: SRAM, QSPI flash, DDR and user memory.
 Moreover, this timer adapter placement does not translate well to FVP, so current Corstone-310 FVP implementation does
-not support the feature. Additionally - base addresses of timer adapters blocks have changed for Corestone-310:
+not support the feature. Additionally - base addresses of timer adapters blocks have changed for Corstone-310.
 
-#### Timer Adapters for Corstone-300 FVP and FPGA:
+### Timer Adapters for Corstone-300 FVP and FPGA:
+
 | TA# | Interface TA is placed on | Base address (non-secure/secure) | Size  |
 |-----|---------------------------|----------------------------------|-------|
 | 0   | M0/AXI0 for Ethos-U NPU   | 0x4810_3000/0x5810_3000          | 0.5KB |
 | 1   | M1/AXI1 for Ethos-U NPU   | 0x4810_3200/0x5810_3200          | 0.5KB |
-#### Timer Adapter for Corstone-310 FPGA:
+
+### Timer Adapter for Corstone-310 FPGA:
+
 | TA# | Interface TA is placed on | Base address (non-secure/secure) | Size |
 |-----|---------------------------|----------------------------------|------|
 | 0   | FPGA SRAM                 | 0x4170_0000/0x5170_0000          | 4KB  |
@@ -155,4 +160,5 @@
 | 2   | DDR                       | 0x4170_1000/0x5170_2000          | 4KB  |
 | 3   | User memory               | 0x4170_3000/0x5170_3000          | 4KB  |
 
-With this in mind, when targeting Corstone-310, evaluation kit should be built with timing adapters disabled altogether via `-DETHOS_U_NPU_TIMING_ADAPTER_ENABLED=OFF` flag. Because timing adapters do not affect CPU-driven traffic for Corstone-300, building both platforms without the support for timing adapters allows for a CPU performance comparison.
\ No newline at end of file
+This is why the evaluation kit is configured with timing adapters disabled altogether (parameter
+`ETHOS_U_NPU_TIMING_ADAPTER_ENABLED` set to `OFF`) for Corstone-310 target platform. 
diff --git a/scripts/cmake/tensorflow.cmake b/scripts/cmake/tensorflow.cmake
index ac11542..24227d9 100644
--- a/scripts/cmake/tensorflow.cmake
+++ b/scripts/cmake/tensorflow.cmake
@@ -51,10 +51,7 @@
 else()
     set(TENSORFLOW_LITE_MICRO_TARGET "cortex_m_generic")
 
-    if ("${CMAKE_SYSTEM_ARCH}" STREQUAL "armv8.1-m.main" OR "${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "cortex-m85")
-        # TensorFlow's generic makefile doesn't currently have a flow for Cortex-M85.
-        # We build for Arm Cortex-M55 instead.
-        # @TODO: check with latest TensorFlow package.
+    if ("${CMAKE_SYSTEM_ARCH}" STREQUAL "armv8.1-m.main")
         set(TENSORFLOW_LITE_MICRO_TARGET_ARCH "cortex-m55")
     else()
         set(TENSORFLOW_LITE_MICRO_TARGET_ARCH "${CMAKE_SYSTEM_PROCESSOR}")