Building From Source #20
Comments
|
What's your version of ARM gcc ? I have 6.2.1 20161205. |
|
Can confirm that it builds fine with the latest arm-gcc build (6 2016q4) |
|
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? |
|
So your saying if I do: git clone https://github.com/furrtek/portapack-havoc.git it should just work |
|
You'll need to copy over the toolchain from portapack-hackrf repo, as well as any other files the build says are missing. |
|
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. |
|
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 |
|
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. |
|
My end goal to to have portapack-h1-havoc.bin |
|
Ubuntu 16.04 |
|
Built the portpack-hackrf firmware with 1 warning and have the bin to flash trying something with portapack-havoc |
|
following the same steps I used on hackrf I got stuck at 97%, still working on it |
|
stuck on this error at 97%, not sure what I am missing [ 97%] Generating baseband.img I cloned the havoc repo and get tons of warnings and it ends with the above error, but portapack-hackrf builds with no issues |
|
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] /home/portapack-havoc/firmware/application/ui_closecall.cpp:284:1: warning: 'ui::CloseCallView::f_max' should be initialized in the member initialization list [-Weffc++] |
|
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? |
|
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. |
|
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? |
|
Those files will be in portapack-hackrf/firmware/baseband/ after you've built the portapack-hackrf firmware successfully. |
|
Do you get a ton of warnings when building havoc vs hackrf that only gives me 2-3? |
|
Warnings aren't important, they're just because of -Weffc++ and variables not clearly initialized.
|
|
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 --Goes through and just shows all the warnings Scanning dependencies of target baseband |
|
@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. |
|
Doing hackrf.img and terminator.img should be generated from baseband/CMakeLists.txt lines 404 and 416. Can't see why it wouldn't. |
|
I will try adding make clean and see what happens, it did not mention
having to use make clean at any point of the hackrf build guide
…On Wed, Feb 8, 2017 at 4:40 AM, Furrtek ***@***.***> wrote:
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.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABpPNzD2hysSWJEAcUAdMtQxcAwU2Qj7ks5raanIgaJpZM4L3w7T>
.
|
|
You shouldn't have to, but diverting from instructions is helpful sometimes. |
|
Missing .cmake file added, and dependencies for baseband.img changed. |
|
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 |
* Update analog_audio_app.cpp (furrtek#353) * Adding phase field (extracted from @jamesshao8 repo)
Getting many errors when using git clone and trying to build from source, worked through most of the errors and now stuck with this output
[ 0%] Building CXX object firmware/application/CMakeFiles/application.elf.dir/rf_path.cpp.obj
/home//portapack-havoc/firmware/application/rf_path.cpp: In constructor 'constexpr rf::path::{anonymous}::Config::Config(rf::Direction, rf::path::Band, bool)':
/home//portapack-havoc/firmware/application/rf_path.cpp:99:2: sorry, unimplemented: use of the value of the object being constructed in a constant expression
}
^
/home//portapack-havoc/firmware/application/rf_path.cpp: At global scope:
/home//portapack-havoc/firmware/application/rf_path.cpp:169:49: in constexpr expansion of 'rf::path::{anonymous}::config_band()'
/home//portapack-havoc/firmware/application/rf_path.cpp:163:25: in constexpr expansion of 'rf::path::{anonymous}::config_rx_tx((rf::path::Band)0)'
/home//portapack-havoc/firmware/application/rf_path.cpp:156:38: in constexpr expansion of 'rf::path::{anonymous}::config_amp((rf::Direction)0, ((rf::path::Band)band))'
/home//portapack-havoc/firmware/application/rf_path.cpp:169:49: error: 'constexpr rf::path::{anonymous}::Config::Config(rf::Direction, rf::path::Band, bool)' called in a constant expression
constexpr ConfigBand config_table = config_band();
^
/home//portapack-havoc/firmware/application/rf_path.cpp:169:49: error: 'constexpr rf::path::{anonymous}::Config::Config(rf::Direction, rf::path::Band, bool)' called in a constant expression
firmware/application/CMakeFiles/application.elf.dir/build.make:2211: recipe for target 'firmware/application/CMakeFiles/application.elf.dir/rf_path.cpp.obj' failed
make[2]: *** [firmware/application/CMakeFiles/application.elf.dir/rf_path.cpp.obj] Error 1
CMakeFiles/Makefile2:247: recipe for target 'firmware/application/CMakeFiles/application.elf.dir/all' failed
make[1]: *** [firmware/application/CMakeFiles/application.elf.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
Please advise on what is needed to compile from source, I have all the needed depends and compilers and toolchains
The text was updated successfully, but these errors were encountered: