loading
21Comments

Tell us about yourself!

Complete Your Profile
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0012: Digital Logic3 weeks ago
    HackerBoxes 0012: Digital Logic

    Anyone with Windows 10 able to use their USB Blaster? Every time I try to use it my machine crashes. I'm using the drivers that came with Quartus 16.0.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0010: Phython Pi3 months ago
    HackerBoxes 0010: Phython Pi

    The file should have been created in step 2-A. If it wasn't, retry step 2-A and confirm the file was created. To write to /etc/wpa_supplicant you need root access so be sure you used a root terminal and not a regular terminal.If the file isn't being created, run step 2-A without redirecting the output (wpa_passphrase "<ssid of your network>") and copy the output after you enter in your network's passphrase and put it into the file manually.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0010: Phython Pi3 months ago
    HackerBoxes 0010: Phython Pi

    I have the EXACT same problem. It shows up as a 2gb partition with 14g unpartitioned. I've tried various SD format utilities, some report the format ran successfully, but then reinserting the card shows the same 2gb partition.I've given up and started using a different card.I suspect the batch of SD cards packaged in this box was bad.

    I've finally got a fix for my wireless network problems. It looks like it's a bug in Wicd not waiting long enough for the connection to be established and reporting a "bad password" instead of a timeout error.I've uninstalled Wicd and installed network-manager using these instructions:http://forum.armbian.com/index.php/topic/1775-wicd...But how did I get online in the first place to download those files using apt-get?! I manually connected using wpa_supplicant at the command line. Here's how:1. open up a root terminal (applications menu -> system -> root terminal)2-A. wpa_passphrase "<ssid of your network>" > /etc/wpa_supplicant/wpa_supplicant.conf2-B. when you hit enter you will be prompted to enter your wireless network's passphrase.3-A. wpa_supplica...see more »I've finally got a fix for my wireless network problems. It looks like it's a bug in Wicd not waiting long enough for the connection to be established and reporting a "bad password" instead of a timeout error.I've uninstalled Wicd and installed network-manager using these instructions:http://forum.armbian.com/index.php/topic/1775-wicd...But how did I get online in the first place to download those files using apt-get?! I manually connected using wpa_supplicant at the command line. Here's how:1. open up a root terminal (applications menu -> system -> root terminal)2-A. wpa_passphrase "<ssid of your network>" > /etc/wpa_supplicant/wpa_supplicant.conf2-B. when you hit enter you will be prompted to enter your wireless network's passphrase.3-A. wpa_supplicant -D n180211 -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf3-B. the parameter after -D is the driver. try "wext" if n180211 doesn't work for you.4. the wpa_supplicant program will run in the foreground and will manage the connection, so open a second root terminal like you did in step 1.5. dhclient wlan0This should get you connected to your network. Now you can run the apt-get commands in the form post I linked up above. If you run into problems, google wpa_supplicant, there's a ton of examples of how to use it to connect to your wireless network out there.

    Yes, I was having the exact same problem. And then my card died completely (can't partition it, format it, or do anything). I'm now using a new SD card and the performance warnings have gone away and it's running well.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0010: Phython Pi3 months ago
    HackerBoxes 0010: Phython Pi

    One issue I ran into with the Orange Pi Lite is that it was generating a partially-random MAC address on boot every time. It looks like this is a bug in Armbian. See: http://forum.armbian.com/index.php/topic/1738-opi...The fix is to edit the file /etc/modprobe.d/8189fs.conf and enter in a new MAC address; probably change the first three byte values to "00:e0:4c" then the last 3 can be whatever you want. Now you've got an Orange Pi Lite that will have the same MAC address every time you boot it up.Why care about the MAC address? Some wireless networks might have access control based on MAC addresses. Or your router's DHCP server might give it a different IP every time it connects because the MAC address keeps changing.

    My 16gb card has somehow become corrupted. I've tried many different MicroSD readers/adpaters and they all think it has an unreadable 2gb partition and 14gb of unused space and I can't do anything to change the partition table or even format the thing now.I had been having some slowness that seemed to be related to the filesystem, so I think my 16gb card might have been off to begin with. But I have an 8gb from a previous Hackerbox and that I've put Armbian on and it's running great now.

    I didn't receive header pins for the display or the female to male cables. If you've received previous hackerboxes you might have some spare header pins and/or m/f wires. If not, soldering the jumper wires would probably work.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0010: Phython Pi3 months ago
    HackerBoxes 0010: Phython Pi

    Just a heads up on the micro SD card reader that comes with this kit. A similar (the same model actually, I think) reader came in a previous Hackerbox and it didn't seem to read the card. So I pushed the card in as hard as I could and wound up breaking the reader.If you're having problems with the reader, do NOT force the card further in. Instead, pull the card back out a couple millimeters. Then the pins on the reader engage with the card and your computer should recognize the card.

    I was having problems connecting to my WPA2-PSK wireless network (using Armbian). What I've found works is to open up the Wicd Network Manger (click on the computer screen icon just left of the "Orange Pi Lite" text in the upper-right of the screen). Then click on the down arrow on the far right of the menu near the top of the window and select "Preferences" from the menu that appears. Then go into the "Advanced Settings" tab and under "Driver" try using "none" or "nl80211" instead of "wext" which is probably the one selected by default.I've still had some intermittent connectivity issues, so maybe the problem is deeper, but at least I was able to run an "apt-get update" and "apt-get upgrade" to up...see more »I was having problems connecting to my WPA2-PSK wireless network (using Armbian). What I've found works is to open up the Wicd Network Manger (click on the computer screen icon just left of the "Orange Pi Lite" text in the upper-right of the screen). Then click on the down arrow on the far right of the menu near the top of the window and select "Preferences" from the menu that appears. Then go into the "Advanced Settings" tab and under "Driver" try using "none" or "nl80211" instead of "wext" which is probably the one selected by default.I've still had some intermittent connectivity issues, so maybe the problem is deeper, but at least I was able to run an "apt-get update" and "apt-get upgrade" to update armbian.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0008: Clockwork5 months ago
    HackerBoxes 0008: Clockwork

    I've found that in the gettemp function in main.c, I need to cast the variable raw to float on the return otherwise odd things happen.return 76 - (float)raw * 64 / 637;I'd love to know where that formula for taking the ADC value of the thermistor came from. It's pretty effective and saves a lot of math overhead,

    I've got the code running, but there are still some bugs that need I need to ironed out (mostly problems with button presses). If you're playing around with the code as well, there are a couple things I wanted to quickly share that took me a while to figure out.in ds1302.h the pins for the clock, DS_CE, DS_IO, DS_SCLK, need to be changed to P1_1, P1_2, P1_0. In ds1302.c the sendbyte() and readbyte() functions have these ports hard-coded in assembly and therefore also need to be updated. Replace _P1_2 with _P1_0 then replace _P1_1 with _P1_2.In main.c, the port mode for the clock pins are being changed because their hardware included pull-up resistors on those pins. We don't have pull-up resistors on the pins, so we don't want to change the pin mode. 187. P1M1 |= (1<<6) | (1<&l...see more » I've got the code running, but there are still some bugs that need I need to ironed out (mostly problems with button presses). If you're playing around with the code as well, there are a couple things I wanted to quickly share that took me a while to figure out.in ds1302.h the pins for the clock, DS_CE, DS_IO, DS_SCLK, need to be changed to P1_1, P1_2, P1_0. In ds1302.c the sendbyte() and readbyte() functions have these ports hard-coded in assembly and therefore also need to be updated. Replace _P1_2 with _P1_0 then replace _P1_1 with _P1_2.In main.c, the port mode for the clock pins are being changed because their hardware included pull-up resistors on those pins. We don't have pull-up resistors on the pins, so we don't want to change the pin mode. 187. P1M1 |= (1<<6) | (1<<7);188. P1M0 |= (1<<6) | (1<<7);For a brighter display try adding P3M0 = 0xFF;below the above two lines.Also in main.c, the timer0_isr() function controls updating the display. P3_0 through P3_7 pins are used for the segments, and P2_0 - P2_3 are used for the digits on our display. This function needs to be modified to reflect that.114. P2 |= 0x0F;119. P3 = dbuf[digit]121. P2 &= ~(0x8 >> digit);And be sure to change the switch pins in the code.31. #define SW2 P2_733. #define SW1 P2_6In led.h there are two arrays, ledtable[] and ledtable2[]. The second table is unique to the hardware for their project (their 3rd digit is inverted). We don't need it, so delete that table completely. Then modify updateTmpDisplay() and change the reference to ledtable2 in line 86 to just ledtable.You may also need to invert the entries in ledtable[]; basically replace the value with the "was" value you see in the comment next to it. I use sdcc and stcgal to compile and flash the code. I use the project's makefile to automate the process. I had to edit Makefile and change SDCC (remove the path, set it to sdcc), STCGALPORT (for me it's COM6, but set it to whatever COM port your USB to TTL dongle is on), and I had to change STCGAL to just "stcgal" without the path or .py. Then run make, and make flash. When you run make flash, stcgal will wait while you cycle the power on the clock, then it'll start flashing.The dot for the third digit will blink with the colon. That's because this code uses their inverted third digit's dot to be the top of the colon, whereas we have the luxury of having a separate colon. I haven't fixed this yet, but fixing it should be a simple matter of looking for calls to dotdisplay() and filldisplay() where the first argument of either is a value of 2, the third argument should be changed to a 0.The major problem I'm having is a single button press is registering multiple actions instead of 1 action per press. The colon also blinks fast for me. I think both problems are related to how the timing is handled. I could try increasing the values passed to _delay_ms() in the main loop, but I think I'm going to try to rework how button presses are handled and maybe stick the colon flash into the button press (debounce) timer.

    The button issue was my own doing. The code refers to a RELAY pin is an extra LED on their hardware that we don't have. I commented out the 3 lines of code that turn it on, wait, then turn it off. Turns out the wait part is important to the main loop's timing. Once I uncommented that line, it works much better.In led.h, if you change all the values in ledtable[] back to what they were, you also need to modify the updateTmpDisplay() function and replace "tmp&=0x7F" with "tmp|=0x80" on all 4 lines, otherwise the colon/periods won't work.

    I've created a fork of of Jens Jensen's stc_diyclock project on GitHub and modified the code to work with the digital clock kit that came with this HackerBox. You can grab the code from GitHub at https://github.com/ruthsarian/stc_diyclock. It's a starting point for those who want to mod their clock.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0008: Clockwork5 months ago
    HackerBoxes 0008: Clockwork

    I soldered a 1k resistor in parallel with the 10k resistor on the light sensor (rather than having to desolder the display to get at the back of the board to desolder the 10k resistor) and that gave it the sensitivity I preferred. You could do the same with a 2.2k resistor for a little less sensitivity. I opted for the lower value because the display is especially bright so I wanted it on its dim setting even when it's somewhat light out.

    My display is working again. I've added the 4-pin header to the pcb and have been able to reprogram the clock through the header. The kit that the stc_diyclock project is based on has the digit pins and segment pins reversed. The external clock is on different pins as well. I tried modifying the code to reflect this, but something still isn't right.I'll keep playing with it.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0008: Clockwork5 months ago
    HackerBoxes 0008: Clockwork

    What positions do you have your thermistor and photoresistor attached to?The instructions have the photoresistor in R5 for and the he thermistor in R4, but the schematic has it the other way around. I suspect my problem is I need to swap the two, but I'd like some confirmation before I start trying to desolder the display so I can get at the pads for R4 and R5.

    Thanks for the confirmation. I must have something wired wrong or maybe a short somewhere. I'll poke around and see if I can find anything.If I get anywhere with reprogramming it, I'll definitely share here.

    View Instructable »
  • ruthsarian commented on HackerBoxes's instructable HackerBoxes 0008: Clockwork5 months ago
    HackerBoxes 0008: Clockwork

    About the 4-digit clock...Has anyone tried programming the STC15F204EA that drives the digital clock? I took a stab at it using the USB-to-serial module we got in the box, the 4-pin header (above the switches) on the PCB and sctgal, but I couldn't get sctgal to dump information about the chip. It seems the TxD and RxD pins on the chip used for ISP are also used to drive the display; I wonder if that's creating a problem.I found this project on GitHub to update the firmware on a similar (but not the same) clock kit. The MCU is the same, but the pins on that project are different from ours. It seems like it might be a starting place to updating the firmware on our clocks to use a 12 hour format, or Fahrenheit instead of Celsius.Does anyone notice the display changing brightness based on t...see more »About the 4-digit clock...Has anyone tried programming the STC15F204EA that drives the digital clock? I took a stab at it using the USB-to-serial module we got in the box, the 4-pin header (above the switches) on the PCB and sctgal, but I couldn't get sctgal to dump information about the chip. It seems the TxD and RxD pins on the chip used for ISP are also used to drive the display; I wonder if that's creating a problem.I found this project on GitHub to update the firmware on a similar (but not the same) clock kit. The MCU is the same, but the pins on that project are different from ours. It seems like it might be a starting place to updating the firmware on our clocks to use a 12 hour format, or Fahrenheit instead of Celsius.Does anyone notice the display changing brightness based on the photoresistor? It doesn't seem to be doing anything for me. I checked the voltage across the photoresistor with a multimeter and the photoresistor itself is definitely working, which makes me think the firmware isn't even using it.

    View Instructable »
  • ruthsarian followed HackerBoxes5 months ago