Skip to content

file "slot" in FILE_OPEN, FILE_READ inconsistencies in firmware and emulation #2

Description

@bspruck

The slot cannot be set for files. There is no FILE_SLOT command. For files slot is always -1:

packet_t *packet = getPacket(comInCMD, slot);

Unluckily, FILE_OPEN used the file ID as slot number when pushing the packet, thus this value cannot be read

pushPacket(HUB_FILE_OPEN, comInBuffer[0]);

Two solutions:

In the handy emulation code this is broken as well. But here both functions use a slot number.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions