Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #47466

    Regdone
    Participant

    Hello,

    I built 2 Opensprinkler with pcb 2.3a by myself. One with Atmega 644 as “Hardware Version 2.2” an the other one with Atmega 1284 as “Hardware Version 2.3”. I flashed the correct Firmware, all OK.
    I wonder why I can use 2.2 without SD-Card, but 2.3 is no way to use without card. 2.3 says on display “Error Code: 0x2D” when I boot 2.3 without card. Why this? In Software it is defined so by using Atmega 1284:

    #if defined(__AVR_ATmega1284P__) || defined(__AVR_ATmega1284__)
        if(!status.has_sd) {
          lcd.setCursor(0, 0);
          lcd_print_pgm(PSTR("Error Code: 0x2D"));
          while(1){}
        }
    #endif

    Whats the cause of this? Why must 1284 have a card and 644 don’t so?

    Second Problem: I wanna use older SD-Cards, but small Cards e.g. 1 GB don’t match. In 2.2 it wouldn’t be initialized, no card logo on display, on 2.3 it stops booting with “Connecting” on display. 4-GB-Card works fine.
    Is this a problem in firmware? Support OS SDHC only?

    Thanks for your answers!

    #47741

    Ray
    Keymaster

    Because features available on firmware 2.1.7 requires SD card. If you don’t want these features, you can go back to firmware 2.1.6 which does not require SD card.

    If it stops booting at ‘Connecting’ message, it doesn’t sound like a SD card problem — it will get stuck at Error Code: 0x2D if SD card is not detected.

    Also, since your built the circuit yourself, it’s hard for us to tell if there is any soldering/reflow related issues.

    #47785

    Regdone
    Participant

    Hi Ray,

    thanks for your answer. No, the cardproblem isn’t a problem of bad soldering. Thats a problem of card compatibility. Other cards (2…4 GB) works fine, but 1 GB don’t work in Opensprinkler and hang booting with “Connecting…”. Without card, displays 0x2D, thats right.
    But no problem, I use other card and works fine.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.