Building From Source about portapack-havoc HOT 28 CLOSED

What's your version of ARM gcc ? I have 6.2.1 20161205.

from portapack-havoc.

Can confirm that it builds fine with the latest arm-gcc build (6 2016q4)

from portapack-havoc.

So let me start from fresh, I git clone, moved over the needed lib and toolchain from hackrf, cd to fw and then run make. Maybe starting from git clone will help me see where is fails.

**I built the lib from source and moved the files to the lib folder under common

So lets start when I git clone, what next?

from portapack-havoc.

See https://github.com/sharebrained/portapack-hackrf/wiki/Building%20Firmware

from portapack-havoc.

So your saying if I do:

git clone https://github.com/furrtek/portapack-havoc.git
cd portapack-havoc
mkdir build
cd build
cmake ..
make firmware

it should just work

from portapack-havoc.

You'll need to copy over the toolchain from portapack-hackrf repo, as well as any other files the build says are missing.

from portapack-havoc.

Already have and know that part already from when I was working through errors when I first tried compiling, just confirming the steps listed in the hackrf guide.

from portapack-havoc.

The error above is where it builds at 17% and then fails with the error above, if I try again it just gives the above error.

I will have access to that computer in an hour

from portapack-havoc.

Deleted all, started fresh, after some tinkering it builds but do you all get a ton of warnings during the build process? Also after building I don't see the bin for flashing.

from portapack-havoc.

My end goal to to have portapack-h1-havoc.bin

from portapack-havoc.

Ubuntu 16.04
gcc-arm-embedded_6-2016q4
cmake version 3.5.1
toolchain from hackrf in havoc fw folder
lib folder in fw folder with source compiled files inside
cd build
cmake ..
make firmware

from portapack-havoc.

Built the portpack-hackrf firmware with 1 warning and have the bin to flash

trying something with portapack-havoc

from portapack-havoc.

following the same steps I used on hackrf I got stuck at 97%, still working on it

from portapack-havoc.

stuck on this error at 97%, not sure what I am missing

[ 97%] Generating baseband.img
cat: hackrf.img: No such file or directory
cat: terminator.img: No such file or directory
firmware/baseband/CMakeFiles/baseband.dir/build.make:78: recipe for target 'firmware/baseband/baseband.img' failed
make[3]: *** [firmware/baseband/baseband.img] Error 1
make[3]: *** Deleting file 'firmware/baseband/baseband.img'
CMakeFiles/Makefile2:353: recipe for target 'firmware/baseband/CMakeFiles/baseband.dir/all' failed
make[2]: *** [firmware/baseband/CMakeFiles/baseband.dir/all] Error 2
CMakeFiles/Makefile2:103: recipe for target 'firmware/CMakeFiles/firmware.dir/rule' failed
make[1]: *** [firmware/CMakeFiles/firmware.dir/rule] Error 2
Makefile:118: recipe for target 'firmware' failed
make: *** [firmware] Error 2

I cloned the havoc repo
made build folder
copied toolchain from hackrf fw folder to havoc fw folder
cd build
ran cmake ..
make firmware

and get tons of warnings and it ends with the above error, but portapack-hackrf builds with no issues

from portapack-havoc.

Example of one of the many warnings I get using the working steps on building hackrf on havoc:

