Controller concept

The controller emulates up to 32 AZ® disk devices on a single microSD card. Each emulated disk (pseudo disk) is represented on the card by a file in terms of the FAT32 file system, so there are no questions about placing pseudo disks on a large-capacity storage device - just place the card in the card reader, connect it to the PC, copy files of the required size (and with the required content) to the card, move it to the controller, and that's it! Moreover, after working with the card on the PDP-11/DVK/BK/UKNC, you can remove it from the controller, place it back in the card reader and copy the resulting disk image files to the PC, where you can work with them by any means - for example, connect to the emulator, archive and put them somewhere for storage, send them to a conference, etc. It is also not particularly difficult to copy some material found on the Internet onto a card, move it to the controller and use this material on the PDP-11/DVK/UKNC.

Controller registers

The controller has 4 registers on the QBUS

• 177220 - Command and Status Register (CSR)
• 177222 - Data Register (DR)
• 177224 - Primary Boot Register (BOOT1)
• 177226 - Alternate Boot Register (BOOT2)

The CSR register accepts commands in bits D0-D5 and the interrupt enable bit in bit D6, all write only, always zero is read. In bit D7, the readiness bit is read. One in it means that the previous command has been executed and the controller is ready for exchange. Zero means that the controller is busy executing the previous operation, the other registers are disabled, access to any of them will cause Trap to 4. If the execution of the previous command caused an error, bit D15 is set simultaneously with bit D7.

Writing to registers is done only in words; byte writing is not allowed.

All data exchange is conducted via DR. For commands with a single-word argument, this argument should be sent to DR, and then the command should be sent to CSR. For commands exchanging with the controller buffer, on the contrary, the command should be issued and only after it a data block of a certain length should be received or transmitted.

Interruptions

Most commands are executed almost instantly - within the execution time of one or two CPU commands. But the commands for exchanging with the micro-SD card still take time. You can wait for these operations to complete either by polling the D7 CSR bit, or (for example, if you have a multitasking OS that has somewhere to utilize this time) - set the D6 CSR bit (interrupt enable) and do something else. When the operation is completed, an interrupt will occur and you can continue operations on it.

Namespaces

As already mentioned, the disk device presented to the PDP-11 system is a physical file on some file system. Starting with the V17 firmware, network functionality has appeared, it allows using network drives provided by MAXIOL Landisk® technology. Accordingly, for complete unification and ensuring complete "transparency", all differences are reduced to the mount point, at the moment these are the following spaces:

• 0:/ - local files on the MicroSD card
• R:/ - network files in the file repository
• N:/ - network files in the archive https://mirrors.pdp-11.ru/

Planned network spaces (functionality will be implemented in the following firmware):

• P:/ - personal cloud, available only under one account
• S:/ - cloud that allows you to share your files with other members

Buffers

The controller has several buffers for different purposes, all buffers have word sizes because they are transmitted through a 16-bit register.

• Main buffer - IOBUF [258]
• Non-volatile memory buffer - cmosmem_buffer[256]
• Clock buffer - output timestamp_out_buffer[14]
• Clock buffer - input timestamp_in_buffer [7]
• IP information buffer - ipdata
• Map size buffer - sizecard

Main command block

The command is sent to the CSR, to bits 5-0. It should be sent only as a word, byte writing is not allowed. The command bits are for writing only, always zero is read. The command codes are given in octal.

These commands use the main buffer for their operation (IOBUF [258]).

000: Controller reset

The command code is 000. The command stops all controller operations, if possible. Its completion should be waited for by polling. Example program:

Note on the reset command. In fact, it is instantaneous - if the controller is not busy executing an operation that cannot be interrupted, specifically - SD data exchange. While the SD data exchange is in progress, the controller does not accept any commands and the reset command can be skipped. Therefore, if the controller is busy (bit D7 is zero), the reset command is issued again. This happens quite rarely (for example, double-clicking Ctrl/C when rewriting), usually, during normal operations, the wait for writing or reading is performed in a special place and, upon completion of this operation, not a reset is performed, but completely different actions.

001: Select device

The controller supports up to 32 pseudo disks. The "device selection" command selects one of them for operation. Command code 001. To select a device, you should send the number of the drive you are going to work with to the data register (177222) and then send the code 001 to the CSR. The command is executed instantly, i.e. during the time the CPU sends the "device selection" code. When attempting to select an AZ disk that is not assigned an image file, an error is returned in bit D15 of the CSR register.

