[David Mozombite]

Hi Leo,

Thanks for noting this. This change has been made.

Thanks!

David

[David Mozombite]

Hi Leo,

Thanks for the heads-up. No it should not take you to a login page. I have updated the link to direct you to the correct page.

https://a.co/d/fpqvwib

Above is the link it was supposed to direct you to.

Thanks,

David

[David Mozombite]

Hi Joel,

I wanted follow up, I didn’t receive the workspace yet and I’m wondering if you had emailed it to the correct email. As for version 3.7 vs 3.8, I’d like to test your workspace before diving to deeply into that.

Thanks and let me know,

David

[David Mozombite]

Hi Sean,

I apologize for the delay in responding – if you are still having this problem I recommend that you try two things:

1. Use sudo raspi-config, enter Interfacing Options, and enable the the I2C port. In the same menu activate the Serial monitor, Disable the Login Shell to be accessible over serial and enable serial. Reboot and check if you can see the correct interface.
2. If that does not work, I recommend that you jump to the install minicom step in the following section, and use the following commands:
   1. ATE1
   2. AT+QCFG=”usbnet”

Let me know the results. Thank you for your patience,

David

[David Mozombite]

Hi Joel,

After the first six characters it will respond with the SEND OK command letting you know that it has completed that transmission. To send another longer or shorter transmission, resend the QISEND command and change the “6” that to either a larger number for more characters, or a smaller number of less characters.  That number limits how many characters can be entered at a time. You can send other AT commands after the transmission.

Let me know if there’s any issues!

David

[David Mozombite]

Hi Sean,

Do you see a blue light lit on your Sixfab? If it is not, then the problem could stem from your EG25-G, try reseating it by removing it, and reconnecting. It will take a few minutes to power back on. Following this I recommend that you try two things:

First, ensure the the EG25-G module is connected and built up with the UFL antennas. Also, using the included USB cable cable in the Sixfab, connect the Sixfab to the Pi, try lsusb -t again and see if it works now. If it does not, swap the connection from a USB 2.0 to a USB 3.0 connection (black USB port to blue USB port).

Second, try a different USB cable. Any USB cable will work. But the best results will come from the shortest possible USB cable. If there is a break internally within the USB cable then its possible that there is no data being transferred between the Sixfab and Raspberry Pi.

The cdc-wdm0 commands will not work if your Raspberry Pi cannot detect any Sixfab devices.

Let me know if this fixes it,

Thanks,

David

[David Mozombite]

Hi Sean,

The correct command should be:

sudo qmicli -d /dev/cdc-wdm0 –dms-get-operating-mode

and

sudo qmicli -d /dev/cdc-wdm0 –dms-set-operating-mode=’online’

There should be two (not one) dashes, thank you for bringing this to attention we will fix within the site, and check to make sure this issue is avoided in other locations.

Thank you!

David

[David Mozombite]

First,

Update the repository (repo) of the Raspberry Pi by running sudo apt-get update then sudo apt-get upgrade. Then restart your Raspberry Pi, you should now see the 3.8 version.

Second,

Can you send over the workspace you are using to the BISKIT email (biskit@usfiae.org)? I will try to troubleshoot on my side and report back to you as soon as possible.

Thanks!

[David Mozombite]

Joel,

Thank you for pointing this out, it’s now fixed in the lab.

Let us know if there are any other issues!

[David Mozombite]

Hi Joel!

I ask that you try two things:

First, some of the micro USB cables that are used with the HackRF can be spotty. Try using a different cable and ensure that on the HackRF you can see the USB cable light (right of the RF light). Another way to check if your Raspberry Pi and HackRF is working properly is by typing into the command into the terminal:

lsusb

If you do not see the “Great Scott Gadgets HackRF One SDR” listed, then you will need to try a different USB cable.

Second, shift around the center frequency, since the keyfob’s precise frequency can shift from device to device try increasing the center frequency to 434000000 (434 MHz). If you still don’t see it, shift your frequency downward to 432,000,000 (432 MHz) and see if the signal is in that area.

Let us know if this helps!

David

[David Mozombite]

Also,

Referring to the issue on apt vs apt-get, apt can be used, and doesn’t cause any issue over apt-get. Through some research, and what you found, the commands are essentially interchangeable. An important difference when updating packages:

“apt-get upgrade” it will upgrade all packages that can be upgraded without removing other packages or installing new packages.

“apt upgrade” upgrades all packages that can be upgraded without removing other packages.

Essentially, apt is a new version of the command, where as apt-get is still older, but still usable and more than likely won’t be depreciated any time soon. Ultimately, use whichever comes to mind first, there should be no issue with which ever is used.

[David Mozombite]

Hi Leo,

I was unable to recreate your error, however I noticed that you have already downloaded the files for the Proxmark previously. I recommend that you delete the existing Proxmark3 folder through the file manager, it should be in your home/pi folder. Clone from the repo once more, change your current directory to the proxmark (cd proxmark3), and attempt to make accessrights once more.

Apologizes for the late response,

David

[David Mozombite]

Hi Leo,

Yes, unfortunately the RFID tags included with the RC522 are not capable of changing UID, we asked that you use the Proxmark RFID tags in the material sections of the task. The cards included with the Proxmark are equipped with the magic backdoor that allows for the changing of UIDs. This difference is demonstrated in the Proxmark section of the lab, only specific RFID tags versions can change. If you try to scan your card and you see that the error you have experienced, then it is a compatibility issue with RFID tags.

Apologizes for the late response,

David

[David Mozombite]

Hi Leo,

We are working to get the Exploring Raspberry Pi book to you. We will contact you over email with the pertinent information to get this solved. In the mean time, you are still able to complete the labs as written so please continue forward.

Thanks!

[Author]

Posts