FreeCalypso > hg > fc-magnetite
view src/cs/system/bootloader/inc/protocol.h @ 632:d968a3216ba0
new tangomdm build target
TCS211/Magnetite built for target leonardo runs just fine on the Tango-based
Caramel board, but a more proper tangomdm build target is preferable in order
to better market these Tango modems to prospective commercial customers. The
only differences are in GPIO and MCSI config:
* MCSI is enabled in the tangomdm build config.
* GPIO 1 is loudspeaker amplifier control on Leonardo, but on Tango platforms
it can be used for anything. On Caramel boards this GPIO should be
configured as an output driving high.
* GPIO 2 needs to be configured as Calypso input on Leonardo, but on Tango
platforms it can be used for anything. On Caramel boards this GPIO should be
configured as an output, either high or low is OK.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Sat, 04 Jan 2020 19:27:41 +0000 |
parents | 945cf7f506b2 |
children |
line wrap: on
line source
/****************************************************************************** * FLUID (Flash Loader Utility Independent of Device) * * (C) Delta Technologies 2001. * Cleanup, modifications and extensions by Mads Meisner-Jensen, mmj@ti.com. * * Target/PC protocol definition * * $Id: protocol.h 1.9 Wed, 31 Oct 2001 11:47:00 +0100 mmj $ * ******************************************************************************/ enum ProtocolChars { PROTO_HELLO = 'H', PROTO_BAUDRATE = 'B', PROTO_HARDWARE = 'H', PROTO_QUERY = 'Q', PROTO_QUERY_CHIP = 'C', PROTO_READY = 'R', PROTO_ISEMPTY = 'I', PROTO_DOWNLOAD = 'L', PROTO_DETECT = 'D', PROTO_ERASE = 'E', PROTO_COMPRESS = 'Z', PROTO_PROGRAM = 'P', PROTO_CKSUM = 'C', PROTO_READ = 'R', PROTO_RESET = '0', PROTO_ERROR_CKSUM = 'X', PROTO_ERROR_MEMORY = 'M', PROTO_ERROR_FLASH_TIMEOUT = 'T', PROTO_ERROR_FLASH_COMMAND = 'C', PROTO_ERROR_FLASH_VPP = 'P', PROTO_ERROR_FLASH_LOCKED = 'L', PROTO_ERROR_VERIFY = 'V', PROTO_CHECKSUM = 'C', PROTO_VERSION = 'V', PROTO_ERROR = '?', PROTO_TRACE = '$' }; // Not really part of the protocol but as this header file is included by // both PC side and target side source code, this is an easy place to put // these difinitions. enum ChipIdCodes { // Ulysses and Hercules CHIP_ID_ULYSSES_0 = 0xB2B5, CHIP_ID_ULYSSES_A = 0xB335, CHIP_ID_HERCULES_A = 0xB334, // Correct revision designation? CHIP_ID_HERCULES_B = 0xB32C, // Correct revision designation? // Samson and Calypso CHIP_ID_CALYPSO_A = 0xB2AC, CHIP_ID_CALYPSO_B = 0xB396 };