Skip to content

04. Firmwares V1.X & V2.X

Jump to bottom Edit New page
Marcelo Arredondo edited this page Jan 31, 2025 · 5 revisions

Warning

⚠️⚠️Before you load any firmware check on your CatSniffer which CC1352 model you have (CC1352P o CC1352R for Catsniffer v1.x and v2.x and CC1352P7 for Catsniffer v3.x) and use the correct firmware .hex file for your chip. IF YOU FLASH THE INCORRECT FIRMWARE TO YOUR BOARD IT MAY GET STUCK AND IT WILL NOT ALLOW YOU TO RE-PROGRAM BY BOOTLOADER. Only v3.x can be erased internally using the RP2040 as a JTAG programmer. For versions 1 and 2 you will need an external programmer to recover the board.⚠️⚠️

Firmware repository

All the firmware source files and binaries are now stored in a specific repository where you can follow better the releases and the board version you need to use in different branches:

SAMD21E17

SerialPassthroughwithboot

This firmware is the most basic one for the SAMD21on the CatSniffer. It has two main functions, a direct pass through of the serial communication and setting the board in bootloader mode. The firmware uses a flag to determine what is being performed on the board.


Mode Flags

It uses a very simple structure to send everything read on one serial to the other.


Serial Passthrough Structure

The sketch looks for a combination of button presses to enter into bootloader mode.


Bootloader Button Sequence

catSniffer_LoRa

Most basic LoRa use case with the board. You can transmit C-string or Arduino string up to 256 characters long

CC1352P2

Important

It is really important to correctly identify the type of CC1352 chip that your board has. Loading the incorrect firmware to your board may get it stuck, and it will not allow you to reprogram it by bootloader. Identifying which type of board you have is really simple, just hold your board up to a well lit space and read the inscription on the chip marked in the photos below. If you are not able to read the chip you can shine a flashlight or camera flash onto the board to be able to read it better. We also recommend using a magnifying glass or taking a close up picture with the camera flash on of the chip. If your board is a v3.x the chip should be a CC1352P7. The real issue is with v1.x and v2.x boards. This version can have either a CC1352P1 or a CC1352R1. If you flash either chip with the incorrect firmware you risk bricking your board, and it will only be possible to recover using an external cJTAG programmer.

Creating your own firmware: Creating your own .hex files

In this section, the user will learn how to create their own .hex files.

There are some prerequisites to make your .hex files compatible with CatSniffer:

When the installation of both software were finished, follow the next steps to build hex file:

  1. Create a new folder inside firmware_TI_PACKET_SNIFFER folder or anywhere you like. Here is an example, this new folder will be our workspace.


Create a Project Folder

  1. Open CCS and choose this new folder for the workspace.


Choose the Project Folde on CCS

  1. When CCS runs, go to Window > Preferences.


Preferences Location

  1. Now go to Code Composer Studio > Products.


Products Location

  1. Select in Discovered products the SimpleLink CC13x2 26x2 SDK and press install. Choose the path where the SDK was installed and click on Apply and Close.


Select the Correct Platform

  1. Now select the option Import Project, in the window choose the option Select search-directory and browse the next path: C:\path\CatSniffer\firmware_TI_PACKET_SNIFFER\sniffer_fw\ide\cc1352p1lp\ccs. Select the option sniffer_fw and click on finish.


Import the Project

  1. When the project finishes importing, do a right click on the project sniffer_fw and go down to properties.


Project Properties

  1. In the Properties window go to Arm Hex Utility and mark the option Enable Arm Hex Utility, click on Apply and Close.


Enable Arm Hex Utility

  1. Now go to ccfg.c file and change the next values to enable the bootloader mode on CC1352:
  • SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE...............0xC5
  • SET_CCFG_BL_CONFIG_BL_LEVEL.........................0x0
  • SET_CCFG_BL_CONFIG_BL_PIN_NUMBER...................0x0F
  • SET_CCFG_BL_CONFIG_BL_ENABLE.......................0xC5


Enable Bootloader Mode

  1. As a way to verify the hex file, it’s recommended to activate the blink of a LED. Catsniffer's CC1352 has a LED at DIO 24, changing DIO 6 to 24 to activate LED 4. When the uploading of the hex file finishes, this LED will start blinking.


Activate LED Blink

  1. To build the project, do a right click on the sniffer_fw and then Build Project. and wait till it finishes.


Build Project

  1. The hex file will appear on the path: C:\path\CatSniffer\firmware_TI_PACKET_SNIFFER\Build Example\sniffer_fw\Debug


Built Project on Project Folder

Now you are ready to create your own hex files and upload them to CatSniffer.

Thank you for reading our Wiki!

Clone this wiki locally