• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


dummy manual for ATTiny85
#1
Hey

i have a ATTiny85 here and want to use it to reduce cpu wast on the reciver.

Some questions
1. are all the pins needed for operation or only to flash the chip?
2. are the pin numbers wiringX or BCM?
3. how to flash it for dummy's?

kind regards
Mark
 
Reply
#2
There are quite detailed instructions on the wiki about how to set it up (http://wiki.pilight.org/doku.php/low-pass_filter). However, the pin numbers on the drawing are not very good, and do not make much sense. It helps to go by the default settings for the pins (http://wiki.pilight.org/doku.php/settings). They are wiringx pin numbers.

Not all pins are needed for operation, only the +V, GND, data in, and data out pins are needed for using it. The others can be disconnected I believe.
 
Reply
#3
thanks
i was looking on the wiki but didn't find the page you gave me.
i added the link to the receiver page

Thanks
 
Reply
#4
The link is on the hardware page already, might be good to add it to the sidebar too though, it is a very useful page.
 
Reply
#5
I use a raspberry b rev1 so i need to change the pin numbers

Quote:to change the pins create an .avrduderc file in your home directory containing (the numbering is wiringpi numbering!):

Code:
programmer
    id    = "gpio";
    desc  = "Use sysfs interface to bitbang GPIO lines";
    type  = gpio;
    reset = 8;
    sck   = 11;
    mosi  = 10;
    miso  = 9;
;
and connect the T85 like the picture
https://github.com/pilight/pilight_firmware
http://wiringpi.com/pins/

but it doesn't do what i expect
Code:
pilight-flash -f /etc/pilight/pilight_firmware_t85_v3.hex
[ Mar 29 18:06:37:26950] pilight-flash: INFO: **** START UPD. FW ****
[ Mar 29 18:06:37:30779] pilight-flash: DEBUG: running on a raspberrypi
[Mar 29 18:06:37:210349] pilight-flash: ERROR: AVR device not responding
[Mar 29 18:06:37:388403] pilight-flash: ERROR: AVR device not responding
[Mar 29 18:06:37:566608] pilight-flash: ERROR: AVR device not responding
[Mar 29 18:06:37:567581] pilight-flash: ERROR: AVR unknown
[Mar 29 18:06:37:569083] pilight-flash: INFO: First run firmware_getmp
[Mar 29 18:06:37:570012] pilight-flash: INFO: **** FAILED UPD. FW ****
[Mar 29 18:06:37:571157] pilight-flash: DEBUG: freed options struct
 
Reply
#6
I don't know so much about this, I've only flashed some ATTiny45's on Rev2 boards, so I can't really help you. Maybe @curlymo can.

Although, are you sure you got the wiring right according to the wiringX pin numberings? And if necessary, adapted them using config.json? I'm not 100% sure, but your log does say "AVR device not responding", which sounds like incorrect wiring to me...
Additionally, you could try to use pins that are the same through the hardware revisions, and then define those in your config.json using the settings wiki page above.
 
Reply
#7
I also tried this configuration


Code:
{
        "devices": {},
        "rules": {},
        "gui": {},
        "settings": {
                "log-level": 4,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "send-repeats": 10,
                "receive-repeats": 1,
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/",
                "webserver-port": 5001,
                "webserver-cache": 1,
                "firmware-update": 1,
                "firmware-gpio-reset": 7,
                "firmware-gpio-sck": 11,
                "firmware-gpio-mosi": 10,
                "firmware-gpio-miso": 3
        },
        "hardware": {
                "none": {}
        },
        "registry": {}
}
 
Reply
#8
Maybe it is the hardware: "none" definition that it does not like. What happens if you set it to the default 433gpio?
 
Reply
#9
i replaced all the cables
replaced all the resistors
replaced my config.json with

Code:
{
        "devices": {},
        "rules": {},
        "gui": {},
"settings": {
        "port": 5000,
        "standalone": 0,
        "log-level": 4,
        "pid-file": "/var/log/daemon/pilight.pid",
        "log-file": "/var/log/pilight.log",
        "send-repeats": 10,
        "receive-repeats": 1,
        "webserver-enable": 1,
        "webserver-root": "/usr/local/share/pilight/",
        "webserver-port": 5001,
        "webgui-template": "default",
        "webgui-websockets": 1,
        "webserver-cache": 1,
        "webserver-authentication": [ "username", "password" ],
        "webserver-user": "",
        "whitelist": "",
        "protocol-root": "/usr/local/lib/pilight/protocols",
        "hardware-root": "/usr/local/lib/pilight/hardware",
        "action-root": "/usr/local/lib/pilight/action",
        "operator-root": "/usr/local/lib/pilight/operator",
        "firmware-update": 1,
        "firmware-gpio-reset": 10,
        "firmware-gpio-sck": 14,
        "firmware-gpio-mosi": 12,
        "firmware-gpio-miso": 13,
        "watchdog-enable": 1
},
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }
        },
        "registry": {
                "pilight": {
                        "version": {
                                "current": "6.0"
                        }
                }
        }
}


Code:
pilight-flash -f /etc/pilight/pilight_firmware_t85_v3.hex
[Mar 29 19:16:21:454077] pilight-flash: ERROR: config setting "pid-file" must point to an existing folder
[Mar 29 19:16:21:455768] pilight-flash: DEBUG: garbage collected config settings library
[Mar 29 19:16:21:456667] pilight-flash: DEBUG: garbage collected config devices library
[Mar 29 19:16:21:457510] pilight-flash: DEBUG: garbage collected config rules library
[Mar 29 19:16:21:458635] pilight-flash: DEBUG: garbage collected config gui library
[Mar 29 19:16:21:459769] pilight-flash: DEBUG: freed options struct
[Mar 29 19:16:21:460659] pilight-flash: DEBUG: freed options struct
[Mar 29 19:16:21:461492] pilight-flash: DEBUG: freed options struct
[Mar 29 19:16:21:462604] pilight-flash: DEBUG: garbage collected config hardware library
[Mar 29 19:16:21:463656] pilight-flash: DEBUG: garbage collected config registry library
[Mar 29 19:16:21:464803] pilight-flash: DEBUG: garbage collected config library
[Mar 29 19:16:21:466042] pilight-flash: DEBUG: freed options struct
 
Reply
#10
Have you been able to flash it yet?
I think you need to change the path to the pid-file in your config.json, it says that the path does not exist. Maybe change it to
Code:
...
        "pid-file": "/var/log/pilight.pid",
...
,
so without the daemon/ in there.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Flashing ATTiny85 troubles apacheguy 2 1,716 01-26-2017, 04:48 PM
Last Post: apacheguy
  attiny85+433mhz receiver+led (lpd6803 ws2801) betonishard 1 3,697 08-26-2014, 07:12 PM
Last Post: creamers
  Impuls Remote manual? mike 1 8,052 05-25-2014, 01:19 PM
Last Post: mike
Question Schematics for dummy's TheWheel 5 4,809 09-25-2013, 12:53 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)