AMC FMC Carrier AFC issueshttps://ohwr.org/project/afc/issues2021-02-25T12:18:41Zhttps://ohwr.org/project/afc/issues/170[Testing] FMC Connectors2021-02-25T12:18:41ZMikolaj Sowinski[Testing] FMC Connectors* Power supply
* LA, HA, HB connectivity
* PRSNT_M2C
* PG_C2M
* PG_M2C
* VADJ level negotiation with MMC (was this ever implemented?)
Clocking, I2C, JTAG and MGT links are suggested to be reported in respective issues.AFC v4.0https://ohwr.org/project/afc/issues/173[Testing] Clocking system2021-02-25T12:18:41ZMikolaj Sowinski[Testing] Clocking systemLots of variations here... But let's try do our best:
* TCLKx and FCLK
* FPGA_CLKx
* RTM clocks
* MGT clocks
* FMC clocs
* WR oscillatorsAFC v4.0https://ohwr.org/project/afc/issues/174[Testing] RTM Connector2021-02-25T12:18:41ZMikolaj Sowinski[Testing] RTM Connector* Power supplies
* LVDS lines
* I2C
* RTM PS#
Clocking, I2C, JTAG and MGT links are suggested to be reported in respective issues.AFC v4.0https://ohwr.org/project/afc/issues/175[Testing] MLVDS2021-02-25T12:18:41ZMikolaj Sowinski[Testing] MLVDSAMC ports 17-20AFC v4.0https://ohwr.org/project/afc/issues/178AFC v4 Prototype Testing Campaign2021-02-25T12:18:46ZMikolaj SowinskiAFC v4 Prototype Testing CampaignAs manufacturing of the prototypes is in the advanced phase in TechnoSystem and Creotech it is high time to draw a testing campaign. Together with @danielot we've agreed to use OHWR for high-level organization and hardware-related issues.
It is difficult to run the board without MMC, so some aspects of testing will be tightly related to AFCv4 OpenMMC port. It is agreed that @KMacias will make o PR to the [LNLS OpenMMC repo](https://github.com/lnls-dig/openMMC) and a dedicated branch for AFC4 will be created there. All issues related to MMC should be reported to [that repo](https://github.com/lnls-dig/openMMC/issues) (and **not** here).
All involved in testing who wants to contribute to MMC should created their own forks and submit PR to the LNLS repository.
I've created a number of *meta-issues* covering main subsystems of AFC with some ideas of what should be tested. If you find these lists incomplete, please add your positions. It would be great if all involved in testing campaign would report successful results to these meta-issues. For found bugs please create separate issues.
* Power supply #169
* FMC Connectors #170
* MGT Links #171
* DDR Memory #172
* Clocking system #173
* RTM Connector #174
* MLVDS #175
* I2C Subsystem #176
* USB / JTAG #177AFC v4.0https://ohwr.org/project/afc/issues/176[Testing] I2C Subsystem2021-03-16T09:36:58ZMikolaj Sowinski[Testing] I2C Subsystem- [x] TCA9548 MMC
- [x] TCA9548 FPGA
- [ ] INA3221 x3
- [x] LM75 x4
- [ ] MAX6642
- [x] 8V54816ANLG
- [x] AT24MAC602
- [ ] AT24C64D
- [x] MCP79410AFC v4.0https://ohwr.org/project/afc/issues/169[Testing] Power supply2021-03-18T16:23:55ZMikolaj Sowinski[Testing] Power supply- [x] Verify all voltage levels
- [x] Operation from onboard power connector
- [x] Operation from AMC connector
- [ ] Verify VADJ regulation range
- [ ] Verify INA readoutsAFC v4.0https://ohwr.org/project/afc/issues/172[Testing] DDR Memory2021-04-13T12:42:18ZMikolaj Sowinski[Testing] DDR MemoryMIG design with data rate of 1866 MT/sAFC v4.0https://ohwr.org/project/afc/issues/171[Testing] MGT Links2021-04-13T12:51:00ZMikolaj Sowinski[Testing] MGT LinksThere are many variants and we should try to test them all. Xilinx IBERT is proffered, whenever possible use 6.6 Gbps line rate.
* AMC P0-P15
* RTM GTP 0-7
* FMC1 DP0-DP3
* FMC2 DP0-DP3AFC v4.0https://ohwr.org/project/afc/issues/155Evaluate separate 2.5V power supply option for RTM banks2021-06-07T14:24:21ZGustavo BrunoEvaluate separate 2.5V power supply option for RTM banksAs it currently is FMC2 LPC and RTM will only work properly if Vadj is set to 2.5V, as this is needed for both LVDS and LVCMOS signals from the RTM connector (maybe 1.8V in some corner case). An option to prevent this would be to have a separate power rail for these banks with an option of mounting a 2.5V supply, separate from Vadj2. This supply could be derived from the 3.3V rail.
I understand this may have a huge impact, and this decision in the end will depend on available space for routing and mounting components. But i believe it is worth registering this limitation and evaluating it before the actual layout is done.AFC v4.0.2https://ohwr.org/project/afc/issues/181Branches and tags2021-06-08T00:37:04ZMikolaj SowinskiBranches and tagsThis issue is to make an agreement on the way manufacturers publish modifications made to satisfy requirements of the PCB manufacturers.
Some ideas:
* main development takes place in master branch
* releases are tagged
* every manufacturer has his own branch originating from the project release (e.g. v4.0.2) and publishes there its modifications
* **every** manufactured commit gets its **own tag** consisting of project release, manufacturer abbreviation and batch id, that is manufacturer specific (e.g. `v4.0.2_ts_batch452` or `v4.0.2_cti_batch199`)
* as modifications will depend on PCB manufacturer, one may want to have several to have several batches for a single project release
* if a manufacturer's modification introduces an upgrade that is not "PCB-house specific", it can be merged to master and generate a new patch release (e.g. 4.0.3)AFC v4.0.2https://ohwr.org/project/afc/issues/182Tag reference on silkscreen2021-06-08T01:36:29ZMikolaj SowinskiTag reference on silkscreenAdd information on production tag (as specified in #181) on the silkscreen.
Questions:
* How such reference should look like? QR?
* Should we include requirement of placing such reference on silkscreen in project README? Or make a manufacturers Wiki page?AFC v4.0.2https://ohwr.org/project/afc/issues/183Variant sticker2021-06-08T01:36:30ZMikolaj SowinskiVariant stickerIt would be great to have a sticker with variant definition on the device.
The question is what should variant definition look like?AFC v4.0.2https://ohwr.org/project/afc/issues/177[Testing] USB / JTAG2021-07-21T13:32:18ZMikolaj Sowinski[Testing] USB / JTAG- [x] JTAG from USB
- [x] JTAG from AMC
- [x] JTAG from connector
- [x] Primary UART
- [x] Secondary UART
- [x] MMC console
- [x] MMC programming via USB
- [x] JTAG to FMC1
- [x] JTAG to FMC2
- [x] JTAG to RTM
- [x] FPGA JTAGAFC v4.0https://ohwr.org/project/afc/issues/196usb - FMC collision2022-10-04T20:20:48ZGrzegorz Kasprowiczusb - FMC collisionmove the USB connector because THT pins collide with FMC panel
![image](/uploads/274a9ff4b667e68d9e1dff2e269c6a3c/image.png)
![image](/uploads/d0497610d10a5ad4cb4addb23041b2b7/image.png)https://ohwr.org/project/afc/issues/197LED - misalignement with lightpipe2023-08-28T10:00:13ZJakub MoskwaLED - misalignement with lightpipeMove LED 1,8mm towards inside of the PCB.
![image](/uploads/230302c63649a04b0c247092cfbee1c2/image.png)
![image](/uploads/546f8215b08a0d88e64429c426a20b73/image.png)