Пример программы:

002: Set block number, low bits of block number

The controller provides the machine with QBUS as disks AZ0 - AZ7 file-images of the DSK type on the micro-SD card. The size of these file-images and, accordingly, pseudo-disks, can be any, up to 4G each. Addressing on these pseudo-disks is direct - the block number received via QBUS, after shifting, is used as an offset from the beginning of the corresponding file-image. In fact, this is something like LBA on a PC.

There are PDP-11 operating systems that support such disks - RSX-11, DIAMS, and some others. However, the most common OS - RT-11 - uses a WORD (16 bits) for the block number, and the code 0177777 is used in some places for special purposes and is not suitable as a disk size, so disks with a maximum number of blocks of 0177776, i.e. 65534 blocks (33553408 bytes or 32767 K bytes), can be used for RT-11. Therefore, there are two commands for setting the block number: to set the low-order bits of the block number - code 002 and to set the high-order bits of the block number - code 012. If the block number fits into 16 bits (for RT-11 - always), it is enough to use the command to set the low-order bits of the block number, the high-order bits are cleared. If the number does not fit into 16 digits, then first the lower bits must be output, and then the higher ones. If you try to immediately transmit the higher bits without first transmitting the lower ones, an error is returned. If the transmitted address goes beyond the file-image boundary, an error is also returned, no matter at what stage - either when transmitting the lower 16 bits of the block number, or when transmitting the higher ones.

To perform these actions, you must send the required part of the block number bits to DR and then send the command code to CSR, after which you must check for an error. The commands are instantaneous, i.e. they are executed in one QBUS access cycle.

Example of a program - 16-bit  version block number:

003: Open HFS Table of Contents

Sequence of actions:

• reset the controller
• send the command "Accept data block to buffer" to the CSR and transmit the entire line with the full path text (Full Path) to the required table of contents word by word. The line must end with a zero byte (0x00) and be no longer than 384 bytes (192 words).
• send the "Open table of contents" command code to the CSR
• wait for it to finish (the command is long)
• check for errors

Example utility - AZDIR

Example program:

004: Mount a disk

Sequence of actions:
• Reset the controller
• Send a line to the controller with a record similar to the lines describing the disks in the AZ.INI file
• Issue the "Mount disk" command
• Wait for it to finish (the command is long)
• Check for errors
The selected AZnn drive MUST NOT have a disk mounted. If it is mounted, the old disk should be unmounted before mounting a new one - command 014

Example program:

In this fragment, the 51SYS_DS.DSK image file is mounted on the AZ4 disk, located in the SYSTEM folder, which is located in the DISKS folder, which is located in the root directory of the micro-SD card.

005: Reading block into buffer

The controller has a built-in buffer for 256 words (512 bytes). In fact, this is part of the STM32 microcontroller's RAM, allocated in its program for this buffer. All exchange in the main command block goes through this buffer.

The AZ disk memory is represented as a set of blocks, each 512 bytes in size. Such a block is the only available unit for exchanging data with AZ disks. The blocks are numbered from zero to 65533 for the 16-bit version or up to 8388607 for the 32-bit version - this is when using AZ drives of the maximum permissible capacity. No one prevents you from using drives of a smaller capacity - the actual size of the drive is equal to the size of the file-image mounted on this drive. An error will be registered if you try to access beyond the file-image.

Command 005 - reading a block from MicroSD to the buffer. From the pseudo-disk AZn, previously selected by the command "Select device", the block whose number is transmitted by the command (commands) "Set block number" is started for reading. Long-term command.

In fact, a block from a MicroSD card is read in about 500-800 µs. During this time, the controller goes into a state that during the discussion of the project was called "I think, please do not interfere." Namely, for the entire time of its execution, all device registers are disabled, except for CSR, in which zero is read as long as the controller is busy executing this command. After the block is read, the remaining controller registers are connected to the QBUS, bit D7 (ready) is set in CSR and, if bit D6 (interrupt enable) was set in CSR, an interrupt with vector 0174 is generated.

An example without interruptions is trivial:

006: Write block from buffer to disk

Command code 006. The buffer contents are written to the selected pseudo-disk at the specified disk address (block number). Before writing, checks are performed (1) "was there a write to the buffer?", if not, an error is returned and (2) "is the buffer completely filled?", if not (for the last shortened block of the file), the rest of the buffer is cleared with zeros. Then the block is written to the media. The operation is lengthy, after it is started the controller, as with reading, goes into the "I think, please do not interfere" state. And just as with reading, you must wait for the end of this operation, by the same means as with reading.

