Hey all.
I'm having a problem with transitioning to EDK 6.1 with a custom OPB peripheral.
I started out with EDK 3.2/ISE 5.2 with a custom OPB peripheral in a Microblaze system on a V2 with a well populated OPB bus. That system works fine, but we have new hardware and need to transistion. I'm moving to EDK 6.1/ISE 6.1 with a V2Pro/PPC system with the same OPB peripheral.
The new system has a PLB->OPB bridge and on the OPB bridge is 3 OPB UART Lites and the custom OPB peripheral. The PPC is running a simple "hello world" type program. The program runs fine without the custom core connected. With the core connected and not accessed, the OPB bus resets after any of the UARTS tries to spit out more than 16 characters at a time.
The custom core started out using opb_ipif_ssp0_v1_00_a, then I upgraded it to v1_00_b. Both exhibited the same behavior. It isn't connected to drive to any resets and only the OPB bus resets. Not the PLB. When I address the peripheral with more than 16 addresses in a row or more than
16 access to the same address, there doesn't seem to be any OPB bus resets.Is there a transition guide somewhere that I missed?
What I haven't tried/am planning to try:
1) Go back to a Microblaze system but on the V2Pro. 2) Downgrade to EDK 3.2/ISE 5.2 and use the V2Pro. (bit of a pain, this one). 3) Port the OPB Peripheral to PLB.I'm just trolling to make sure I didn't miss anything obvious.
Thanks!
--Carlos V.