Receiving executable instructions from volatile memory
The present disclosure includes apparatuses, methods, and systems for receiving executable instructions from volatile memory. In an example, a method can include storing executable instructions comprising a bootloader at a pre-defined memory address range in a non-volatile memory device of a solid state drive (SSD), copying the executable instructions from the pre-defined memory address range to a volatile memory device of the SSD in response to powering on the SSD, and transmitting the executable instructions from the volatile memory device to a host.
1 . A method, comprising:
storing executable instructions comprising a bootloader at a pre-defined memory address range in a non-volatile memory device of a solid state drive (SSD) of an autonomous or partially autonomous vehicle;
copying the executable instructions from the pre-defined memory address range to a volatile memory device of the SSD in response to a proximity of a fob of the autonomous or partially autonomous vehicle being detected; and
transmitting the executable instructions from the volatile memory device to a host.
2 . The method of claim 1 , wherein the method includes receiving the pre-defined memory address range in the non-volatile memory device from a user.
3 . The method of claim 1 , wherein the pre-defined memory address range is fixed across power cycles.
4 . The method of claim 1 , wherein the method includes mapping the pre-defined address to the volatile memory device.
5 . The method of claim 1 , wherein the method includes transmitting the executable instructions to the host in response to receiving a boot load command from the host.
6 . The method of claim 1 , wherein the method further includes:
storing second executable instructions comprising a system image at the pre-defined memory address range in the non-volatile memory device;
copying the second executable instructions to the volatile memory device in response to transmitting the executable instructions comprising the bootloader to the host; and
transmitting the second executable instructions from the volatile memory device to the host.
7 . A solid state drive (SSD) of an autonomous or partially autonomous vehicle, comprising:
a volatile memory device;
a non-volatile memory device; and
a controller coupled to the volatile memory device and the non-volatile memory device, the controller including circuitry configured to:
receive a pre-defined memory address range from a user;
store executable instructions at the pre-defined memory address range in the non-volatile memory device;
in response to a proximity of a fob of the autonomous or partially autonomous vehicle being detected, copy the executable instructions from the pre-defined memory address range to the volatile memory device; and
transmit the executable instructions from the volatile memory device to a host.
8 . The SSD of claim 7 , wherein the executable instructions include a number of bootloaders.
9 . The SSD of claim 7 , wherein the executable instructions include an operating system, utilities, diagnostics, and boot and data recovery information.
10 . A solid state drive (SSD) of an autonomous or partially autonomous vehicle, comprising:
a volatile memory device;
a non-volatile memory device comprising a first memory address range including executable instructions; and
a controller coupled to the volatile memory device and the non-volatile memory device, the controller including circuitry configured to:
map the executable instructions from the first memory address range in the non-volatile memory device to a second memory address range in the volatile memory device in response to a proximity of a fob of the autonomous or partially autonomous vehicle being detected; and
transmit the executable instructions from the second memory address range in the volatile memory device.
11 . The SSD of claim 10 , wherein the first memory address range includes a first bootloader, a second bootloader, and a third bootloader.
12 . The SSD of claim 10 , wherein the non-volatile memory device further comprises operating system data at the first memory address range; and
wherein the controller is further configured to transmit the operating system data.
13 . The SSD of claim 12 , wherein the controller is further configured to transmit the operating system data after transmitting a first bootloader, a second bootloader, and a third bootloader sequentially.
14 . The SSD of claim 12 , further comprising a host interface coupled to the controller;
wherein the controller is configured to transmit the first bootloader, second bootloader, and third bootloader sequentially via the host interface.
15 . An autonomous or partially autonomous vehicle, comprising:
a host; and
a memory device including:
a volatile memory device;
a non-volatile memory device; and
a controller including circuitry configured to:
store executable instructions at a pre-defined memory address range in the non-volatile memory device;
in response to a proximity of a fob of the autonomous or partially autonomous vehicle being detected, copy the executable instructions from the pre-defined memory address range in the non-volatile memory device to the volatile memory device; and
transmit the executable instructions from the volatile memory device to a host;
wherein the host is configured to execute the executable instructions.
16 . The autonomous or partially autonomous vehicle of claim 15 , wherein the non-volatile memory device is a NAND device.
17 . The autonomous or partially autonomous vehicle of claim 15 , wherein the volatile memory device is a dynamic access memory (DRAM) device.
18 . The autonomous or partially autonomous vehicle of claim 15 , wherein the memory device is a solid state drive (SSD).
19 . The autonomous or partially autonomous vehicle of claim 15 , wherein the host is configured to execute the executable instructions by:
loading a second bootloader image;
loading a third bootloader image; and
loading an operating system image.
20 . The autonomous or partially autonomous vehicle of claim 19 , wherein the host is further configured to execute the executable instructions by:
loading a partition table;
mounting a file system; and
running a background service.