Example of a program without interrupts:

007: Get disk size

There are two commands for obtaining the size of a pseudo-disk, i.e. the AZn file-image mounted on the selected pseudo-drive.

If the OS being used (or a program working with disks without an OS) can work with large (more than 32M) disks, you should use the command with the code 017. The sequence of actions: reset the controller (command 000), select the drive (p. 3.2) and send the code 017 to the CSR, and then, without any waiting, read from DR first the lower word, and then the higher word of the size of the selected drive (image file).

If the OS you are using cannot work with disks larger than 32M (RT-11), you should use the 007 command - get the pseudo-disk size with a limit of up to 32M. The steps are similar: reset the controller, select the disk, send the 007 code to the CSR and read one word of the pseudo-disk size from DR. If the size of the image file mounted on the selected pseudo-drive is larger than 65534 blocks, the controller returns the number 65534 instead of this "large" size. We remind you that the number 65535 is used in some places for special purposes and cannot be the disk size.

We also remind you that if the image file is not mounted on this drive, the sequence of actions will not work (command 001 select device) and the program execution will simply not reach this point. Therefore, these commands do not provide for errors.

Example of a program with "small" disks

010: Allow network operation

Command code 010. Having completed the sequence of actions for transferring the next portion of data, and expecting that the next request will not follow immediately, you can "utilize" the processor time of the STM32 microcontroller, which is the basis of AZ - occupy it with servicing the network. In the same RT-11, this can be done before exiting the AZ driver, before the .DRFIN macro command, which completes the execution of the input-output request.

Indeed, the I/O operation is completed, the CPU program in the system will prepare a new portion of data for output, or figure out (based on the previously read data) where it should read something else, or generally think about something of its own. smile.gif In other words, after the I/O request is completed, there is a fairly high probability that there will be a pause in working with the AZ disks. So, the time of this pause can be given to servicing the network. To do this, before executing the .DRFIN macro in RT-11 or its analogue in other OS, you should send code 110 (enable network plus enable interrupts) to the CSR.

In this case, the interrupt will not occur, it is activated only upon completion of "long" operations that transfer the controller to the "Thinking, please do not interfere" state, and the interrupt enable trigger set to "1" also enables network operation if it is activated. When the next input-output operation is started, the actions in paragraph 3.1 (controller reset) will also reset this trigger, after which the network service program, having detected the reset of this trigger, will stop (suspend) its work and return control to the main disk service program AZ. The maximum that can be noticed from the CPU side is a small (10-20 µs) delay in executing the reset command, but this is a very reasonable price for network capabilities.

011: Get AZn drive assignment table

Command code 011. Upon receiving this command, the controller switches from the block buffer to its internal assignment table (32 lines of 140 bytes each)*. Before issuing this command, the controller should be reset. After issuing this command, command 015 (read buffer) should be issued, but in this case it will not be the buffer that is read, but the same table, sequentially, word by word.

* starting with v17, the file name length is no longer 130 bytes, but 386 bytes (the last word is zero, to end the line)

AZSMNT utility example

Example program:

012: Setting the block number, block number high bits

The controller provides the machine with MPI as disks AZ0 - AZ7 file-images of the DSK type on the micro-SD card. The size of these file-images and, accordingly, pseudo-disks, can be any, up to 4G each. Addressing on these pseudo-disks is direct - the block number obtained by QBUS, after shifting, is used as an offset from the beginning of the corresponding file-image. In fact, this is something like LBA on a PC.

There are PDP-11 operating systems that support such disks - RSX-11, DIAMS, and some others. However, the most common OS - RT-11 - uses a WORD (16 bits) for the block number, and the code 0177777 is used in some places for special purposes and is not suitable as a disk size, so disks with a maximum number of blocks of 0177776, i.e. 65534 blocks (33553408 bytes or 32767 K bytes), can be used for RT-11. Therefore, there are two commands for setting the block number: to set the low-order bits of the block number - code 002 and to set the high-order bits of the block number - code 012. If the block number fits into 16 bits (for RT-11 - always), it is enough to use the command to set the low-order bits of the block number, the high-order bits are cleared. If the number does not fit into 16 digits, then first the lower bits must be output, and then the higher ones. If you try to immediately transmit the higher bits without first transmitting the lower ones, an error is returned. If the transmitted address goes beyond the file-image boundary, an error is also returned, no matter at what stage - either when transmitting the lower 16 bits of the block number, or when transmitting the higher ones.

