Code base (only two files were added on the base of HACKRF original code base, one file was changed):
Https://github.com/JiaoXianjun/hackrf-UART-1602LCD
The goal is primarily to help people who want to change the debug HACKRF firmware. Because there is no debugging means to change the firmware basic two eyes a dark, groping in the darkness is difficult. The previous days to collect the aircraft firmware has been in the dark good grasp debugging means, shared to the needs of the people.
is to HACKRF board added 1602 LCD screen and UART, and then can happily in their own firmware code output to the LCD screen or printf to the computer's serial terminal.
1 hardware connection (without hackrf any changes, using the existing IO that it leaves)
1602LCD HACKRF PIN Connection
-------------------- 1602LCD pin6hackrf P20 9 -- 1602LCD pin5hackrf P20 7 -- 1602LCD PIN4HACKRF -- 1602LCD pin2 pin15hackrf --1602LCD pin1 pin3 Pin16
UART HACKRF PIN Connection
1 gnd --GND of computer or usb-4 UART0 RXD --TXD of computer or usb-5 UART0 TXD --RXD of computer or Usb-uart dongle
Where Hackrf's P20 and P25 are defined, everyone goes to see its hackrf-one-assembly.pdf and hackrf-one-schematic.pdf (HACKRF code base doc/hardware directory). About the pin pin definition of the 1602LCD module, as well as the pin PIN definition of the USB serial port It's a bad street.
2 software Demo
I gave the HACKRF firmware code loop on the LCD display two lines, but also to the computer minicom print serial output. Baud rate 921600.
Core source Files Hackrf_uart_1602lcd.c
The entire compiled code base is put here: Https://github.com/JiaoXianjun/hackrf-UART-1602LCD
Directory firmware/hackrf_uart_1602lcd/build/a compiled DFU firmware, if you do not want to compile, you can directly in the DFU mode to try to quickly verify that your hardware connection is correct:
0 --download Hackrf_uart_1602lcd.dfu (before DFUset your board into DFU mode)
3 Some pits about firmware compilation
The basic firmware compilation method can refer to the README. Note that the libopencm3 is compiled according to the Readme and then:
CD firmware/-drun_from=rammake
Keng:
1. Not any dfu-util can be used, I tested N, this can be used
git://gitorious.org/dfu-util/dfu-util.git
I also put a copy here: https://github.com/sdr-x/sdr-x.github.io/blob/master/_resource/dfu-util.tar.gz
2.hackrf-common.cmake needs to change.
COMMAND dfu-suffix--vid=0x1fc9--pid=0x000c--did=0x0-s 0-a _tmp.dfu "-s 0" removed. Add one more line later:
COMMAND dfu-prefix-s 0-a _tmp.dfu
It's like this: Hackrf-common.cmake
3.Ubuntu comes with the Gcc-arm-none-eabi compiler is not available! To use this:
https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded
!!! If you is using Ubuntu 14.04 and later, please be careful because there is packages with same name but produced by Debia N and inherited by Ubuntu. Simply follow the above 3 steps, you could end up with Gcc-arm-none-eabi from Ubuntu. So-to-install Gcc-arm-none-eabi from arm, steps is:
1). sudo apt-get remove Binutils-arm-none-eabi gcc-arm-none-eabi2). sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded3). sudo apt-get update4). sudo apt-get install gcc-arm-none-eabi=4.9. 3. 2015q1-0trusty13 or sudo apt-get install gcc-arm-none-eabi=4.9 . 3. 2015q1-0utopic14
If you do not find a command error, you might want to do the following:
cd/usr/lib/arm-none--s/usr/arm-none-eabi/bin Bin
Add 1602LCD and UART to HACKRF (with firmware compilation method)