Jump to content
Hak5 Forums

Search the Community

Showing results for tags 'firmware'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • WiFi Pineapple / Jasager
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • Mark V
    • Mark IV
    • Pineapple Modules
    • WiFi Pineapple University
    • Mark I, II, III
  • Active Projects
    • Bash Bunny
    • Packet Squirrel
    • Lan Turtle
    • USB Rubber Ducky
    • SDR - Software Defined Radio
    • Community Projects
  • Hak5 Shows
    • Hak5
    • HakTip
    • Metasploit Minute
    • Threatwire
  • Community
    • Forums and Wiki
    • #Hak5
  • Other Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Found 27 results

  1. Is there any documentation for the many USB Rubber Ducky firmware images? From what I have been able to surmise in the forums, the duck.hex is the original firmware and the c_duck images are the Twin Duck variants. Can anyone tell me what functions the other firmware images on GitHub might serve and whether they require keyboard interaction to function? Composite_Duck_4cap.hex Composite_Duck_S003.hex Rand_Delay.hex USB_Spammer_v1.0.hex USB_v2.1.hex c_duck_osx.hex c_duck_uk.hex c_duck_us.hex c_duck_v2.1.hex c_duck_v2_S001.hex c_duck_v2_S002.hex duck.hex duck_v2.1.hex duck_v2.hex m_duck.hex m_duck_v2.hex osx.hex usb.hex usb_v2.hex
  2. Hello guys, I faced a lot of problems with my Pineapple Nano 6, such as difficult to recognize SD Card, configuration sometimes is saved and sometimes not, modules sometimes work and sometimes not, need to click two, three or four times to apply a command, and other. I saw same complaining from other guys and they recommended to change the firmware. I was using 1.1.3 and I tried some other, but I still face some problems as I told. My question is: Are you facing problems like this in consequence of firmware? In what firmware did you find stability to work fine with Pineapple? Thank you and regards!
  3. I followed the wiki to update the firmware, but the red blinked for 4min, then green lighted up for once. After that, there was no light and the bash bunny got overheated. So I tried to recover the firmware by following the wiki, but the same thing happened again. It's just not working and my pc can't detect it as a mass storage. Can anyone give me some help?
  4. twin duck firmware

    hey just flashed the twin ducked firmware on my ducky usb, when the ducky is plugged in several PCs, it doesn't always show up as usb drive(F:), in my scriot, theres this, gui r delay 500 string cmd enter delay 1000 F: enter the f: part doesnt always work, so is there a way to let cmd open the drive by name and not my letter? thanks!
  5. I Picked up the Sandisk Wireless Connect 16G at w.mart for $20 figured it would be fun to hack Processor: Marvell: 88wm302 (per FCC filing pictures) I tried pulling apart the firmware, comparing between the three firmware files I was able to find (2034) (2038) (2050) I was able to narrow the checksum down to a 96 byte area of the file but I just can't seem to crack the encoding maybe (3-way cipher??) I do know the version number is checksummed with the value in decimal converted to hex I finally gave up and took the device apart, there is a SD card inside the device. Taking the card out and putting it into a card reader I was able to see the device had (2) 16mb uninitialized partitions the second of them had the device firmware in it. While the card is within the Connect device this second partition is not accessible. File size is stored at the beginning of every file but I have yet to find the drive table so it must be a custom filesystem. I have edited the file 'sort.js' to allow index redirection to my own file I'll be adding this once i get it finished and simplified the process a bit. Notes: settings.xml is accessible from root 'sandisk.com/settings.xml' the device uses a http.post method to rewrite the xml file, I expanded this to try and re-write the scripts but got reply of 'Bad Request' /myconnect/files/ and /myconnect/wfd/ are the same directory javascript is in /static/js/ the media javascript is in /static/mejs css is in /static/css/ Index.html seems to be auto generated from a templatesort.js fills the page
  6. Hi all, I try to update the firmware via the web-interface and it seems like it failed. so I try to do it with the firmware recovery through the (http://wiki.wifipineapple.com/#!troubleshooting.md%23Firmware_Recovery) And it still failing. Afte I upgrade the firmware the ethernet gets disconnected and connected again. I cannot access neither 172.16.42.1 nor 192.168.1.1 after the reboot. and the yellow light is Solid durring this process. Please help! Thanks in advance. PS.: Not sure but i believe I can still save it via accessing the UART, but not sure how!
  7. Flash firmware OS X

    Does anyone know how to flash new firmware for the ducky on OS X? Thanks in advance
  8. Modify firmware source code

    i want to modify the source code of one of the firmware of rubber ducky project, example write in a .text file inside the memory a number each time i plug the memory in a pc ... but a i am a little lost with the code somebody have experience in this, somebody have been working in this issue thanks and sorry my english i am a latinoamerican
  9. Update bunny to firmware 1.3 fail

    Hello, I have upload firmware 1.3 to this m├ęthod : https://bashbunny.com/downloads My bashbunny is a single usb to one partition... My root partition gone.. I search issue.. i dont understant.. I have Respected update method
  10. Hello, I'm trying to compile custom firmware for a rubberducky, because I want to change the ducky's serialnumber. I've found the setting I want to change: \USB-Rubber-Ducky-master\Firmware\Source\Mass_Storage\USB\src\config\conf_usb.h > define USB_DEVICE_SERIAL_NAME "..." // Disk SN for MSC So now I just need to compile this into new working firmware. But I can't find a guide on doing this anywhere, and I haven't done much compiling/coding, so I don't have the experience to do it on my own. I've downloaded "Atmel Studio 7.0" since I read somewhere that that is what's needed, but after a lot of clicking arround and opening files and pressing buttons, I can't seem to get it to compile anything.. Can anyone help me with this? FYI: I've done my fair share of coding for arduino's/pi's and hardware hacking so I'm not a complete noob, but this has left me flustered a bit...
  11. Ok so i wanted to upgrade to firmware 1.3. That didnt work well. The bunny starts to flash the LED red->blue. as intended. Then the LED shuts off. No LED. I tried to boot it 3 times to trigger recovery. It then starts the flash red -> blue. After some time it comes a green LED and then it starts the red -> blue blinking again. After that a green LED and then it goes dark again. If i unplug it and plugs it back in, the green LED is solid for a sec and then ...wait for it...... DARK again. What a fun bunny, i might carry it out in the woods and leave it there :..( It also gets burning hot. I cannot accsess the files either. Maybe there is a way i dont know about? Its this BB dead now? 100 dollars out the window i guess
  12. Firmware update troubles

    Im having some issues updating the bash bunny to the most recent firmware. I am currently on the base firmware from when I have purchased the device and have run apt-get update && apt-get upgrade after getting internet with my linux machine. I then download the firmware .tar file from the downloads area and copy the file to the / directory of the bash bunny. I then safely eject the device in arming mode and plug it back in expecting to see a red blinking light. Unfortunately it does nothing and boots to the regular storage mode and nothing has changed. I have searched the forums for help but I can't seem to figure out why this is happening. Can someone help me out with this issue?
  13. Can someone tell me how to re-do the 1.3 upgrade as FAQ do it from GUI and no option to update firmware manually. (Firmware Recovery -> https://www.wifipineapple.com/pages/faq) Someone said there may have been an issue with my 1.2 to 1.3 upgrade so would like to try and re-load it. I can ssh and upload file its the command to load the .bin file and flash it i am not sure of .. maybe doing it via cli will get more stable results then the gui upgrade. Thanks
  14. I'm trying to upgrade my firmware of this yard stick one. But I keep getting different errors. Now I have the bad address one. root@raspberrypi3:/home/pi/rfcat_170508# rfcat_bootloader /dev/RFCAT_BL_YS1 erase_all RC = 0 (OK) root@raspberrypi3:/home/pi/rfcat_170508# rfcat_bootloader /dev/RFCAT_BL_YS1 download firmware/CCBootloader/CCBootloader-rfcat-ys1.hex Writing :0600000002017B02140363 RC = 3 (Bad Address) Error downloading code!
  15. Is there going to be a new release of the firmware coming out soon? since the last update my nano has gotten gradually worse I barely even use it now and yes Ive wiped everything and reinstalled firmware all over again. You guys mentioned something big last year for nano and tetra and no news since then. Something about kali linux integration I believe. Does my nano have a warranty if I want to send it in? Thanks
  16. UPGRADE TO THE LATEST FIRMWARE Download the latest version of the Bash Bunny firmware from https://bashbunny.com/downloads Verify that the SHA256 checksum of the downloaded firmware files matches the checksum listed at bashbunny.com Slide the Bash Bunny switch into Arming Mode (closest to the USB plug) and plug the Bash Bunny into your computer Copy the firmware upgrade file downloaded in step 1 to the root of the Bash Bunny flash drive. Safely eject the Bash Bunny flash drive (IMPORTANT) With the switch still in Arming Mode, plug the Bash Bunny back into your computer and wait 10 minutes. When the bunny is done flashing, it will pop up as an storage device. INSTALLING LANGUAGES i have opened a pull request on the official repo to add the languages to the /languages folder (.json provided/made by ducktoolkit.com) But for now you will have to manually add them (Atleast from what i understand since i cannot get the ducktoolkit install payload to work) Download the Ducktoolkit compressed file-> https://github.com/hak5/bashbunny-payloads/raw/53a9e7fb69677b0480b2005a590471f4feacd180/payloads/library/DuckyInstall/DuckToolkit-1.0.1.tar.gz Unzip all the .json language files from "\DuckToolkit-1.0.1\ducktoolkit\languages" inside the .tar.gz file to\languages on the BashBunny (Connected while in arming mode) Remove and re-attach the bash bunny, you can now use different keyboard languages INSTALLING "IMPACKET" AND OTHER DEPENDENCIES There are 2 tools folders on the bash bunny itself, one lives in /tools on the Linux file-system which you can see and access using SSH/ Serial access.The other one lives in the mounted drive which you see every-time you connected the bunny as an storage device. What we effectively are going to do is to download the latest impacket source from github, place it on the bash bunny flash-mounted tools folder. re-attach and re-boot the bunny , this will copy the folder into the linux file-system tools folder, where we will install the module. Clone or download -> https://github.com/CoreSecurity/impacket as an .zip file. Unzip the "impacket-master" folder inside the .zip file into the /tools folder while the bash bunny is connected as an storage device (in arm mode) Rename the "impacket-master" folder to "impacket" ( remove and re-attach /reboot the bash bunny on the system. If you go to the same /tools folder now, the "impacket" folder should be gone. Serial/SSH into the bunny so you get a shell. and execute the following commands, in this order "cd" | "cd .." | " cd /tools/impacket/" | "python setup.py install" ( "|" separate each command, dont type the " quotes) remove and re-attach the bash bunny, and you are all good ! :)
  17. BashBunny LED Solid Red during Flashing

    Hi Ya'll, This is my first post on the Hak Forums. So, I'm in a bit of a panic. I finally cracked open my launch day firmware versioned BashBunny. I grabbed the latest firmware from the site, dropped it into the root directory of the BashBunny, and safely ejected. Then I plugged it back in to my computer. The light went green, then almost immediately started flashing red. I thought everything was good, but then after a while, the LED changed to solid red. It's been like that for 30 minutes, and I'm very scared that somehow my new $100 tool got bricked for no reason. Please please someone help soon. I need to sleep, but I can't leave the Bunny powered at the same time. Thanks, -NR
  18. Bash Bunny: Problem [Unsolved]

    Apparently I've tried to update to 1.1 incorrectly. It has a solid green on startup then it turns blank. After three times it goes into recovery mode I am assuming. Then once there it blinks red for a while. Then it turns blank again. I've waited ten minutes tried to replug it in assuming something went wrong it it was done. But it never blinks or goes solid green or blue after the red blinking. But just now It was blinking red then started to alternate red to blue. Now it's blank again, I will wait another fifteen minutes before I try anything else. What exactly is going on? I am assuming it's either trying to recover then flash. I moved the upgrade contents to the root file system. I don't know exactly what went wrong. Easier way to understand the problem: Plug In > Solid Green > Blank LED ........ Ten minutes has passed.... Replug In > Solid Green > Blank LED ....... Ten minutes has passed.... Replug In > Solid Green Blank LED ...... Ten minutes has passed.... Replug In > Blinking Red > Couple of Minutes Passed > Blinking Red . Blinking Blue . Blinking Red > Couple of Minutes Passed > Blinking Red > Couple of Minutes Passed > BLANK LED!!!! Ten minutes has passed... Replug In > Solid Green > Blank LED Every time it tries to recover then it will try to boot three times and try to recover again. It will never fully boot up nor will Kali recognize the file system or that it's plugged in.
  19. [Upgrade] Dynamic Switching

    So, I've made a payload to upgrade the bash bunny to allow for switching on the fly. I'm not posting it yet, because it seems that the PRs are piling up and don't want it lost in the shuffle. i currently have it so that it runs the payload on the switch you switch it to, but feel it could eventually be used to register commands to the script. Would anyone find this useful? Any ideas on other uses detecting the switches could do?
  20. 1.1 and firmware updates

    So after the latest episode of Hak5, you mentioned 1.1 was ready to ship. When will this be available, and is there a new feature list?? You guys are awesome for pumping this out so quickly. I'm super excited.
  21. Hello I have built a usb rubber with at32uc3b1256. but it does not work. when I plug it in to my computer, I receive this error :"A request for the USB device descriptor failed". could anyone tell me, what I should do? thanks. I've used a 12 MHz crystal. this is the conf_clock file: /** * \file * * \brief Chip-specific system clock manager configuration * * Copyright (c) 2011 Atmel Corporation. All rights reserved. * * \asf_license_start * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * 3. The name of Atmel may not be used to endorse or promote products derived * from this software without specific prior written permission. * * 4. This software may only be redistributed and used in connection with an Atmel * AVR product. * * THIS SOFTWARE IS PROVIDED BY ATMEL "AS IS" AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE * EXPRESSLY AND SPECIFICALLY DISCLAIMED. IN NO EVENT SHALL ATMEL BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * \asf_license_stop * */ #ifndef CONF_CLOCK_H_INCLUDED #define CONF_CLOCK_H_INCLUDED // ===== System Clock Source Options //#define CONFIG_SYSCLK_SOURCE SYSCLK_SRC_RCSYS //#define CONFIG_SYSCLK_SOURCE SYSCLK_SRC_OSC0 #define CONFIG_SYSCLK_SOURCE SYSCLK_SRC_PLL0 // ===== PLL0 Options #define CONFIG_PLL0_SOURCE PLL_SRC_OSC0 //#define CONFIG_PLL0_SOURCE PLL_SRC_OSC1 #define CONFIG_PLL0_MUL 2 /* Fpll = (Fclk * PLL_mul) / PLL_div */ #define CONFIG_PLL0_DIV 2 /* Fpll = (Fclk * PLL_mul) / PLL_div */ // ===== PLL1 Options #define CONFIG_PLL1_SOURCE PLL_SRC_OSC0 //#define CONFIG_PLL1_SOURCE PLL_SRC_OSC1 #define CONFIG_PLL1_MUL 8 /* Fpll = (Fclk * PLL_mul) / PLL_div */ #define CONFIG_PLL1_DIV 2 /* Fpll = (Fclk * PLL_mul) / PLL_div */ // ===== System Clock Bus Division Options //#define CONFIG_SYSCLK_CPU_DIV 1 /* Fcpu = Fsys/(2 ^ CPU_div) */ //#define CONFIG_SYSCLK_PBA_DIV 1 /* Fpba = Fsys/(2 ^ PBA_div) */ //#define CONFIG_SYSCLK_PBB_DIV 1 /* Fpbb = Fsys/(2 ^ PBB_div) */ // ===== Peripheral Clock Management Options //#define CONFIG_SYSCLK_INIT_CPUMASK ((1 << SYSCLK_SYSTIMER) | (1 << SYSCLK_OCD)) //#define CONFIG_SYSCLK_INIT_PBAMASK (1 << SYSCLK_USART0) //#define CONFIG_SYSCLK_INIT_PBBMASK (1 << SYSCLK_HMATRIX) //#define CONFIG_SYSCLK_INIT_HSBMASK (1 << SYSCLK_MDMA_HSB) // ===== USB Clock Source Options //#define CONFIG_USBCLK_SOURCE USBCLK_SRC_OSC0 //#define CONFIG_USBCLK_SOURCE USBCLK_SRC_PLL0 #define CONFIG_USBCLK_SOURCE USBCLK_SRC_PLL1 #define CONFIG_USBCLK_DIV 1 /* Fusb = Fsys/(2 ^ USB_div) */ #endif /* CONF_CLOCK_H_INCLUDED */ and this is the conf_usb.h file: /** * \file * * \brief USB configuration file * * Copyright (c) 2009 Atmel Corporation. All rights reserved. * * \asf_license_start * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * 3. The name of Atmel may not be used to endorse or promote products derived * from this software without specific prior written permission. * * 4. This software may only be redistributed and used in connection with an Atmel * AVR product. * * THIS SOFTWARE IS PROVIDED BY ATMEL "AS IS" AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE * EXPRESSLY AND SPECIFICALLY DISCLAIMED. IN NO EVENT SHALL ATMEL BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * \asf_license_stop * */ #ifndef _CONF_USB_H_ #define _CONF_USB_H_ #include "compiler.h" /** * USB Device Configuration * @{ */ //! Device definition (mandatory) #define USB_DEVICE_VENDOR_ID USB_VID_ATMEL #define USB_DEVICE_PRODUCT_ID USB_PID_ATMEL_AVR_HIDKEYBOARD #define USB_DEVICE_MAJOR_VERSION 1 #define USB_DEVICE_MINOR_VERSION 0 #define USB_DEVICE_POWER 100 // Consumption on Vbus line (mA) #define USB_DEVICE_ATTR \ (USB_CONFIG_ATTR_REMOTE_WAKEUP|USB_CONFIG_ATTR_SELF_POWERED) // (USB_CONFIG_ATTR_REMOTE_WAKEUP|USB_CONFIG_ATTR_BUS_POWERED) // (USB_CONFIG_ATTR_SELF_POWERED) // (USB_CONFIG_ATTR_BUS_POWERED) //! USB Device string definitions (Optional) #define USB_DEVICE_MANUFACTURE_NAME "ALVAND" #define USB_DEVICE_PRODUCT_NAME "HAMEDAN" // #define USB_DEVICE_SERIAL_NAME "12...EF" /** * Device speeds support * @{ */ //! To define a Low speed device //#define USB_DEVICE_LOW_SPEED //! To authorize the High speed #if (UC3A3||UC3A4) //#define USB_DEVICE_HS_SUPPORT #endif //@} /** * USB Device Callbacks definitions (Optional) * @{ */ #define UDC_VBUS_EVENT(b_vbus_high) main_vbus_action(b_vbus_high) #define UDC_SOF_EVENT() main_sof_action() #define UDC_SUSPEND_EVENT() main_suspend_action() #define UDC_RESUME_EVENT() main_resume_action() //! Mandatory when USB_DEVICE_ATTR authorizes remote wakeup feature #define UDC_REMOTEWAKEUP_ENABLE() main_remotewakeup_enable() #define UDC_REMOTEWAKEUP_DISABLE() main_remotewakeup_disable() //! When a extra string descriptor must be supported //! other than manufacturer, product and serial string // #define UDC_GET_EXTRA_STRING() //@} //@} /** * USB Interface Configuration * @{ */ /** * Configuration of HID Keyboard interface * @{ */ //! Interface callback definition #define UDI_HID_KBD_ENABLE_EXT() main_kbd_enable() #define UDI_HID_KBD_DISABLE_EXT() main_kbd_disable() #define UDI_HID_KBD_CHANGE_LED(value) ui_kbd_led(value) //@} //@} /** * USB Device Driver Configuration * @{ */ //@} //! The includes of classes and other headers must be done at the end of this file to avoid compile error #include "udi_hid_kbd_conf.h" #include "main.h" #include "ui.h" #endif // _CONF_USB_H_ and this is my main.c file: /** * \file * * \brief Main functions for Keyboard example * * Copyright (c) 2009-2011 Atmel Corporation. All rights reserved. * * \asf_license_start * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * 3. The name of Atmel may not be used to endorse or promote products derived * from this software without specific prior written permission. * * 4. This software may only be redistributed and used in connection with an Atmel * AVR product. * * THIS SOFTWARE IS PROVIDED BY ATMEL "AS IS" AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE * EXPRESSLY AND SPECIFICALLY DISCLAIMED. IN NO EVENT SHALL ATMEL BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * \asf_license_stop * */ #include "compiler.h" #include "preprocessor.h" #include "board.h" #include "gpio.h" #include "sysclk.h" #include "sleepmgr.h" #include "conf_usb.h" #include "udc.h" #include "udd.h" #include "ui.h" //volatile static bool main_b_kbd_enable = false; volatile static bool main_b_kbd_enable = true; /*! \brief Main function. Execution starts here. */ int main(void) { irq_initialize_vectors(); cpu_irq_enable(); // Initialize the sleep manager sleepmgr_init(); sysclk_init(); board_init(); ui_init(); ui_powerdown(); ui_wakeup_enable(); volatile uint32_t freq = sysclk_get_cpu_hz(); freq ++; LED_Toggle(LED3); // Start USB stack to authorize VBus monitoring udc_start(); //udc_attach(); if (!udc_include_vbus_monitoring()) { // VBUS monitoring is not available on this product // thereby VBUS has to be considered as present main_vbus_action(true); } // The main loop manages only the power mode // because the USB management is done by interrupt while (true) { #ifdef USB_DEVICE_LOW_SPEED // No USB "Keep a live" interrupt available in low speed // to scan keyboard interface then use main loop if (main_b_kbd_enable) { static uint16_t virtual_sof_sub = 0; if (700 == virtual_sof_sub++) { virtual_sof_sub = 0; static uint16_t virtual_sof = 0; ui_process(virtual_sof++); } } #else sleepmgr_enter_sleep(); #endif } } void main_vbus_action(bool b_high) { //if (b_high) { // Attach USB Device udc_attach(); //} else { // VBUS not present //udc_detach(); //} } void main_suspend_action(void) { ui_powerdown(); } void main_resume_action(void) { ui_wakeup(); } void main_sof_action(void) { if (!main_b_kbd_enable) return; ui_process(udd_get_frame_number()); } void main_remotewakeup_enable(void) { ui_wakeup_enable(); } void main_remotewakeup_disable(void) { ui_wakeup_disable(); } bool main_kbd_enable(void) { main_b_kbd_enable = true; return true; } void main_kbd_disable(void) { main_b_kbd_enable = false; } /** * \mainpage ASF USB Device HID Keyboard * * \section intro Introduction * This example shows how to implement a USB Device HID Keyboard * on Atmel MCU with USB module. * The application note AVR4903 provides information about this implementation. * * \section startup Startup * The example uses the buttons or sensors available on the board * to simulate a standard keyboard. * After loading firmware, connect the board (EVKxx,XPlain,...) to the USB Host. * When connected to a USB host system this application provides a keyboard application * in the Unix/Mac/Windows operating systems. * This example uses the native HID driver for these operating systems. * * \copydoc UI * * \section example About example * * The example uses the following module groups: * - Basic modules: * Startup, board, clock, interrupt, power management * - USB Device stack and HID modules: * <br>services/usb/ * <br>services/usb/udc/ * <br>services/usb/class/hid/ * <br>services/usb/class/hid/keyboard/ * - Specific implementation: * - main.c, * <br>initializes clock * <br>initializes interrupt * <br>manages UI * - specific implementation for each target "./examples/product_board/": * - conf_foo.h configuration of each module * - ui.c implement of user's interface (buttons, leds) */
  22. Dashboard - Notifications

    Hi all, Would you be able to tell me how I can send Notifications on the Notifications tile on the Dashboard page of the Pineapple firmware.? Many thanks
  23. Naked Ducky + Twin Duck

    Hi, i am trying to run different payloads on different keypresses(capslock, numlock); I would usually go for the Naked Duck way but I am trying to run different batch files depending on what key is pressed(and for that I need the mass storage to be loaded). Is there any way to combine these things? Or any way to run different batch files stored on the ducky at different keypresses?
  24. running windows 10 with nano tethered, am getting bulletins and the firmware search found the new version however it sits. have attempted almost 10 times to get it to load.
  25. Questions about PineAP

    Hello, Ive been using my nano for a few days now, and I ran across a small problem. After I activate PineAP Daemon, and click save, and after its running, attempt to select any of the log boxes or "allow associations" and click save it will de-select itself and wont activate. Any idea on what the problem is? Not being able to allow associations is crippling to my nano. fyi I haven't changed any default config settings. Thanks in advance.
×