Abstract: A lock management system manages access to a controlled environment by locking or unlocking a door. The lock management system can actuate one or more components of a lock system to lock or unlock the door. To determine whether to lock or unlock the door, the lock management system can establish a connection with one or more devices. The lock management system can receive an access credential via the connection and authenticate the access credential. Based on authenticating the access credential, the lock management system can lock or unlock the door. The lock management system can monitor a door status and/or door activity and provide alerts to a user computing device.

Abstract: Hardware resource sharing for a computerized system running software tasks. A mutex controller is associated with the hardware resource. Lock and unlock indicators are settable by a software task and readable by the controller, and locked and waiters flags are settable and readable by the controller. The controller monitors whether the lock indicator has been set and determines whether the locked flag is set. If not, it sets the locked flag and, if so, it sets the waiters flag and asserts a mutex interrupt signaling the computer system to divert the software task to run a lock request routine. The controller also monitors whether the unlock indicator has been set and then determines whether the waiters flag is set. If not, it clears the locked flag and, if so, it asserts a mutex interrupt signaling the computer system to divert the software task to run an unlock request routine.

Abstract: Hardware resources sharing for a computer system running software tasks. A controller stores records including a mutex ID tag and a waiter flag in a cache. Lock and unlock registers are readable by the controller and loadable by the tasks with a mutex ID specifying a hardware resource. The controller monitors whether the lock register for loading with a mutex ID, and then determines whether it corresponds with the tag of a record in the cache. If so, it sets the record's waiter flag. If not, it adds a record having a tag corresponding with the mutex ID. The controller also monitors whether the unlock register for loading with a mutex ID, and then determines whether it corresponds with the tag of a record in the cache. If so, it determines whether that record's waiter flag is set and, if so, it clears that record from the cache.

Abstract: A system for handling debug log messages in a computerized device under test that has a filesystem and a communications link. A virtual debug folder provides one or more virtual folders wherein the debug log messages are stored as synthesized filenames. The virtual folders are then viewable via the communications link as if actual folders of the filesystem and the synthesized filenames are viewable via the communications link as if actual filenames of the filesystem.

Abstract: A system for a universal serial bus (USB) device to perform power configuration to operate with a USB host. A connection to the USB host is enabled. Then a high-power configuration is reported to the USB host and successful enumeration by the USB host is monitored for. If such enumeration is not forthcoming within a preset time, the connection to the USB host is disabled and re-enabled, and a low-power configuration is then reported to the USB host. Optionally, the system can further ramp up power usage until a preset high-power configuration is reached, or until there is voltage sag on the VBUS and then either ramp power usage back down or measure the sag and set to a calculated power usage.

Abstract: A system for a block storage client to work with data blocks in a virtual filesystem (VFS) where the actual data for the data blocks is stored in a real filesystem (RFS). A virtual block mapping table caches references to the actual data in files and directory structures of the RFS. A read mapper then accesses the files and directory structures based on the cached references in the virtual block mapping table, and constructs the data blocks from the files or synthesizes them from the directory structures. And a VFS interface receive read requests from the client, directs the read mapper to prepare the data blocks, and provides the data blocks to the client.

Abstract: A system for handling debug log messages in a computerized device under test that has a filesystem and a communications link. A virtual debug folder provides one or more virtual folders wherein the debug log messages are stored as synthesized filenames. The virtual folders are then viewable via the communications link as if actual folders of the filesystem and the synthesized filenames are viewable via the communications link as if actual filenames of the filesystem.

Abstract: A system for a block storage client to work with data blocks in a virtual filesystem (VFS) where the actual data for the data blocks is stored in a real filesystem (RFS). A virtual block mapping table caches references to the actual data in files and directory structures of the RFS. A read mapper then accesses the files and directory structures based on the cached references in the virtual block mapping table, and constructs the data blocks from the files or synthesizes them from the directory structures. And a VFS interface receive read requests from the client, directs the read mapper to prepare the data blocks, and provides the data blocks to the client.

Abstract: Hardware resources sharing for a computer system running software tasks. A controller stores records including a mutex ID tag and a waiter flag in a cache. Lock and unlock registers are readable by the controller and loadable by the tasks with a mutex ID specifying a hardware resource. The controller monitors whether the lock register for loading with a mutex ID, and then determines whether it corresponds with the tag of a record in the cache. If so, it sets the record's waiter flag. If not, it adds a record having a tag corresponding with the mutex ID. The controller also monitors whether the unlock register for loading with a mutex ID, and then determines whether it corresponds with the tag of a record in the cache. If so, it determines whether that record's waiter flag is set and, if so, it clears that record from the cache.

Abstract: Hardware resource sharing for a computerized system running software tasks. A mutex controller is associated with the hardware resource. Lock and unlock indicators are settable by a software task and readable by the controller, and locked and waiters flags are settable and readable by the controller. The controller monitors whether the lock indicator has been set and determines whether the locked flag is set. If not, it sets the locked flag and, if so, it sets the waiters flag and asserts a mutex interrupt signaling the computer system to divert the software task to run a lock request routine. The controller also monitors whether the unlock indicator has been set and then determines whether the waiters flag is set. If not, it clears the locked flag and, if so, it asserts a mutex interrupt signaling the computer system to divert the software task to run an unlock request routine.

Abstract: A magnetic stripe reader having an integrated signature scanner and electronic transaction system employing the same provide for simultaneous reading of magnetically encoded data and scanning of an authorized signature typically located above the magnetic stripe located on credit cards or other data cards, thus allowing a merchant or other operator to quickly and discretely compare a tendered signature with the authorized signature. In this manner, the signature may be verified without the need for physical retention of the card until a visual comparison of the signature can be made with the authorized signature on the card.