Base Config
(extra)
Compiled again with EEPROM enabled, confirmed eeprom.dat was created, so Marlin appears to be booting.
Expected behavior: Should be able to issue basic commands, eg M119, and get response.
Actual behavior: No Comms
Ive tried this against two PC's, ruling out (i hope) software issues.
Ive also comparatively loaded Smoothieware onto the board to check for board issues. Smootie runs fine and connects fine.
This is using the as current branch of bugfix-2.0.x, no changes to the base Configuration as stated.
I am experiencing exactly the same symptoms described here.
I can see the firmware.bin is being renamed to firmware.cur so I assume that all checks out?
The default configs were recently changed to disable the secondary serial port, please set Serial port 1 to the usb connection (-1) or re-enable the secondary port.
This is where a Max7219 LED Matrix would come in handy. They are under $2 on eBay including shipping. (And they look cool even if you don't have a problem).
@Roxy-3D What for? Showing boot status?
@p3p That sorted it.
Thats a rather non-intuitive change though. Given the majority of off the shelf hardware is going to have an intended port for serial comms as a primary, would it not make sense to have Serial Port 1 be defined by default at the board level, and overridable instead of a main config item?
would it not make sense to have Serial Port 1 be defined by default at the board level, and overridable instead of a main config item?
It could be so. There would need to be an option not just to override it but also to disable it from the configuration too, for cases where users know it won't ever be used.
I'm currently facing the exact same behavior with my Re-Arm board.
After a reset I can establish a USB host Connection within the first 30 - 60 seconds and even send and receive GCode commands. As soon as the virtual com port appears in the device Manager and the SD Card appears in the file Explorer the USB host Connection is dropped and a reconnect is not possible reconnect. The host reporting that the COM port is not existing.
On the other Hand I a reset reboot is performd and I'm waiting until the SD appears in the file Explorer and try to connect through host Software same error as COM Port is not existing.
I'm using default config with just
#define MOTHERBOARD BOARD_RAMPS_14_RE_ARM_EFB
and
#define SERIAL_PORT -1
@adamnock still having this issue?
Nope, that was all sorted.
My only issue now is my Re-arm blew up because im an idiot.
Probably not a Marlin config flag to fix that
i have the same issue now whit the usb connection over MacOS (the pc more near at printer)
i have configured the unit like @oakdesign and the wiki say (http://marlinfw.org/docs/basics/install_rearm.html)
when open the pronterface and i try connect with the unit. the connection is OK. but any command inserted is recognized as Unknown, include the internal commands launched from pronterface iself

the printer works iself over the LCD
the configuration files
greetings
I tried your two config giles with the latest bugfix_2.0.x and had problems.
I never saw the symptoms you reported. What I did see was the PC complaining about an unrecognized USB device. The USB port appears to come up properly and then die.
I then switched to a virgin configuration, changed serial port to -1 and change the motherboard to RE_ARM. That worked.
It appears that you've run acros some combination of config options that is causing problems.
Please open a new issue for this problem. Please include all the info you've posted here.
I never saw the symptoms you reported. What I did see was the PC complaining about an unrecognized USB device. The USB port appears to come up properly and then die.
I then switched to a virgin configuration, changed serial port to -1 and change the motherboard to RE_ARM. That worked.
Same issue with Re-Arm with no shield. Trying to compile clear configuration - all(serial port and SD) works fine.
I began to turn on the options one by one, and the board hung again after I changed TEMP_SENSOR_BED from 0 to 1.
@Bob-the-Kuhn @syurev
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.