To perform these actions, you should send the required part of the block number bits to DR and then send the command code to CSR, after which you should check for an error. The commands are instantaneous, i.e. they are executed in one cycle of access via MPI.

013: Read HFS TOC entry

Command code 013, the command reads the TOC record into the internal memory area and switches the pointer to it for data transfer via DR. The TOC must be open before this.

The procedure is as follows:
• Reset the controller.
• Issue the command "Read the table of contents entry" to the CSR and wait for it to finish.
• Issue the command "Read from controller memory" to the CSR
• Read 11 words of the table of contents entry from DR

The table of contents entry has the format:

The offsets are specified in octal. The formula in the fName line means that there must first be a name, maximum of eight characters, then a period, then a type, up to three characters, and a terminating zero byte 0x00. If the type is not specified, the period is also not needed.

File attributes in fAttr byte (octal):

001 - Read Only
002 - Hidden
004 - System
020 - Directory
040 - Archive

Example program

014: Unmount disk

Command code 014, to unmount the disk, you should reset the controller, send the AZ drive number to the controller DR, which should be unmounted, and send the 014 code to the controller CSR, then wait for the operation to complete (it takes a long time) and check for an error. An error is issued if the drive has not been mounted.
AZUMNT utility example

015: Start transferring the read block

The command code is 015. Having received this command, the controller is configured to output word by word the contents of the same built-in buffer for 256 words, which will be output sequentially through the DR register. No waiting is required, we simply send a word from DR to sequential memory cells 256 times, and that's it. If less than 256 words are needed (the last shortened block of the file), then the remainder can simply be discarded without reading, resetting the controller at the beginning of the next operation will also reset this remainder.

Example program:

That's it, reading is complete.

To write the opposite way, you first need to transfer the entire data block from the CPU memory to the controller and then issue the command "Write the contents of the buffer to disk"

016: Receive data block into buffer

Command code 016. The command sets the controller to receive a block of data and place it in the buffer. The next 256 write cycles to DR will place the data transferred via the QBUS in the buffer.

Example program:

017: Get ramdisk size, large

There are two commands to get the size of a pseudo-disk, i.e. the AZn file-image mounted on the selected pseudo-drive.

If the OS being used (or a program working with disks without an OS) can work with large (more than 32M) disks, you should use the command with the code 017. The sequence of actions: reset the controller (p. 3.1), select the drive (p. 3.2) and send the code 017 to the CSR, and then, without any waiting, read from DR first the lower word, and then the higher word of the size of the selected drive (image file).

If the OS you are using cannot work with disks larger than 32M (RT-11), you should use the 007 command - get the pseudo-disk size with a limit of up to 32M. The steps are similar: reset the controller, select the disk, send the 007 code to the CSR and read one word of the pseudo-disk size from DR. If the size of the image file mounted on the selected pseudo-drive is larger than 65534 blocks, the controller returns the number 65534 instead of this "large" size. We remind you that the number 65535 is used in some places for special purposes and cannot be the disk size.

We also remind you that if the image file is not mounted on this drive, the sequence of actions will not work (command 001 select device) and the program execution will simply not reach this point. Therefore, these commands do not provide for errors.

Example of a program with large disks

020: Get extended diagnostic code

Command code 020, after resetting the controller, you should issue this command in the CSR and then read two words of extended diagnostics from DR. The command is instant, no waiting is required.

027: Get firmware version AZ STM32

Command code 027, returns 2 words

first word - 06404 = high byte 13. this is the firmware version, low byte 4. this is the hardware version - i.e. AZБК in this case second word - 037 = this is the maximum mountable disk - 31.

030: No operation

The main purpose of this command is to set the interrupt enable bit from the controller. The command transfers the interrupt enable bit, which is in the same word with it, but is not part of it (remember, the command is located in bits D0 - D5, and the interrupt enable bit is D6), to the corresponding trigger of the controller and does not affect the processes in the controller in any other way. Control of this trigger works even in the "Thinking, please do not interfere" state, and this is the main feature of the "no operation" command.

The command has the code 0030. Sending the code 0130 to the CSR will enable interrupts from the controller, sending the code 0030 will disable them. An example is not given due to its triviality.

Command block for working with non-volatile memory

The interface provides any AZ controller with access to 255 words of non-volatile memory, all commands set the ready bit upon completion. This allows you to save user settings in non-volatile memory, for example, this is used in AZBK ??- there are saved settings for more comfortable operation of the controller.

