View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000011 | IDE Simulator | [All Projects] General | public | 2021-06-24 08:50 | 2021-07-21 13:29 |
| Reporter | smoobandit | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0000011: Crystalfontz Display does not initiate on boot - if another USB device is connected. | ||||
| Description | As indicated in the summary, I am running the CFA633 Crystalfontz display. I am connecting via USB to USB1 on the PCB. The display and the PCB both have their own 5v power supply from the same PSU. On boot, the display activates as the power comes on. It shows the Crystalfontz start screen: "Crystalfontz 633 USB: h2.1,u2v2" It does not show the Tattiebogle start screen. it does not matter how long I leave it powering up, the start screen is still not shown. The PCB does detect the Crystalfontz screen. If I putty into USB0 from my PC and run status, I get this: "USB0: device mode; high speed; driver: CDC serial USB1: host mode; full speed; driver: Crystalfontz LCD SD card: Error (1) Uptime: 37 seconds Simulated drive: closed Audio: Idle - track 1 / disk time 0:00:00 unavailable>" If I unplug the display from USB1, wait a second or two, and then plug it back in, I get the TB logo, and: "IDE Simulator Version 3.10" the 'status' command still gives me: "USB0: device mode; high speed; driver: CDC serial USB1: host mode; full speed; driver: Crystalfontz LCD SD card: Error (1) Uptime: 191 seconds Simulated drive: closed Audio: Idle - track 1 / disk time 0:00:00 unavailable>" The same behaviour can be seen if a USB thumbdrive is connected to USB0 instead of the cable to the PC. It makes no difference if the Crystalfontz is on USB0 or USB1. I have not tried a card in the SD slot. What DOES make a difference is if the ONLY USB device attached is the Crystalfontz display. If it is the only thing connected (to either USB0 or USB1), the display will boot with the CF message, and then cycle to the TB splash screen, and then the normal operating screen. At that point you can connect the USB thumbdrive, and you are off to the races. So, what seems to be happening is that if there are TWO USB devices attached, the CF display is not initiated by the PCB on first boot. With the current firmware there are only two solutions: Unplug and replug the CF display into the PC after boot Don't start the PCB with a USB drive attached. Neither are ideal, as I want to mount the whole system inside a case, with USB access at the rear. | ||||
| Steps To Reproduce | Connect PCB to CF display on USB0 or USB1 Do not connect anything else. Power both separately Turn on system PCB and CF display operate as intended. Turn off system Connect USB drive to other USB0/1 port on PCB Turn on system CF display does not initiate as expected. | ||||
| Tags | No tags attached. | ||||
|
|
Definitely can reproduce, I hadn't noticed as it doesn't seem to happen when the debugger is attached, though I did manage to get a crash once it was running that's hopefully related. |
|
|
Hopefully found it, a bug in NXP's USB stack. Please try attached build that seems to fix the issue for me. fix-lcd-usb.fw (272,640 bytes) |
|
|
yep, that did it. cheers. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-06-24 08:50 | smoobandit | New Issue | |
| 2021-06-26 06:11 | colin | Note Added: 0000082 | |
| 2021-06-28 04:40 | colin | File Added: fix-lcd-usb.fw | |
| 2021-06-28 04:40 | colin | Note Added: 0000087 | |
| 2021-07-21 13:29 | smoobandit | Note Added: 0000094 |
