repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 28. January 2015 10:20 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 30. January 2015 08:04 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 30. January 2015 09:25 |
Registrierungsdatum: 9 Jahre zuvor Beiträge: 1.610 |
Quote
Chriss
sobald ich den EEPROM aktiviere (EEPROM_MODE <> 0) hängt sich die Firmware beim Start auf (Display bleibt leer; wenn ich mit dem Repetier Host verbinde erscheint die Meldung "x Befehle warten"). Deaktiviere ich in dieser Situation die SD Card (SDSUPPORT 0) klappt der Start und alles (bis auf die SD Card) läuft wie gewünscht.
Deaktiviere ich den EEPROM (EEPROM_MODE >0; meist 1 oder 2) und aktiviere die SD Card (SDSUPPORT 1) klappt auch dies...
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 30. January 2015 09:41 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 30. January 2015 12:03 |
Registrierungsdatum: 9 Jahre zuvor Beiträge: 1.610 |
if (USE_CONFIGURATION_BAUD_RATE) { // Used if eeprom gets unusable baud rate set and communication wont work at all. if(HAL::eprGetInt32(EPR_BAUDRATE) != BAUDRATE) { HAL::eprSetInt32(EPR_BAUDRATE,BAUDRATE); baudrate = BAUDRATE; uint8_t newcheck = computeChecksum(); if(newcheck != HAL::eprGetByte(EPR_INTEGRITY_BYTE)) HAL::eprSetByte(EPR_INTEGRITY_BYTE,newcheck); } Com::printFLN(PSTR("EEprom baud rate restored from configuration.")); Com::printFLN(PSTR("RECOMPILE WITH USE_CONFIGURATION_BAUD_RATE == 0 to alter baud rate via EEPROM")); }Reine Vermutung!
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 30. January 2015 14:36 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 06. February 2015 04:06 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
V:\avrdude>avrdude -c usbasp -p m2560 -U lock:w:0x3F:m -U efuse:w:0xFD:m -U hfuse:w:0xD8:m -U lfuse: w:0xFF:m -U flash:w:Repetier.cpp.hex avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.03s avrdude: Device signature = 0x1e9801 avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option. avrdude: erasing chip avrdude: reading input file "0x3F" avrdude: writing lock (1 bytes): Writing | ################################################## | 100% 0.01s avrdude: 1 bytes of lock written avrdude: verifying lock memory against 0x3F: avrdude: load data lock data from input file 0x3F: avrdude: input file 0x3F contains 1 bytes avrdude: reading on-chip lock data: Reading | ################################################## | 100% 0.01s avrdude: verifying ... avrdude: 1 bytes of lock verified avrdude: reading input file "0xFD" avrdude: writing efuse (1 bytes): Writing | ################################################## | 100% 0.01s avrdude: 1 bytes of efuse written avrdude: verifying efuse memory against 0xFD: avrdude: load data efuse data from input file 0xFD: avrdude: input file 0xFD contains 1 bytes avrdude: reading on-chip efuse data: Reading | ################################################## | 100% 0.01s avrdude: verifying ... avrdude: 1 bytes of efuse verified avrdude: reading input file "0xD8" avrdude: writing hfuse (1 bytes): Writing | ################################################## | 100% 0.01s avrdude: 1 bytes of hfuse written avrdude: verifying hfuse memory against 0xD8: avrdude: load data hfuse data from input file 0xD8: avrdude: input file 0xD8 contains 1 bytes avrdude: reading on-chip hfuse data: Reading | ################################################## | 100% -0.00s avrdude: verifying ... avrdude: 1 bytes of hfuse verified avrdude: reading input file "0xFF" avrdude: writing lfuse (1 bytes): Writing | ################################################## | 100% -0.00s avrdude: 1 bytes of lfuse written avrdude: verifying lfuse memory against 0xFF: avrdude: load data lfuse data from input file 0xFF: avrdude: input file 0xFF contains 1 bytes avrdude: reading on-chip lfuse data: Reading | ################################################## | 100% 0.01s avrdude: verifying ... avrdude: 1 bytes of lfuse verified avrdude: reading input file "Repetier.cpp.hex" avrdude: input file Repetier.cpp.hex auto detected as Intel Hex avrdude: writing flash (144874 bytes): Writing | ################################################## | 100% 243.84s avrdude: 144874 bytes of flash written avrdude: verifying flash memory against Repetier.cpp.hex: avrdude: load data flash data from input file Repetier.cpp.hex: avrdude: input file Repetier.cpp.hex auto detected as Intel Hex avrdude: input file Repetier.cpp.hex contains 144874 bytes avrdude: reading on-chip flash data: Reading | ################################################## | 100% 224.82s avrdude: verifying ... avrdude: verification error, first mismatch at byte 0x0000 0x0c != 0xff avrdude: verification error; content mismatch avrdude: safemode: Fuses OK avrdude done. Thank you.
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 06. February 2015 09:47 |
Registrierungsdatum: 9 Jahre zuvor Beiträge: 1.610 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 06. February 2015 10:01 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 06. February 2015 14:57 |
Registrierungsdatum: 9 Jahre zuvor Beiträge: 1.610 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 06. February 2015 15:23 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 02. September 2015 10:35 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
#if PiBot_V_1_4==true || PiBot_V_1_6==true /* not valid for v1.4 !!! #define BEEPER_PIN 37 #define UI_DISPLAY_RS_PIN 16 #define UI_DISPLAY_RW_PIN -1 #define UI_DISPLAY_ENABLE_PIN 17 #define UI_DISPLAY_D0_PIN 23 #define UI_DISPLAY_D1_PIN 25 #define UI_DISPLAY_D2_PIN 27 #define UI_DISPLAY_D3_PIN 29 #define UI_DISPLAY_D4_PIN 23 #define UI_DISPLAY_D5_PIN 25 #define UI_DISPLAY_D6_PIN 27 #define UI_DISPLAY_D7_PIN 29 #define UI_ENCODER_A 33 #define UI_ENCODER_B 31 #define UI_ENCODER_CLICK 35 #define UI_RESET_PIN 41 #define UI_DELAYPERCHAR 50 #define UI_BUTTON_OK 4 #define UI_BUTTON_NEXT 6 #define UI_BUTTON_PREVIOUS 5 #define UI_BUTTON_BACK 11 #define UI_BUTTON_SD_PRINT 42 */ // #define BEEPER_PIN 31 #define BEEPER_PIN 8 // only for silent testing without beeps #define UI_DISPLAY_RS_PIN 45 #define UI_DISPLAY_RW_PIN -1 #define UI_DISPLAY_ENABLE_PIN 44 #define UI_DISPLAY_D0_PIN 43 #define UI_DISPLAY_D1_PIN 42 #define UI_DISPLAY_D2_PIN 19 #define UI_DISPLAY_D3_PIN 18 #define UI_DISPLAY_D4_PIN 43 #define UI_DISPLAY_D5_PIN 42 #define UI_DISPLAY_D6_PIN 19 #define UI_DISPLAY_D7_PIN 18 #define UI_ENCODER_A 61 #define UI_ENCODER_B 62 #define UI_ENCODER_CLICK 63 #define UI_RESET_PIN 28 #define UI_DELAYPERCHAR 50 #define UI_BUTTON_OK 49 #define UI_BUTTON_NEXT 48 #define UI_BUTTON_PREVIOUS 47 #define UI_BUTTON_BACK 46 #define UI_BUTTON_SD_PRINT 29 #endifACHTUNG: die Belegung passt NICHT für Version 1.6 der PiBot Hardware! PiBot_V_1_4 wird in der aktuellen pins.h nicht mehr gesetzt!
avrdude: verification error, first mismatch at byte 0x0000 0x0c != 0x01 avrdude: verification error; content mismatch
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 02. September 2015 12:49 |
Registrierungsdatum: 9 Jahre zuvor Beiträge: 1.610 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 02. September 2015 14:02 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |
Re: repetier 0.92 | PiBot v1.4 | SD Card & EEPROM => Fehler 03. September 2015 07:57 |
Registrierungsdatum: 10 Jahre zuvor Beiträge: 27 |