Searched +full:56 +full:ns (Results 1 – 6 of 6) sorted by relevance
36 each MCK cycle will be equivalent to 8ns. Since the memory full cycle is37 55ns, as per specification, it requires atmel,smc-cycle-timing of at least38 7 pulses (56ns). The atmel,smc-cycle-timing is composed of three parts:41 is66wv51216dbll-55 a minimum setup of 5ns (1 cycle) with at least 45ns
112 bool "25ns"114 bool "100ns"116 bool "250ns"281 default 56 if PTP_DSCP_HIGH_PRIORITY
89 (``-DBOARD=mps2/an521/cpu0/ns``).96 west build -p -b mps2/an521/cpu0/ns samples/tfm_integration/psa_crypto105 cmake -GNinja -DBOARD=mps2/an521/cpu0/ns ..115 cmake -DBOARD=mps2/an521/cpu0/ns ..142 Build Zephyr with a non-secure configuration (``-DBOARD=mps2/an521/cpu0/ns``)150 west build -p -b mps2/an521/cpu0/ns samples/tfm_integration/psa_crypto -t run159 cmake -GNinja -DBOARD=mps2/an521/cpu0/ns ..169 cmake -DBOARD=mps2/an521/cpu0/ns ..203 (``-DBOARD=nrf5340dk/nrf5340/cpuapp/ns`` or ``-DBOARD=nrf9160dk/nrf9160/ns``).212 cmake -GNinja -DBOARD=nrf9160dk/nrf9160/ns ..[all …]
151 * - 0: I2C device has a 50 ns spike filter where153 * - 1: I2C device does not have a 50 ns spike filter155 * - 2: I2C device does not have a 50 ns spike filter187 * I2C device has a 50 ns spike filter where it is not affected by high195 * I2C device does not have a 50 ns spike filter but can work with high203 * I2C device does not have a 50 ns spike filter and cannot work with high232 * The I2C devices have 50ns spike filter on SCL.238 * The I2C devices do not have 50ns spike filter on SCL245 * The I2C devices do not have 50ns spike filter on SCL2065 * D: I3C msg: testing, addr=56
3 …ns</b></font></div></div></div></foreignObject><image x="12" y="17.5" width="698" height="59.5" xl…
348 …phy1oYP9rl4i5bOPnhEOE2YBgRtm61+dGP9DHY2mg4mUh30UvP8LdsyWbFS6Po/gUM6lDEhLDF+56q8QAwBLSNN304+pBatG1q…555 "Epoch 56/500\n",1503 …bv/OZg8GUaNqtefbTVKBEmgcFUhd7x2BzOWzaj3Nj079aRVSit6d+ldqU9BRFoeJYIkEksIr69+nS+2frFX2x6cdTCZrTLpkNm…1888 "Epoch 56/500\n",