/home/portapack-havoc/firmware/common/bch_code.cpp:349:17: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (i = 0; i < (m + 1); i++) {
~~^~~~~~~~~
[ 30%] Building CXX object firmware/application/CMakeFiles/application.elf.dir/bht.cpp.obj
/home/portapack-havoc/firmware/application/bht.cpp: In function 'std::__cxx11::string gen_message_ep(uint8_t, size_t, uint32_t, uint32_t)':
/home/portapack-havoc/firmware/application/bht.cpp:31:103: warning: unused parameter 'relay_state_B' [-Wunused-parameter]
std::string gen_message_ep(uint8_t city_code, size_t family_code_ep, uint32_t relay_state_A, uint32_t relay_state_B) {

/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::f_max' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::slice_trim' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::slice_start' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::slice_frequency' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::slices_max' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::slices_counter' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::last_channel' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::scan_span' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::resolved_frequency' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::locked_imax' should be initialized in the member initialization list [-Weffc++]
/home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::scan_counter' should be initialized in the member initialization list [-Weffc++]

from portapack-havoc.

Narrowed it down to something in the FW folder, I moved over the toolchain from the hackrf repo, is this correct? Am I missing anything?

from portapack-havoc.

That's how I do it. Not sure if that's the "official" way, but I build the portapack-hackrf firmware, then copy over the toolchain, hackrf.img, and terminator.img over to their respective locations in the portapack-havoc directories. Proceed to build firmware as usual. You're not really going to build anything different than the portapack-h1-havoc.bin that comes in the firmware dir, however; I usually just flash this file directly to the HackRF.

from portapack-havoc.

The point to me struggling to build by source is so I can tinker and learn from the code, otherwise I would just keep downloading the bin, thanks for the info, I think thats what I was missing and did not know I needed to do that since its not listed anywhere, i will give it a try now, where did you find the hackrf.img terminator.img?

from portapack-havoc.

Those files will be in portapack-hackrf/firmware/baseband/ after you've built the portapack-hackrf firmware successfully.

from portapack-havoc.

Do you get a ton of warnings when building havoc vs hackrf that only gives me 2-3?

from portapack-havoc.

Warnings aren't important, they're just because of -Weffc++ and variables not clearly initialized.
I have to add a bunch of { } and { 0 } to shut them up.

sudo make firmware should generate the .img and the final portapack-h1-havoc.bin after a bunch of warnings, without doing anything special.

from portapack-havoc.

not for me, just wiped and started fresh again and used sudo make firmware and get the same error as before

$ git clone havoc repo
$ cd portapack-havoc/
~/portapack-havoc/$ mkdir build
~/portapack-havoc/$ cd build
~/portapack-havoc/build$ cmake ..
~/portapack-havoc/build$ sudo make firmware
Scanning dependencies of target bootstrap.elf
[ 0%] Building C object firmware/bootstrap/CMakeFiles/bootstrap.elf.dir/bootstrap.c.obj
[ 0%] Building ASM object firmware/bootstrap/CMakeFiles/bootstrap.elf.dir/startup_ARMCM4.S.obj
[ 0%] Linking C executable bootstrap.elf
[ 0%] Built target bootstrap.elf
Scanning dependencies of target bootstrap
[ 1%] Generating bootstrap.bin
[ 1%] Built target bootstrap
[ 1%] Generating hackrf_cpld_data.hpp, hackrf_cpld_data.cpp
[ 1%] Generating portapack_cpld_data.cpp
Scanning dependencies of target application.elf

--Goes through and just shows all the warnings

Scanning dependencies of target baseband
[ 92%] Generating baseband_ais.bin, baseband_ais.img
[ 93%] Generating baseband_am_audio.bin, baseband_am_audio.img
[ 93%] Generating baseband_capture.bin, baseband_capture.img
[ 93%] Generating baseband_ert.bin, baseband_ert.img
[ 94%] Generating baseband_fsktx.bin, baseband_fsktx.img
[ 94%] Generating baseband_pocsag.bin, baseband_pocsag.img
[ 94%] Generating baseband_nfm_audio.bin, baseband_nfm_audio.img
[ 94%] Generating baseband_tpms.bin, baseband_tpms.img
[ 95%] Generating baseband_wfm_audio.bin, baseband_wfm_audio.img
[ 95%] Generating baseband_wideband_spectrum.bin, baseband_wideband_spectrum.img
[ 95%] Generating baseband_ook.bin, baseband_ook.img
[ 95%] Generating baseband_jammer.bin, baseband_jammer.img
[ 96%] Generating baseband_audio_tx.bin, baseband_audio_tx.img
[ 96%] Generating baseband_afsk.bin, baseband_afsk.img
[ 96%] Generating baseband_replay.bin, baseband_replay.img
[ 97%] Generating baseband_tones.bin, baseband_tones.img
[ 97%] Generating baseband_rds.bin, baseband_rds.img
[ 97%] Generating baseband_ads.bin, baseband_ads.img
[ 97%] Generating baseband.img
cat: hackrf.img: No such file or directory
cat: terminator.img: No such file or directory
firmware/baseband/CMakeFiles/baseband.dir/build.make:79: recipe for target 'firmware/baseband/baseband.img' failed
make[3]: *** [firmware/baseband/baseband.img] Error 1
make[3]: *** Deleting file 'firmware/baseband/baseband.img'
CMakeFiles/Makefile2:356: recipe for target 'firmware/baseband/CMakeFiles/baseband.dir/all' failed
make[2]: *** [firmware/baseband/CMakeFiles/baseband.dir/all] Error 2
CMakeFiles/Makefile2:103: recipe for target 'firmware/CMakeFiles/firmware.dir/rule' failed
make[1]: *** [firmware/CMakeFiles/firmware.dir/rule] Error 2
Makefile:118: recipe for target 'firmware' failed
make: *** [firmware] Error 2

from portapack-havoc.

@ablanquart, thank you for your help with building this repo, appreciate it very much, thanks to you I am good to go with your steps and made a little shell script to automate the steps for me. Thanks!

@furrtek, if sudo make firmware did work I would wonder why with the hackrf repo, since you pulled the initial code from their why sudo would have to be used since hackrf does not, but sudo make firmware as shown above does not work

I am all set for building and can just pull new changes and build now that everything is setup, ill let you get to this issue when you can, I would guess there is only a handful of us building from source and all others are downloading the FW from github.com like I was.

from portapack-havoc.

Doing make clean and sudo make firmware I have:
[ 93%] Generating terminator.img [ 93%] Generating baseband_ais.bin, baseband_ais.img [ 94%] Generating baseband_am_audio.bin, baseband_am_audio.img [ 94%] Generating baseband_capture.bin, baseband_capture.img [ 94%] Generating baseband_ert.bin, baseband_ert.img [ 95%] Generating baseband_fsktx.bin, baseband_fsktx.img [ 95%] Generating baseband_pocsag.bin, baseband_pocsag.img [ 95%] Generating baseband_nfm_audio.bin, baseband_nfm_audio.img [ 95%] Generating baseband_tpms.bin, baseband_tpms.img [ 96%] Generating baseband_wfm_audio.bin, baseband_wfm_audio.img [ 96%] Generating baseband_wideband_spectrum.bin, baseband_wideband_spectrum.img [ 96%] Generating baseband_ook.bin, baseband_ook.img [ 96%] Generating baseband_jammer.bin, baseband_jammer.img [ 97%] Generating baseband_audio_tx.bin, baseband_audio_tx.img [ 97%] Generating baseband_afsk.bin, baseband_afsk.img [ 97%] Generating baseband_replay.bin, baseband_replay.img [ 98%] Generating baseband_tones.bin, baseband_tones.img [ 98%] Generating baseband_rds.bin, baseband_rds.img [ 98%] Generating baseband_ads.bin, baseband_ads.img [ 98%] Generating hackrf.bin, hackrf.img [ 98%] Generating baseband.img

hackrf.img and terminator.img should be generated from baseband/CMakeLists.txt lines 404 and 416. Can't see why it wouldn't.

from portapack-havoc.

from portapack-havoc.

You shouldn't have to, but diverting from instructions is helpful sometimes.

from portapack-havoc.

Missing .cmake file added, and dependencies for baseband.img changed.
I cleared everything and cloned again, build still gave a lot of warnings but finished without errors.

from portapack-havoc.

Sorry, went on a week vacation with no connectivity

deleted repo and started fresh

everything works with no workarounds, most errors in the 70ish% range, some in the first 20%

closing now that everything works

from portapack-havoc.