Searched refs:running (Results 1 – 8 of 8) sorted by relevance
| /mcuboot-2.7.6/ptest/src/ |
| D | main.rs | 81 running: HashSet<String>, field
98 running: HashSet::new(), in new()
106 if self.running.contains(&key) || self.done.contains(&key) { in start()
109 debug!("Starting: {} ({} running)", key, self.running.len() + 1); in start()
110 self.running.insert(key); in start()
116 self.running.remove(&key); in done()
143 self.running.len()); in done()
155 let running = self.running.len(); in status() localVariable
157 print!(" {} running ({}/{}/{} done)\r", running, done, running + done, self.total); in status()
|
| /mcuboot-2.7.6/docs/ |
| D | testplan-zephyr.md | 13 ## Building and running.
49 And you should see a revert and "hello1" running.
|
| D | readme-zephyr.md | 20 Currently, the two image slots must be contiguous. If you are running
70 directory you chose when running `cmake`. Use the Zephyr build
71 system `flash` target to flash these binaries, usually by running
137 Generating a keypair with imgtool is a matter of running the keygen
|
| D | testplan-mynewt.md | 3 The current target for running the tests is the Freedom K64F board.
|
| D | PORTING.md | 49 After running the management functions of the bootloader, `boot_go` returns
|
| D | release-notes.md | 311 - This release supports building with and running Apache Mynewt and Zephyr
313 - RIOT is supported as a running target.
|
| /mcuboot-2.7.6/boot/cypress/BlinkyApp/ |
| D | Readme.md | 7 It is started by MCUBoot Application which is running on CM0p.
|
| /mcuboot-2.7.6/ext/tinycrypt/documentation/ |
| D | tinycrypt.rst | 159 application is running in a constrained environment. AES-256 requires keys
|
