-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't seem to be running after flash #12
Comments
Are you using the UPDuino v1 or v2? Can you paste the exact Do you see anything on the serial port? The default example program will output 'hello, world' once a second at 9600 baud 8N1. I don't have an UPDuino to test on, the support for it was contributed by someone else. I'll double check the current master branch on my iCEBreaker when I get home though, as that does use the same FPGA. |
I'm using an upduino v2.0 Picom is using this: Building with
The following output results:
Green LED comes on to say that it's flashed but nothing on serial and no other leds are blinking or any sign on life. This is the output of the serial
Thanks for your help. |
Not completely sure about this, but I think the upduino board config in icicle is for an upduino v1. I don't know if the v1 pinout is compatible with v2. I'll investigate further tonight. |
If you’re referring to the Upduino patches that I pushed last year: that’s for a v2.0. Tom |
Looking at the PCF file and comparing it to the pinout/PCF here: https://github.com/osresearch/up5k#schematics-and-pinout https://github.com/osresearch/up5k/blob/master/upduino_v2.pcf I think it won't work out of the box with the serial or on-board RGB LED. uart_rx/tx are currently set to pin 12 and 21, which are GPIOs, so by default the serial port will only work with an external FTDI cable and not the on-board FTDI chip. I think the serial could be adjusted to work with the on-board FTDI chip, but as it uses the same FTDI channel as the SPI flash you'd need to:
As for the LEDs, it looks like those are also currently all configured to use GPIOs. You could try hooking some of your own LEDs up to those pins or testing the pins with a multimeter. Alternatively, as it looks like the upduino has an on-board RGB LED, you could try changing some of the LED pins to the R, G and B pins (39, 40 and 41) in the |
Yep switching to RAM, using the internal UART and setting CS to high allowed me to get UART outputting, but I'm not sure why it wouldn't work when using the SPI flash? I had the CP2102 connected to the pins listed in the board definition file previously but when I hooked it up to the oscilloscope I was just getting clock jitter. |
hmm, it'd be interesting to know if it works with the CP2102 but without the SPI flash enabled, as that'd narrow the cause down to definitely being the SPI flash. |
I'm a bit late to the party but this might help others with an Upduino v2.0. I tested using a logic analyzer and external serial cable on pins 12/21; as mentioned above, the onboard FTDI and USB are slightly harder to use, if only because the USB port doesn't always show up on Linux until the port is re-plugged for me. With the configuration currently in the tree I can't get it to boot properly. The RX/TX lines remain high and the led pins are stuck at 0b00000001 as far as I can tell. However by setting
For reference, I build and flash with I'm not quite sure what is up with the flash, but I also don't know enough about what and how it is even used here to debug it; if there is any info I can help provide with little experiments let me know. |
When using a CP2102 with an upduino after flashing it doesn't appear to be doing anything, no leds are blinking or anything I'm not sure what I'm doing wrong, I've tried flashing a few versions but so far no dice. I've tried setting to different pins and such but none seem to respond.
The text was updated successfully, but these errors were encountered: