info: Configuration "default" will build with toolchain "C18" at "C:Program Files (x86)Microchipmplabc18v3.46bin". warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIRIO.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIrReflect.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainhal_Lin_m.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainusb_config.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIRIO.c" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIrReflect.c" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainhal_Lin_m.c" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIRIO.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIrReflect.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainhal_Lin_m.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainusb_config.h" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIRIO.c" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainIrReflect.c" which does not exist in the disk. The make process might not build correctly. warning: Configuration "default" refers to file "C:UsersKevin.Kevin-PCDesktopHackingFirmware-mainhal_Lin_m.c" which does not exist in the disk. The make process might not build correctly.
I'm still having trouble getting it to compile in MPLAB-X It says it can't find the source files, even though they are listed in the project pane. Is there some particulary directory structure I need to reorganize them into?
after failing to compile from the source bundle I did a svn checkout of the entire open hardware repo, and opened the USBIRToy.X project in MPLAB-x. It gives me a lot of project load errors. and can't seem to find any of the sources.
It's probably something obvious like setting a configuration or something. A clue?
****EDIT*** Never mind. The product page only pointed to the compiler, and it looks like you need the IDE as well. Downloaded and now opened the project. I'm having a little trouble finding prj_usb_config.h
Is this a microchip "system" file? because I can't seem to find it in the source bundle.
***original*** This is totally intriguing! I'm mostly an avr guy. Are there any pointers for setting up the compiler environment on windows? I downloaded mplab, but don't see makefiles etc in the source bundle.
An alternative would be a hex file, though it's about time I dipped back into pic land. (I have a super old dev kit)
I managed to disable driver signing, and got it to work with OLS exactly once, now it captures without any input (flat line) I tried uninstalling and re-installing, and no love.
I took it back to a windows 7 machine, and everything (ols capture, winlirc) worked fine.
Hi, I could swear that this was working before, but I'm having problems now. I upgraded the firmware to v.22, and I'm using ols 0.9.6.1 (also tried 0.9.5)
For a sample source, I've tried an air conditioner remote, and tv-b-gone.
It appears to capture (led blinks in time with the tv-b-gone) but the graphed signal is all low. any clues?
Addendum: I tested it in Winlirc and it works fine there. including irgraph, and rawir. Also went back one more ols version to 0.9.4 and no good there either (flatline!)
Flexible power. Can be powered directly from the Pi, standalone with a battery or wall-wart, or USB power. This is important if your shield takes more power than the Pi can provide or if you want to undock it for standalone operation. Programmable via the Pi’s UART on the GPIO pins, or an FTDI USB-Serial adapter or ISP. Header for connecting Fastrax UP501 GPS. DS3234 Real time Clock. The Pi doesn’t have it’s own battery backed RTC. You can set a program in the AlaMode to report the time to the Pi via serial or I2C Micro-SD card slot. Useful for datalogging, and big-memory for your Arduino applications Row of Servo Headers connected to the PWM pins with a configurable power and ground rail
Dangerous prototypers will be interested to know we used Seeed for prototyping procurement and the PCBs are beautiful
Hi folks, I just wrote up a nice little tip I learned while debugging the bootdrive. You can get all the background at my blog: http://baldwisdom.com/precious-memory/ But if you want just the meat (Though it is useful to read some of the background, useful links etc...):
First find your build directory. On Windows 7 this is users<youruser>AppDataTempbuild<a bunch of numbers>.tmp
Now, assuming you have the avrdude files somewhere in your path, use the command:
avr-size -C --mcu=atmega328p <yourelf-file.elf> For example, the current version of Bootdrive gives me:
Cool. Actually the times I was measuring was on my own device, and I hooked the scope up to one leg of the diode. I wrote some code for the TV-B-Gone to trigger a nikon camera a while ago, and that worked fine (first time!) I decided to implement canon blind (don't have a canon dslr) and wanted to check the timing. Thank you for the explanation, it was very helpful! To play with, I bought both the demodulator and the detector that USBIRtoy uses.