View allAll Photos Tagged debugging
We had a bit of a sticky job this afternoon trying to tune a load of radio microphones.
We've got a school production coming up in December. Do you remember when to get cast in a school production you needed a loud voice? Not any more! This production requires the use of all ten of our headset microphones.
Five are working well, one has a dodgy PSU on the receiver which shouldn't be hard to replace, but four of them are giving us real headaches, and we're suspecting some kind of RF interference, or knackered transmitters.
One thing that does make our life easier is this very useful stage box which runs on a digital snake.
Using the AES50 protocol, this box connected 16 XLR inputs and 8 outputs through one Cat5 cable to the mixer at the back of the room. This is really useful, as trying to drag big XLR bundles across rooms is a pain. The AES protocol doesn't use standard ethernet packets and can't be routed through conventional routers and switches. That's not really a problem in the theatre context, where direct patches are easier to manage.
finally debugged the code, freakin 2150 lines of ASM and it turned out to be a stupid CARRY bit, which was screwing up the setpoint display, but only when messing with the menu buttons.
Phew, I'm glad to have this done. Next step is pump control...
The chipKIT™ Uno32 is a prototyping platform that adds the performance of the Microchip® PIC32 microcontroller. It features a USB serial port interface for connection to the IDE and can be powered via USB or an external power supply. To download the IDE, please visit www.chipkit.net/started
The Uno32 board takes advantage of the powerful PIC32MX320F128 microcontroller. This microcontroller features a 32-bit MIPS processor core running at 80 MHz, 128K of flash program memory, and 16K of SRAM data memory.
The Uno32 can be programmed using the Multi-Platform Development Environment (MPIDE). In addition, the Uno32 is fully compatible with the advanced Microchip MPLAB® IDE and the PICKit3 in-system programmer/debugger.
store.digilentinc.com/chipkit-uno32-basic-microcontroller...
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.
Could this be any less helpful? Google found a really good document on debugging debugger problems, but it's not in there.
And, obviously, clicking Help tells me that help isn't installed. Nice. Bloody Visual Studio.
AAAAARGH!
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