View allAll Photos Tagged debuging
My maternal grandfather was a service engineer for Allis-Chalmers from approximately WW2 until the early 1970s, and this involved flying to various customer sites to debug A-C machinery.
Various customer sites everywhere except maybe the poles, and this included at least one trip to Peru, where he got a rug that we assumed was made of pieced together furs. I don't know exactly when he make the peruvian trip, but I remember this rug sitting in the basement den of their West Allis house from as early as I can remember things.
Well, eventually my grandparents all died, and this rug ended up in my mother's hands, where it hung on the wall for many years until it got (what we thought was) a little moth-eaten and was taken down for repairs, only to be forgotten until today when I cleaned out the closet it was stored in.
When I saw it, it was covered with dust, so I picked up and gave it a vigorous shake only to discover that it was NOT pieced together furs, but hides that had appropriately dyed fur glued to it. Glued to it over 50 years ago, so it wasn't so much /glue/ anymore as powder, so the shake resulted in an explosion of fur all over the room it was in.
I can't fix this (well, I *could* fix this in a perfect world where I wasn't constantly fighting depression or wasn't 60+ years old, but this ain't that world) so I'm afraid we're going to have to toss it in the bin.
This is as annoying to find out as it was to discover that 578 was scrapped after the enthusiast who bought it from the Brillion & Forest Junction lost interest.
Damnit.
How to debug a C/C++ program with Nemiver debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
Enabling PWM for the backlight pin seems to mux *all* PWM pins to PWM mode, which isn't good if you're using them in GPIO mode already to toggle other logic
RenderGlow = TRUE
RenderGlowIterations = 2
RenderGlowLumWeights
* X = 0.299
* Y = 0.587
* Z = 0.114
RenderGlowMaxExtractAlpha = 0.065
RenderGlowMinLuminance = 0.000
RenderGlowResolutionPow = 9
RenderGlowStrength = 0.550
RenderGlowWarmthAmount = 1.000
RenderGlowWarmthWeights
* X = 1.000
* Y = 0.500
* Z = 0.700
RenderGlowWidth = 0.000
Posted by Second Life Resident Torley Olmstead. Visit Highgate.
The hard disk on Julie's old Macbook Pro died tonight (bad block right in the middle of /etc/launchd) and before we discovered this we spent a while looking for the magic command+X codes that tweak the boot sequence. Dust Mite helped, too.
Haven't tracked down the cause of this perimeter retraction issue while printing with the latest PLA. Documenting it here for the moment.
Strange how it seems to be Z-height dependent.
Update: Turns out this was caused by a sticky filament spool.
Once again, if the debug room would just let you fly . . .
This is what the other shot should have looked like but it was way beyond me.
Japanese hint book to the rescue, its just kind of grainy, that's all.
Not intending to sound like a downer (yesterday's entry wasn't particularly upbeat) but today was spent debugging code we hoped to release today. We found a very interesting problem that has us stumped. This is as much joy as we could find.
Thanks to Mike for modeling. In truth, after the shot, we were laughing.
This is my "Joy" entry to the 2009 Photo Challenge hosted by photochallenge.org.
How to debug a C/C++ program with GDB command-line debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
After some adventures in debugging all of the parts on the PC board are cooperating nicely, and I have started on the code. As it turns out the edge sensors have a VERY narrow adjustment band, which is a challenge. Still, I have the initial version running, detecting the edge of the ring, and successfully staying inside.
A simple breakpoint list for the nemiver debugger that I've just added. It currently allows you to jump to a breakpoint in source or delete an existing breakpoint.
How to debug a C/C++ program with Nemiver debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
Is it just me, or is there a point to a debugger that can't show the contents dynamic structures? I mean, that's where the data is. If it won't show me the data in the table (this is a dataset btw) then I have to write code to see it. But I'm mucking about in the debugger because the code I wrote to see the data in the table isn't working. fooking stupid visual studio. hate hate hate. (oh yeah, and enterprise manager is not even half as nice as MySQL control center, which is so old it's not even supported anymore. So there!)
Uh. Oh. I. Uh. Sorry. I'll stop now.
chipKIT PGM Programmer/Debugger for use with Digilent chipKIT Platforms
The chipKIT PGM is designed to work with the MPLAB® and MPLAB X development environments available from Microchip. This allows the chipKIT boards, for example, to be used as a more traditional microcontroller development platform using the professional tools available from Microchip. While the PICkit™3 programmer can generate programming voltages needed to program all Microchip PIC devices, the chipKIT PGM can only program devices that are programmable with 3.3V programming voltage. Further, the PICkit3 can source a small amount of current to provide power to some boards being programmed. The chipKIT PGM does not provide power to the board being programmed.
store.digilentinc.com/chipkit-pgm-programmer-debugger-for...
PICkit 3 In-circuit Debugger
The MPLAB PICkit 3 allows debugging and programming of PIC and dsPIC Flash microcontrollers at a most affordable price point using the powerful graphical user interface of the MPLAB Integrated Development Environment (IDE). The MPLAB PICkit 3 is connected to the design engineer's PC using a full speed USB interface and can be connected to the target via an Microchip debug (RJ-11) connector (compatible with MPLAB ICD 2, MPLAB ICD 3 and MPLAB REAL ICE). The connector uses two device I/O pins and the reset line to implement in-circuit debugging and In-Circuit Serial Programming.
Right extruder prints fine. Left extruder (the Inverted stepper one) prints too little plastic at the bottom and too much plastic on top of my Aztec Pyramid test.
Feels like a firmware bug.
Update: Turns out this was caused by a sticky filament spool.
How to debug a C/C++ program with Nemiver debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
Debugging here. Kind of. I'm hooking up the Flavonoid to a USB Oscilloscope which is my bargin basement (mostly serviceable, although finicky with the setup) logic analyzer to see how the I2C (TWI) bus is doing. I'm picky this way — I tend to debug on the atomic level rather than putting everything together and hoping it works, and when it doesn't, taking things apart to see what isn't working. I'm pretty sure the I2C bus is working just fine, but I need to see for sure. I'd output stuff over RS232 only this weekend FTDI, whose little RS232 to USB chip I'm using (FT232RL), is having some kind of server crisis so I can't download the driver to install on my new MacBook what that has never had the driver installed. Sigh.. Anyway, it's a good exercise to use the logic analyzer..
We upgraded our nrf51822 SOCs with the new Nordic BLE SoftDevice v7 and had to port all of our code to the new API version too. For some reason the SPI master API had changed completely (and the change was not mentioned in the migration guide). So we spent the whole weekend trying to get our gyro code working again. Our old code worked but was actually very wrong :) Clock polarity was inverted and phase was inverted so it all worked but was out of specs. So we ported a lot of our code to use the new API and we finally got the SPI code to work. A lot of time was wasted on a mixup with register names in our gyro headers. But we did get to use most of our testgear and it really looked kind of awesome to have that many debugging devices connected to one small board. Plus I got to teach all this debugging to a new member that was added to my team and who will hopefully take over some of the simpler tasks I've been doing.
www.segger.com/products/debug-probes/j-link/technology/in...
GND* = On later J-Link products like the J-Link ULTRA+, these pins are reserved for firmware extension purposes. They can be left open or connected to GND in normal debug environment. They are not essential for JTAG/SWD in general.