Closed Dukat-Gul closed 3 years ago
Ah good point. Lemme fix that real quick
Okay I pushed something to master mind checking if that works?
Thanks. Compile worked perfectly with the adjusted CRC code on the Raspberry Pi Zero (non-W), which is armv6l based. Obviously took a LOT longer - and I had to establish a swap file as I had before on the Rpi3B due to RAM available. But I am more than happy to wait :) as your program is very very helpful. I will now continue my testing with the Waveshare 433Mhz Hat Ebyte E22 400T22S enabled, which was fine on my Rpi3B and I suspect will be fine on the Zero....
I spoke too soon, whilst the compile seemed to work.... I have tried to send files between two units (a Rpi3 - which was working previously perfectly) and the new rpi0. no joy... lights flicker but fails. i re-clones the git repository on the old rpi3 and recompiled there too, incase the CRC code needed to be the same on both sides. no change still lights flicker and no echo for the echo-test or ftp.
interestingly, as a side test - I used tncattach on both after using the echo-test to set the channel on both sides. and I was able to ping and ssh between the units. So they are talking.
Heya. Just trying to compile this cool program for a based armv6l raspberry pi. zero/w
and I've hit a pretty obvious issue.
DId some quick looking and the used of the various __crc32xx seems to be for the higher spec's arms according to this especially for some used.
Any suggestions PLEASE how I might tweak this to compile without error?