All commands in this block use a non-volatile memory buffer for their operation.

021: Read non-volatile memory block into buffer

Command code 021, this command causes a block of non-volatile memory to be read into the non-volatile memory buffer.

022: Transfer the read block of non-volatile memory from the buffer to the bus

Command code 022, this command ensures that the non-volatile memory buffer is transferred to the DR register for reading.

Example program

obviously, after reading the memory, it is necessary to check the result code in the first word - see the decoding of error codes

Examples of returned data for commands

sequentially issuing the command 021 and then 022 will allow reading 256 words from non-volatile memory
Attention! The first word will be the reading success status

• 0 - ok
• 1 - size does not match saved
• 2 - version error
• 3 - checksum error

023: Receive data from the bus into the buffer for subsequent writing into the buffer

Command code 023, this command allows you to fill the non-volatile memory buffer

024: Write from buffer to non-volatile memory block

Command code 024, this command causes a non-volatile memory block to be written from the non-volatile memory buffer.

Example program

Please note that when recording, the buffer immediately comes with the data, i.e. there is no first word with the statu

Block of commands for working with RTC and NTP

The AZ® controller has 2 sources of date-time, the first is the RTC built into the STM32, the second is the clock in the TCP/IP stack. The RTC clock works autonomously with a 2032 battery installed. The clock in the TCP/IP stack is set based on data from the NTP server.

Buffer format timestamp (readable)

The controller API immediately prepares time in several formats, so that it can be conveniently used on the PDP-11 side

SimpleIN buffer format (when writing)

the format is simplified as much as possible, for work with PDP-11

031: Get time from RTC to timestamp buffer

Command code 031, this command uses RTC clock as a source of filling the timestamp buffer

Example program:

032: Get time from timestamp buffer

Command code 032, this command sends the contents of the timestamp buffer to the bus

It is worth checking the correctness of the received time:

033: Write time-date to SimpleIN buffer

Command code 033, this command receives data from the bus into the SimpleIN buffer

The operation of this command is similar to the operation of commands 023 and 016.

034: Set RTC based on buffer data

Command code 034, this command sets the RTC based on the data in the SimpleIN buffer

This command executes quickly, but to avoid problems, a wait loop is recommended.

035: Stimulate time request from NTP server, set based on response

Command code 035, this command sends a request to the NTP server (set in the AZ.INI file or received from DHCP) and sets the clock in the TCP/IP stack.

Example program: sending a request to set the time from an NTP server

The command execution takes 1-2 seconds on average. This command requires the TCP/IP stack to work, so waiting cycles are needed when the stack is enabled.

An example of a polling cycle to get time from the network

Here we explicitly send a request to the NTP server, then turn on the network and wait for the result, periodically polling and checking the correctness of the result.

036: Setting RTC based on TCP/IP stack clock

Command code 036, this command sets the RTC based on the clock in the TCP/IP stack. You must first set the clock in TCP/IP - command 036.

Example program:

042: Get time from TCP/IP stack clock into timestamp buffer

Command code 042, this command uses the TCP/IP stack clock as a source for filling the timestamp buffer.

Example program:

All commands set the ready bit upon completion.

AZБК® specific commands

These commands are intended for operation of the AZБК® controller, developed for the BK series of computers - BK-0010/BK-0010.01/BK-0011M.

Other AZ® controllers ignore these commands.

037: Restart of the AZБК® controller and the entire computer

Command code 037, this command restarts the AZ® microcontroller, which also causes a restart of the BK-0010/BK-0010.01/BK-0011M itself

Example program

044: Saving a screenshot to a file

Command code 044, this command is designed to take a memory image of the specified size (or determined automatically based on saved parameters) technically, the command can serve as a debugging tool because it is capable of taking a memory image the general limitation on taking a memory image is 2MB per image

service memory page 76(8) is used as parameters

Structure of filling information about a screenshot

Example code for filling a memory page

There are three options for specifying memory areas.

1. specify the address and length 24-bit - see format, if they are not there - the system looks further
2. specify the page number and page quantity, if they are not there
3. the system looks further - that is, it makes a screenshot based on the data about registers 177230, etc.

The screenshot is saved in the format
- page 76 - its first kilobyte
- the memory image itself (if the mode is layered - then all three layers)

