08:16:23 INFO : Memory regions updated for context APU
08:18:17 INFO : Disconnected from the channel tcfchan#3.
08:18:18 INFO : System reset is completed.
08:18:20 INFO : FPGA configured successfully with bitstream "C:/____test/Hello_World15p1/Hello_World15p1.sdk/Hello_World15p1_wrapper_hw_platform_0/Hello_World15p1_wrapper.bit"
08:18:22 INFO : ps7_init is completed.
08:18:22 INFO : ps7_post_config is completed.
>>>>>>>>> Vivado DRC report shows 1 violation ...
An IO Bus FIXED_IO_mio[53:0] with more than one IO standard is found. Components associated with this bus are: FIXED_IO_mio[53:16] of IOStandard LVCMOS18;
>>>>> Board Rev is 'B', as in 'PB200-279 Rev B', 2013
>>>> Okay , Just tried EEEEVrything---Vivado 2015.1, Vivado 2018.2, now Vivado 2017.4(I bought my Zybo B3 and installed 2017.4) Diligent can you comment as in I should have avoided Zybo 1st gen B3 and bought instead (2nd or 3rd gen) ? NO ERRORS, JUST THE uart1 Hello World prints nothing, JTAG jumper setting on JP5(while on JP5 setting=QSP1, the terminal prints nicely. Tells me my host computer is not blocking UART1) I see all other Hello World 'solutions' are never consistent--I've review so many on different years/Vivado Revs, so A Diligent comment tat is a consistent debug on their side I feel is warranted---no just 'read the manual', or 'check board file revs'---this HelloWorld on just PS is so barebones it glaring when NO ERRORS, and a glaringly quiet terminal
Ok it works now(Yes, I did take knock out the IOStandard LVCMOS18 DRC, setting correct IOStandard via XDC but do change in problem), but after unnecessary, adhoc hacking--I have not seen this solution in forums before and it was my last try after despair at spending $ on my Zybo: I will not state my solution, because it was a hack after much wasted time: Diligent may know my solution(it being quite simple) and has not made it known despite being very simple, whereas I have seen many other solves/failed attempts that are so much all over the place. I did rinse and repeat my solve does ensure its repeatable....
Question
ZyboB3
My Retired Zybo(B3) Hello World demo, as is in SDK, won't print. Otherwise, no errors.
>>>>>>>>>> Using Vivado 15.1...., SDK log shows ….
source C:/____test/Hello_World15p1/Hello_World15p1.sdk/Hello_World15p1_wrapper_hw_platform_0/ps7_init.tcl
targets -set -filter {name =~"APU" && jtag_cable_name =~ "Digilent Zybo 210279A79095A"} -index 0
rst -system
targets -set -filter {jtag_cable_name =~ "Digilent Zybo 210279A79095A" && level==0} -index 1
fpga -file C:/____test/Hello_World15p1/Hello_World15p1.sdk/Hello_World15p1_wrapper_hw_platform_0/Hello_World15p1_wrapper.bit
targets -set -filter {name =~"APU" && jtag_cable_name =~ "Digilent Zybo 210279A79095A"} -index 0
ps7_init
ps7_post_config
----------------End of Script----------------
08:16:23 INFO : Memory regions updated for context APU
08:18:17 INFO : Disconnected from the channel tcfchan#3.
08:18:18 INFO : System reset is completed.
08:18:20 INFO : FPGA configured successfully with bitstream "C:/____test/Hello_World15p1/Hello_World15p1.sdk/Hello_World15p1_wrapper_hw_platform_0/Hello_World15p1_wrapper.bit"
08:18:22 INFO : ps7_init is completed.
08:18:22 INFO : ps7_post_config is completed.
>>>>>>>>> Vivado DRC report shows 1 violation ...
An IO Bus FIXED_IO_mio[53:0] with more than one IO standard is found. Components associated with this bus are: FIXED_IO_mio[53:16] of IOStandard LVCMOS18;
>>>>> Board Rev is 'B', as in 'PB200-279 Rev B', 2013
>>>> Okay , Just tried EEEEVrything---Vivado 2015.1, Vivado 2018.2, now Vivado 2017.4(I bought my Zybo B3 and installed 2017.4) Diligent can you comment as in I should have avoided Zybo 1st gen B3 and bought instead (2nd or 3rd gen) ? NO ERRORS, JUST THE uart1 Hello World prints nothing, JTAG jumper setting on JP5(while on JP5 setting=QSP1, the terminal prints nicely. Tells me my host computer is not blocking UART1) I see all other Hello World 'solutions' are never consistent--I've review so many on different years/Vivado Revs, so A Diligent comment tat is a consistent debug on their side I feel is warranted---no just 'read the manual', or 'check board file revs'---this HelloWorld on just PS is so barebones it glaring when NO ERRORS, and a glaringly quiet terminal
Ok it works now(Yes, I did take knock out the IOStandard LVCMOS18 DRC, setting correct IOStandard via XDC but do change in problem), but after unnecessary, adhoc hacking--I have not seen this solution in forums before and it was my last try after despair at spending $ on my Zybo: I will not state my solution, because it was a hack after much wasted time: Diligent may know my solution(it being quite simple) and has not made it known despite being very simple, whereas I have seen many other solves/failed attempts that are so much all over the place. I did rinse and repeat my solve does ensure its repeatable....
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.