Quantcast
Channel: Reprap Forum - Repetier
Viewing all articles
Browse latest Browse all 1321

cannot connect with EEPROM enabled (version 0.92x) (no replies)

$
0
0
I'm suspecting the baudrate is incorrectly stored in the EEPROM, when enabled. Or is it just me?

If I recompile with "#define EEPROM_MODE 0", I can connect (with terminal, Repetier host, pronterface, etc.), otherwise no matter what baud rate I try, I can just see the transmit LED flashing every second (sending the "wait" I assume), but nothing in the terminal. And nothing works.

I tried recompiling with "#define USE_CONFIGURATION_BAUD_RATE 1", but nothing changed.

I am programming my Gen7 custom board with JTAGICE3, so I have the luxury of being able to read the EEPROM content, so I experimented a bit.

When EEPROM_MODE is 0, the EEPROM is blank (full of FF's), as expected.

I then recompiled with EEPROM_MODE 1, and BAUDRATE 115200, and got this in the eeprom.

:1000000001FFFFF27A1D44F27A1D44F27A1D44008A
. . .
:10006000FFFFFFFFFFFFFFFFF40C00FF0000444312

Then I recompiled with EEPROM_MODE 2, and BAUDRATE 250000 and got this:

:1000000002FFFFF27A1D44F27A1D44F27A1D440089
. . .
:10006000FFFFFFFFFFFFFFFFF50C00FF0000444311

I only listed the lines with differences.

Youcan see, that the mode changed from 1 to 2 in the first line, and byte 0x0068 from 0xf4 to 0xf5.

The two baud rates in hex format are:

115200 = 0x1c200
250000 = 0x3d090

Nowhere near to anything containing 0xf4 or 0xf5. Or am I lost somewhere completely?

Anyway, the bottom line is that if the EEPROM is enabled, I cannot connect to the board with antything.

Thanks,
Miki.

Viewing all articles
Browse latest Browse all 1321

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>