View allAll Photos Tagged debugging
All surface mount passives are 0603 parts. Yes, they're fiddly, but they're also cheap. Little-known fact: If they bother you that much, 0805 should also fit on the pads.
Learning a new word every day, from the debugger this time! ^_^
(since I had a power outage this week, my fileserver refuses to rewrite the parity on the raid-array... (which it wants to do because the filesystem was shut down unclean). It simply stops rewriting and hangs... not good. Here I removed a drive from the raid1-array and wanted to add it again so it would rebuild to that drive, but well, it rather stays quiet as you can read... ;-))
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.
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.
webcam image with stk11xx driver and 05e1:0501 device.
Image of white paper, please notice the blue line at the top (it should not be there).
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.
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.
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.
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.
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.
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..
Here's an interactive debugger for UBASIC scripts that lets you inspect and set variables, step through line by line etc.
Beta-testers are welcome to download the prototype here.
There's a PDF document here.
Comments, bug reports and suggestions wlecome.
See also this thread on the CHDK Forum.
debugging the onboard computer on the people mover. their diagnostic software was just spitting out line after line after line of hexidecimal numbers.
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.