Skip to main content ↑ ↓

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - pppd

4
Bus Blaster JTAG debugger / Re: [SOLVED] Anyone successful with the KT-Link/SWD?
Thanks a lot, that was it! Now it works as advertised :) I just need to figure out why I can't make it to work with OpenOCD and my ARM programming can finally begin without VMWare! It seems to have problems with STM32F100 unless I disable fast memory access, but at least I know the board is okay.

I will also try to make a combined jtagkey/ktlink SVF for the CPLD so I don't need to flash it every time I change my project.
6
Bus Blaster JTAG debugger / Re: Anyone successful with the KT-Link/SWD?
Can you please try the CrossWorks without a license? I never activated mine but it still lets me try the target->connect feature. I was waiting for it to start working before using my license.

I tested the BBv2 with CPLDs and it can program them just fine.
8
Client software / Re: Android client
It's been really a long time since I did this and since I am not really a MicroChip guy the code was just modified to work. I remember I got some hints from Ian so what I really had to do is uncomment a few parts of the code. In the version I could locate on my HDD it you activate the UART by pressing the update button after it's already powered up. I will try to help more after the weekend.
9
Bus Blaster JTAG debugger / Re: Anyone successful with the KT-Link/SWD?
I tried it with LPCXpresso (LPC1114), STM32VLDISCOVERY both host (STM32F103C8T6) and target (STM32F100RBT6B). I am sure I was using the right pins because they worked just fine when using another STM32VLDISCOVERY board flashed with Versaloon as the debugger interface or partly worked when using the BP + pirateSWD python script. I tried the 30 day trial of Cross Studio for ARM and Openocd.

To be honest I have no idea about the KTLink original design so I can't really tell if there's anything wrong or not :/ I just hoped someone used it successfully and could share their experience. Attached is OLS recording of an SWD target identification attempt made with BBv2 + Cross Studio.
10
Project logs / Re: Door lock reminder
Hah, sure.. but it was much cheaper to build the device than to go to a psychiatrist to take care of that ;) Anyway, I got it all running yesterday and I hope to never have to return to check the door again.

Also, I'm probably not the first one to do it this way... but if you don't like through-hole parts just as much as I hate them you may want to use surface mount resistors, capacitors or even transistors on your bread board circuits. There's an easy way to do that, just use the pin headers and solder the 1206/0805 parts to them:
[attachment=0]You can see a few 1206 resistors, 0805 capacitor, 0805 RC oscillator I had to create for recovering misconfigured fuses in an ATTiny device and a SOT23 transistor.
12
Project logs / Door lock reminder
I don't know about you guys but I constantly catch myself wondering whether I have locked my apartment door or not. I never actually forgotten to turn the key but I did come back just to make sure a bunch of times. Usually it is when I am in a rush trying to catch a bus knowing the next one won't be soon. Anyway, I wanted to do it for a long time, but I finally got some time this evening and I came up with a simple device that will do the job of remembering for me.

Basically this is an ATtiny13 chip with two reed switches and a buzzer:
[attachment=3]
The chip stays in power-down mode using just 4 uA including the shorted door switch (via 1M + 10k resistors). When the door gets opened it activates, powers up the second switch via PB3 and waits for the door to be closed again checking PB1 level. It then checks the lock status and keeps beeping until you lock the door (PB4 level). Once you do that it returns to the power down mode waiting for another door opening. Some energy could be saved by using sleep instead of delays while active, but I guess the door won't be open for too long anyway so it doesn't really matter. One thing I will fix later is the lock & unlock scenario where you lock the door and then unlock it leaving the door closed. It will not be detected and therefore you can still leave it unlocked. But for now it is just what I needed.

The door sensor is a typical alarm type of reed switch and the for the lock I used a magnet glued to one of the lock "bolts" (what are they called?) the lock switch is glued inside the door frame.
[attachment=1]
The reason it took so long to get it done is that I wanted to make a PCB for that and I hate making them ;) Luckily, my sister sent me a few cool small solderless breadboards from China 5RMB each ( less than 1 USD !! ) so there will be no PCB for that, I'll just put it into a small box and glue it to the door frame. I would have done it now but it's already past 22 and I need to drill a hole in the frame to hide the cables.

The "final" device looks like this:
[attachment=0]

Attached is the source code if anyone wants to use it.
13
Client software / Re: Client beta testers
I'd rather stick to this forum. Secret projects tend not to be successful and I want it to be open source anyway. Maybe Ian could fork it into a new thread.
14
Client software / Re: Client beta testers
I have a BT adapter converted to work with OLS. I started designing a daughter-board with a LiPo and auto-switching power usb/battery. I modified the OLS firmware to check for Bluetooth presence and failover to USB when BT is not present.

I will gladly give the iOS/Android client a go since I am going to refresh my knowledge on coding for this platforms anyway. I can't promise anything like when it's going to be ready since I am known to underestimate the time required to accomplish certain tasks and I have a few other projects which have been on my waiting list for a long time now.

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.02292423792session_write_close ( )...(null):0
20.02342555408ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.02352556184Database_MySQL->query( ).../DatabaseHandler.php:119
40.08332694936Database_MySQL->error( ).../Db-mysql.class.php:273