Before calling the command, you can load the file name for saving the screenshot [in the cmosmem buffer], but if it is missing (there will be no name in the buffer - a line ending with 0), the system will generate its own name based on the following rule: default path for saving screenshots
0:/SCREENS/
name format - DDHHMISS.SCR
where DD is two digits of the day of the month, HH is the hour, MI is the minute, SS is the second

If an error occurs during the command execution, the name will be "ERROR *"
for example
"ERROR f_open 6"

Example program

To unpack a screenshot, you can use this utility - https://master.pdp-11.ru/screen_unpack/

Commands for working with the TCP/IP stack

The following commands operate on the TCP/IP stack information buffer.

040: Get IP address and other TCP/IP stack settings to buffer

Command code 040, this command fills the buffer with information from the TCP/IP stack with current (actual) information.

041: Reading ip address buffer

Command code 041, this command transfers the buffer to the bus

This pair of commands allows you to get current information from the stack

• IP address
• MASK mask
• GW gateway
• NTP address of the NTP server
• DNS1 primary DNS address
• DNS2 backup DNS address

accordingly it is 12 words

Example program:

Example return data:

043: Read MAC address into ip buffer

Command code 043, this command reads the current actual MAC address into the IP address buffer i.e. first 043 and then 041 commands

Example program:

Commands for working with a MicroSD card at the file level

These commands are designed to work with a MicroSD card at the file system level and allow you to read/write files without mounting files as disk images.

These commands use a 256-word buffer that is used in the interface for working with non-volatile memory (see commands 022 023 above)

Limitations - the length of the full path to the file is 256 bytes

050: Set the name of the file we will read

Command code 050, this command sets the name of the file that we will read, while opening the file for reading, and also obtaining its properties.

051: Get file size for reading (or its status) on BUS

Command code 051, this command transmits the file size or reading error to the MPI. The file size is 31 bits, the most significant bit is an error indicator. Accordingly, the maximum file size that can be worked with via this interface is limited to 2 ^ 31 bytes (2GB).

The error generation looks like this:
sizeanyfile=1<<31 + FFres; // if the most significant bit of a 32-bit word is set, then the error code is in the lower part

FFres = FatFS error

http://elm-chan.org/fsw/ff/doc/open.html

052: Read a block of a set file into a buffer

Command code 052, this command reads a file into a non-volatile memory buffer.

As a result, the file reading scheme looks like this
023 - fill the file name into the buffer
050 - set the file for reading
051 - read the file length or file open error
if there is an error - repeat 023 050 051 from the beginning
if everything is ok - start reading the file
052 - read the file block into the buffer
022 - take data from the buffer
repeat the 052 022 pairs the required number of times in order to read the entire file
once the file is read - the last 052 command will close it automatically.

Example program:

053: set the name of the file that we will write

Command code 053, this command opens a file for writing, receives opening parameters (or errors).

054: Set file length

Command code 054, this command sets the expected file length, this is necessary for the correct formation of the file at the file level of the MicroSD card, as well as for organizing data transfer.

055: write data from buffer to file

Command code 055, this command writes data from the non-volatile memory buffer to an open file for writing. The last command 055 will automatically close the file when the declared file length is reached.

The command flow chart for writing is as follows
023 - fill the file name into the buffer
053 - set the file for reading
051 - file opening/creation status
if an error - repeat from the beginning 023 053 051
if everything is ok - move on
054 - set the file length, i.e. we must immediately declare what the file length will be
023 - fill the data block into the buffer
055 - write from the buffer to the file
repeat the 023 055 pairs the required number of times in order to write the entire file
once the file is written - the last 055 command will close it automatically

Example program:

the example is completely in the form of the RT11 utility and is posted here

056: Get data on the size of the map into the sizecard buffer

Command code 056, this command reads the parameters of the MicroSD card into the sizecard buffer

057: Reading sizecard buffer

Command code 057, this command returns the sizecard buffer (2 words)

sizecard buffer contains 2 words 16bit
first word - total card size available for FAT in MB
second word - free card size in MB

Example program:

Example data
035521 - total megabytes on the card - 15185.
035417 - free megabytes - 15119.

Hall of Fame API Command Block

This block of commands is intended for interaction with the server Hall of Fame

025: Инициализация Hall of Fame (HOF)

Command code 025, this command establishes a connection to the Hall of Fame server, initializes the encrypted tunnel and prepares the API for work.

Example program:

026: Exchange with Hall of Fame (HOF)

Command code 026, this command makes a direct exchange with Hall of Fame

Example program: