Re: using Byron Jeff's TLVProgrammer
"Maxim Wexler" <[email protected]> Sat, 16 Dec 2006 12:47:02 -0700
| Newsgroups | gmane.comp.hardware.microcontrollers.gnupic |
|---|---|
| Message-ID | <[email protected]> |
On 12/16/06, Byron A Jeff <[email protected]> wrote: > > On Sat, Dec 16, 2006 at 10:04:09AM -0700, Maxim Wexler wrote: > > Hi group, > > Hi, > > > > > Planning to use this programmer w/ pkp and 16f88 chip on a breadboard. > > I believe there's a report of it working with pkp (that's the console app > for > pikdev right?) Yeah, the gui keeps crashing but that's allright if I can get the same functionality in Konsole. FWIW here's a typical debug session for pikdev. Don't have a clue what it's about just that it seems pikdev specific. Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 14100)] [KCrash handler] #6 0xb5e7616c in memcpy () from /lib/libc.so.6 #7 0xb7395c9b in std::string::_S_construct<char const*> () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5 #8 0xb7392319 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5 #9 0xb7389c51 in std::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::basic_stringbuf () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5 #10 0xb738b597 in std::basic_istringstream<char, std::char_traits<char>, std::allocator<char> >::basic_istringstream () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5 #11 0x0807cfeb in PicFactory::getPic (this=0x8234d90, picname=0x8234d70 "p16f628") at PicFactory.cc:102 #12 0x08060629 in BuiltinProgrammer::selectDevice () #13 0x080604c0 in BuiltinProgrammer::enter () #14 0x08087539 in PikMain::updateProgrammer () #15 0x0808a7df in PikMain::PikMain () #16 0x0807f116 in main () Maxim > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >