MiniZed Hardware Design - Recent Threads

About Programming and Obtaining Configuration Files for IRPS5401MTRPBF

sdimen — Tue, 25 Mar 2025 09:54:30 GMT

Hi everyone,

I am designing a custom carrier board and plan to use Infineon's IRPS5401MTRPBF PMIC with the UltraZed-EG SOM. I understand that the device needs to be programmed to meet specific power requirements.

Programming Method: Programming of the IRPS5401MTRPBF requires the use of the PowIRCenter tool provided by Infineon. The tool allows the user to configure the PMIC's output voltage, startup sequence, and other parameters according to specific application requirements.

Configuration File Obtaining: If you want to use the same configuration as the UltraZed-EG SOM carrier board, you can contact the relevant designer or community member to obtain the PowIRCenter configuration file for the design. In previous discussions, the designer has indicated that such a configuration file is available.

Pre-programmed device procurement: Typically, the IRPS5401MTRPBF is supplied in an unprogrammed state. If you need a pre-programmed device, you may need to contact a vendor or use a programming service. For example, Avnet offers a device programming service that can be customized to your needs.

Arduino expansion shield ports

jimmi1 — Thu, 07 Nov 2024 15:08:52 GMT

Can the arduino expansion ports be driven directly from the programmable logic or is it necessary to pass through the PS?

GPIO can be used as input/output port?

koseiyokoyama — Wed, 19 Jun 2024 02:37:13 GMT

I am trying to comunicate with Temp/Humid module DHT11
However data pin should be pull up to 3.3 but while my RTL trying to comunicate with DHT11 throgh IO13 pin, Data line pull down to GND.
if GPIO can be inout port, then any one know how?

My RTL working fine in simulation with Vivado

Can MInized drive stepper Motor driver ULN2003A?

koseiyokoyama — Fri, 07 Jun 2024 01:14:14 GMT

Can Minized drive Stepper motor driver (one in ELGOO kit) ?

Motor driver uses TI ULN2003A IC to dirve stepper motor (28BY-J-48)

I wrote RTL to drive stepper motor driver from Minized GPIO,

but it does not seems GPIO drive stepper motor driver

thank for your help

Minized System generator hardware in the loop

jimmi1 — Sat, 01 Jun 2024 18:22:41 GMT

I would like to ask if anyone has experience or has managed to achieve hardware in the loop simulations using the minized board in matlabs system generator. I'm not sure if it is possible to enable the JTAG interface and whether or not board definition files exist for system generator.

Thanks.

minized : how to define master clock in xdc for RTL

koseiyokoyama — Thu, 02 May 2024 06:10:35 GMT

I designed 7seg display driver in Verilog.
in xdc file, I define my clock as follows

set_property -dict {PACKAGE_PIN L12 IOSTANDARD LVCMOS33} [get_ports clk];

create_clock -add -name sysclk -period 20.000 -waveform {0.000 10.000} [get_ports clk];

L12 is WRCC Pin

and clk is my clock input pin in my RTL design

it does not seem clock is clocking..

Am I missing something?

Block design is not used.

Updates of some Minized Resource Links

rscasny — Mon, 17 Jul 2023 21:07:58 GMT

I just learned today that some of our links were out of date. Here is the updated list:

Documentation/Reference Design

http://avnet.me/MINIZED_E14

VirtualBox Installation 2021.1

http://avnet.me/minized

www.xilinx.com/zynq-7000

www.xilinx.com/Vitis

www.xilinx.com/vivado

Forums/Discussion

http://avnet.me/minized_forum

Data transfer from PL to PS DDR

Waqas — Wed, 12 Jul 2023 05:40:32 GMT

We are using MiniZed Hardware in our project. We want to move some data from PL side to PS DDR through the control of PL side. We are using AXI datamover IP to transfer data from PL to PS DDR. However, we are not able to see any data in PS DDR after PL has provided data on Streaming Interface of AXI datamover IP.

Can anyone suggest solution to this problem??

MiniZed XDC Files - Where can I find them or how to create them

kas.lewis — Wed, 19 Oct 2022 19:02:31 GMT

Hello,

I'm trying to get back to my FPGA board (Minized) but I'm having trouble as I'm trying to find an XDC file for the board or somewhere I can learn how to create one for all its peripherals. I have found THIS, but it does not include the LEDs or the push buttons on a quick check. Also is there a need to include any information for clocks or timing in this file?

Thanks

Kas

FT2232H

snaseermohamed — Wed, 18 May 2022 05:00:09 GMT

good morning,

I am new to ft2232H. I have tried to implement serial communication using MPSSE command in loop back mode. I tried to run code given for serial communication in AN_135
FTDI MPSSE Basics in loop back mode. But it gives

" Error - MPSSE receive buffer should have the looped-back data ".

I tried both the way 1. using command " byOutputBuffer[dwNumBytesToSend++] = 0x84; " to internally connect TDI/DO PIN and TDO/DI .

2. externally also connected both the pins.

i want the solution for this. Please correct me if I made any mistakes as soon as possible.

#include<stdio.h>
#include<stdlib.h>
#include<string.h>
#include "ftd2xx.h"
#include<direct.h>
#include<stdbool.h>
int main()
{
// -----------------------------------------------------------
// Variables
// -----------------------------------------------------------
FT_HANDLE ftHandle; // Handle of the FTDI device
FT_STATUS ftStatus; // Result of each D2XX call
DWORD dwNumDevs; // The number of devices
unsigned int uiDevIndex = 0xF; // The device in the list that we'll use
BYTE byOutputBuffer[8]; // Buffer to hold MPSSE commands and data
// to be sent to the FT2232H
BYTE byInputBuffer[8]; // Buffer to hold data read from the FT2232H
DWORD dwCount = 0; // General loop index
DWORD dwNumBytesToSend = 0; // Index to the output buffer
DWORD dwNumBytesSent = 0; // Count of actual bytes sent - used with FT_Write
DWORD dwNumBytesToRead = 0; // Number of bytes available to read
// in the driver's input buffer
DWORD dwNumBytesRead = 0; // Count of actual bytes read - used with FT_Read
DWORD dwClockDivisor = 0xFFFF; // Value of clock divisor, SCL Frequency =
// 60/((1+0x05DB)*2) (MHz) = 1Mhz
// -----------------------------------------------------------
// Does an FTDI device exist?
// -----------------------------------------------------------
printf("Checking for FTDI devices...\n");
ftStatus = FT_CreateDeviceInfoList(&dwNumDevs);
// Get the number of FTDI devices
if (ftStatus != FT_OK) // Did the command execute OK?
{
printf("Error in getting the number of devices\n");
return 1; // Exit with error
}
if (dwNumDevs < 1) // Exit if we don't see any
{
printf("There are no FTDI devices installed\n");
return 1; // Exit with error
}
printf("%lu FTDI devices found \
- the count includes individual ports on a single chip\n", dwNumDevs);
// -----------------------------------------------------------
// Open the port - For this application note, we'll assume the first device is a
// FT2232H or FT4232H. Further checks can be made against the device
// descriptions, locations, serial numbers, etc. before opening the port.
// -----------------------------------------------------------
printf("\nAssume first device has the MPSSE and open it...\n");
ftStatus = FT_Open(0, &ftHandle);
if (ftStatus != FT_OK)
{
printf("Open Failed with error %lu\n", ftStatus);
return 1; // Exit with error
}


// Configure port parameters
printf("\nConfiguring port for MPSSE use...\n");
ftStatus |= FT_ResetDevice(ftHandle);
//Reset USB device
//Purge USB receive buffer first by reading out all old data from FT2232H receive buffer
ftStatus |= FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in the FT2232H
// receive buffer
if ((ftStatus == FT_OK) && (dwNumBytesToRead > 0))
FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
//Read out the data from FT2232H receive buffer
ftStatus |= FT_SetUSBParameters(ftHandle, 65536, 65535);
//Set USB request transfer sizes to 64K
ftStatus |= FT_SetChars(ftHandle, false, 0, false, 0);
//Disable event and error characters
ftStatus |= FT_SetTimeouts(ftHandle, 0, 5000);
//Sets the read and write timeouts in milliseconds
ftStatus |= FT_SetLatencyTimer(ftHandle, 1);
//Set the latency timer to 1mS (default is 16mS)
ftStatus |= FT_SetFlowControl(ftHandle, FT_FLOW_RTS_CTS, 0x00, 0x00);
//Turn on flow control to synchronize IN requests
ftStatus |= FT_SetBitMode(ftHandle, 0x0, 0x00);
//Reset controller
ftStatus |= FT_SetBitMode(ftHandle, 0x0, 0x02);
//Enable MPSSE mode
if (ftStatus != FT_OK)
{
printf("Error in initializing the MPSSE %lu\n", ftStatus);
FT_Close(ftHandle);
return 1; // Exit with error
}
Sleep(50); // Wait for all the USB stuff to complete and work
// Enable internal loop-back
byOutputBuffer[dwNumBytesToSend++] = 0x84;
// Enable loopback
ftStatus = FT_Write(ftHandle, byOutputBuffer, \
dwNumBytesToSend, &dwNumBytesSent);
// Send off the loopback command
dwNumBytesToSend = 0; // Reset output buffer pointer
// Check the receive buffer - it should be empty
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// the FT2232H receive buffer
if (dwNumBytesToRead != 0)
{
printf("Error - MPSSE receive buffer should be empty %lu\n", ftStatus);
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
// -----------------------------------------------------------
// Synchronize the MPSSE by sending a bogus opcode (0xAB),
// The MPSSE will respond with "Bad Command" (0xFA) followed by
// the bogus opcode itself.
// -----------------------------------------------------------
byOutputBuffer[dwNumBytesToSend++] = 0xAB;
//Add bogus command ‘0xAB’ to the queue
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the BAD command
dwNumBytesToSend = 0; // Reset output buffer pointer
do
{
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in the device input buffer
} while ((dwNumBytesToRead == 0) && (ftStatus == FT_OK));
//or Timeout
bool bCommandEchod = false;
ftStatus = FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
//Read out the data from input buffer
for (dwCount = 0; dwCount < dwNumBytesRead - 1; dwCount++)
//Check if Bad command and echo command are received
{
if ((byInputBuffer[dwCount] == 0xFA) && (byInputBuffer[dwCount+1] == 0xAB))
{
bCommandEchod = true;
break;
}
}
if (bCommandEchod == false)
{
printf("Error in synchronizing the MPSSE\n");
FT_Close(ftHandle);
return 1; // Exit with error
}
// Disable internal loop-back
//byOutputBuffer[dwNumBytesToSend++] = 0x85;
// Disable loopback
//ftStatus = FT_Write(ftHandle, byOutputBuffer,\
//dwNumBytesToSend, &dwNumBytesSent);
// Send off the loopback command
dwNumBytesToSend = 0; // Reset output buffer pointer
// Check the receive buffer - it should be empty
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in
// the FT2232H receive buffer
if (dwNumBytesToRead != 0)
{
printf("Error - MPSSE receive buffer should be empty\n %lu ", ftStatus);
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}

//MPSSE Setup
// -----------------------------------------------------------
// Configure the MPSSE settings for JTAG
// Multple commands can be sent to the MPSSE with one FT_Write
// -----------------------------------------------------------
dwNumBytesToSend = 0; // Start with a fresh index
// Set up the Hi-Speed specific commands for the FTx232H
byOutputBuffer[dwNumBytesToSend++] = 0x8A;
// Use 60MHz master clock (disable divide by 5)
byOutputBuffer[dwNumBytesToSend++] = 0x97;
// Turn off adaptive clocking (may be needed for ARM)
byOutputBuffer[dwNumBytesToSend++] = 0x8D;
// Disable three-phase clocking
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the HS-specific commands
dwNumBytesToSend = 0; // Reset output buffer pointer
// Set TCK frequency
// TCK = 60MHz /((1 + [(1 +0xValueH*256) OR 0xValueL])*2)
byOutputBuffer[dwNumBytesToSend++] = '\x86';
// Command to set clock divisor
byOutputBuffer[dwNumBytesToSend++] = dwClockDivisor & 0xFF;
// Set 0xValueL of clock divisor
byOutputBuffer[dwNumBytesToSend++] = (dwClockDivisor >> 8) & 0xFF;
// Set 0xValueH of clock divisor
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the clock divisor commands
dwNumBytesToSend = 0; // Reset output buffer pointer
// Set initial states of the MPSSE interface
// - low byte, both pin directions and output values
// Pin name Signal Direction Config Initial State Config
// ADBUS0 TCK/SK output 1 high 1
// ADBUS1 TDI/DO output 1 low 0
// ADBUS2 TDO/DI input 0 0
// ADBUS3 TMS/CS output 1 high 1
// ADBUS4 GPIOL0 output 1 low 0
// ADBUS5 GPIOL1 output 1 low 0
// ADBUS6 GPIOL2 output 1 high 1
// ADBUS7 GPIOL3 output 1 high 1
byOutputBuffer[dwNumBytesToSend++] = 0x80;
// Configure data bits low-byte of MPSSE port
byOutputBuffer[dwNumBytesToSend++] = 0xC9;
// Initial state config above
byOutputBuffer[dwNumBytesToSend++] = 0xFB;
// Direction config above
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the low GPIO config commands
dwNumBytesToSend = 0; // Reset output buffer pointer
// Note that since the data in subsequent sections will be clocked on the rising edge, the
// inital clock state of high is selected. Clocks will be generated as high-low-high.
// For example, in this case, data changes on the rising edge to give it enough time
// to have it available at the device, which will accept data *into* the target device
// on the falling edge.
// Set initial states of the MPSSE interface
// - high byte, both pin directions and output values
// Pin name Signal Direction Config Initial State Config
// ACBUS0 GPIOH0 input 0 0
// ACBUS1 GPIOH1 input 0 0
// ACBUS2 GPIOH2 input 0 0
// ACBUS3 GPIOH3 input 0 0
// ACBUS4 GPIOH4 input 0 0
// ACBUS5 GPIOH5 input 0 0
// ACBUS6 GPIOH6 input 0 0
// ACBUS7 GPIOH7 input 0 0
byOutputBuffer[dwNumBytesToSend++] = 0x82;
// Configure data bits low-byte of MPSSE port
byOutputBuffer[dwNumBytesToSend++] = 0x00;
// Initial state config above
byOutputBuffer[dwNumBytesToSend++] = 0x00;
// Direction config above
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the high GPIO config commands
dwNumBytesToSend = 0; // Reset output buffer pointer
for(dwCount = 0; dwCount < 8; dwCount++)
{ // Clear out the input and output buffers
byInputBuffer[dwCount] = 0x00;
byOutputBuffer[dwCount] = 0x00;
}
// Data Transmit, no receive
dwNumBytesToSend = 0;
byOutputBuffer[dwNumBytesToSend++] = 0x84;
// Enable loopback
ftStatus = FT_Write(ftHandle, byOutputBuffer, \
dwNumBytesToSend, &dwNumBytesSent);
//sleep(2);
dwNumBytesToSend = 0;
byOutputBuffer[dwNumBytesToSend++] = 0x10;
// Output on rising clock, no input
// MSB first, clock a number of bytes out
byOutputBuffer[dwNumBytesToSend++] = 0x01; // Length L
byOutputBuffer[dwNumBytesToSend++] = 0x00; // Length H
// Length = 0x0001 + 1
byOutputBuffer[dwNumBytesToSend++] = 0xA5;
byOutputBuffer[dwNumBytesToSend++] = 0x0F;
// Data = 0xA50F
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the command
dwNumBytesToSend = 0; // Reset output buffer pointer
Sleep(2); // Wait for data to be transmitted and status
// to be returned by the device driver
// - see latency timer above
// Check the receive buffer - it should be empty
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in
// the FT2232H receive buffer
// It should be zero since there was
// no data clocked *in*
FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
if (dwNumBytesToRead != 0)
{
printf("Error - MPSSE receive buffer should be empty %lu\n", ftStatus);
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
printf("Press <Enter> to continue\n");
getchar(); // wait for a carriage return
// Now repeat the transmission with the send and receive op-code in place of transmit-only
// Data Transmit, with receive
byOutputBuffer[dwNumBytesToSend++] = 0x34;
// Output on rising clock, input on falling clock
// MSB first, clock a number of bytes out
byOutputBuffer[dwNumBytesToSend++] = 0x01; // Length L
byOutputBuffer[dwNumBytesToSend++] = 0x00; // Length H
// Length = 0x0001 + 1
byOutputBuffer[dwNumBytesToSend++] = 0xA5;
byOutputBuffer[dwNumBytesToSend++] = 0x0F;
// Data = 0xA50F
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the command
dwNumBytesToSend = 0; // Reset output buffer pointer
Sleep(2); // Wait for data to be transmitted and status
// to be returned by the device driver
// - see latency timer above
// Check the receive buffer - it should contain the looped-back data
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in
// the FT2232H receive buffer
// It should be zero since there was
// no data clocked *in*
FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
// The input buffer should contain the same number of bytes as those output
//printf("\n size:%d",dwNumBytesToRead);
if (dwNumBytesToRead != 2)
{
printf("Error - MPSSE receive buffer should have the looped-back data\n");
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
printf("The correct number of bytes have been received\n");
// Check to be sure it's the same.
for(dwCount = 0; dwCount <= dwNumBytesRead - 1; dwCount++)
{
if (byInputBuffer[dwCount] != byOutputBuffer[dwCount + 3])
// Output data begins at location 3,
// after the opcode and length
{
printf("Error - Data received does not match data output\n");
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
}
printf("The input data matches the output data\n");
printf("Press <Enter> to continue\n");
getchar(); // wait for a carriage return
// Clear the buffers
for(dwCount = 0; dwCount < 8; dwCount++)
{
byInputBuffer[dwCount] = 0x00;
byOutputBuffer[dwCount] = 0x00;
}
FT_Close(ftHandle);
return 0;
}

FT2232H

snaseermohamed — Tue, 17 May 2022 05:18:44 GMT

good morning,

" Error - MPSSE receive buffer should have the looped-back data ".

I tried both the way 1. using command " byOutputBuffer[dwNumBytesToSend++] = 0x84; " to internally connect TDI/DO PIN and TDO/DI .

2. externally also connected both the pins.

i want the solution for this. Please correct me if I made any mistakes as soon as possible.

int main()
{
// -----------------------------------------------------------
// Variables
// -----------------------------------------------------------
FT_HANDLE ftHandle; // Handle of the FTDI device
FT_STATUS ftStatus; // Result of each D2XX call
DWORD dwNumDevs; // The number of devices
unsigned int uiDevIndex = 0xF; // The device in the list that we'll use
BYTE byOutputBuffer[8]; // Buffer to hold MPSSE commands and data
// to be sent to the FT2232H
BYTE byInputBuffer[8]; // Buffer to hold data read from the FT2232H
DWORD dwCount = 0; // General loop index
DWORD dwNumBytesToSend = 0; // Index to the output buffer
DWORD dwNumBytesSent = 0; // Count of actual bytes sent - used with FT_Write
DWORD dwNumBytesToRead = 0; // Number of bytes available to read
// in the driver's input buffer
DWORD dwNumBytesRead = 0; // Count of actual bytes read - used with FT_Read
DWORD dwClockDivisor = 0xFFFF; // Value of clock divisor, SCL Frequency =
// 60/((1+0x05DB)*2) (MHz) = 1Mhz
// -----------------------------------------------------------
// Does an FTDI device exist?
// -----------------------------------------------------------
printf("Checking for FTDI devices...\n");
ftStatus = FT_CreateDeviceInfoList(&dwNumDevs);
// Get the number of FTDI devices
if (ftStatus != FT_OK) // Did the command execute OK?
{
printf("Error in getting the number of devices\n");
return 1; // Exit with error
}
if (dwNumDevs < 1) // Exit if we don't see any
{
printf("There are no FTDI devices installed\n");
return 1; // Exit with error
}
printf("%lu FTDI devices found \
- the count includes individual ports on a single chip\n", dwNumDevs);
// -----------------------------------------------------------
// Open the port - For this application note, we'll assume the first device is a
// FT2232H or FT4232H. Further checks can be made against the device
// descriptions, locations, serial numbers, etc. before opening the port.
// -----------------------------------------------------------
printf("\nAssume first device has the MPSSE and open it...\n");
ftStatus = FT_Open(0, &ftHandle);
if (ftStatus != FT_OK)
{
printf("Open Failed with error %lu\n", ftStatus);
return 1; // Exit with error
}

// Configure port parameters
printf("\nConfiguring port for MPSSE use...\n");
ftStatus |= FT_ResetDevice(ftHandle);
//Reset USB device
//Purge USB receive buffer first by reading out all old data from FT2232H receive buffer
ftStatus |= FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in the FT2232H
// receive buffer
if ((ftStatus == FT_OK) && (dwNumBytesToRead > 0))
FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
//Read out the data from FT2232H receive buffer
ftStatus |= FT_SetUSBParameters(ftHandle, 65536, 65535);
//Set USB request transfer sizes to 64K
ftStatus |= FT_SetChars(ftHandle, false, 0, false, 0);
//Disable event and error characters
ftStatus |= FT_SetTimeouts(ftHandle, 0, 5000);
//Sets the read and write timeouts in milliseconds
ftStatus |= FT_SetLatencyTimer(ftHandle, 1);
//Set the latency timer to 1mS (default is 16mS)
ftStatus |= FT_SetFlowControl(ftHandle, FT_FLOW_RTS_CTS, 0x00, 0x00);
//Turn on flow control to synchronize IN requests
ftStatus |= FT_SetBitMode(ftHandle, 0x0, 0x00);
//Reset controller
ftStatus |= FT_SetBitMode(ftHandle, 0x0, 0x02);
//Enable MPSSE mode
if (ftStatus != FT_OK)
{
printf("Error in initializing the MPSSE %lu\n", ftStatus);
FT_Close(ftHandle);
return 1; // Exit with error
}
Sleep(50); // Wait for all the USB stuff to complete and work
// Enable internal loop-back
byOutputBuffer[dwNumBytesToSend++] = 0x84;
// Enable loopback
ftStatus = FT_Write(ftHandle, byOutputBuffer, \
dwNumBytesToSend, &dwNumBytesSent);
// Send off the loopback command
dwNumBytesToSend = 0; // Reset output buffer pointer
// Check the receive buffer - it should be empty
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// the FT2232H receive buffer
if (dwNumBytesToRead != 0)
{
printf("Error - MPSSE receive buffer should be empty\n", ftStatus);
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
// -----------------------------------------------------------
// Synchronize the MPSSE by sending a bogus opcode (0xAB),
// The MPSSE will respond with "Bad Command" (0xFA) followed by
// the bogus opcode itself.
// -----------------------------------------------------------
byOutputBuffer[dwNumBytesToSend++] = 0xAB;
//Add bogus command ‘0xAB’ to the queue
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the BAD command
dwNumBytesToSend = 0; // Reset output buffer pointer
do
{
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in the device input buffer
} while ((dwNumBytesToRead == 0) && (ftStatus == FT_OK));
//or Timeout
bool bCommandEchod = false;
ftStatus = FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
//Read out the data from input buffer
for (dwCount = 0; dwCount < dwNumBytesRead - 1; dwCount++)
//Check if Bad command and echo command are received
{
if ((byInputBuffer[dwCount] == 0xFA) && (byInputBuffer[dwCount+1] == 0xAB))
{
bCommandEchod = true;
break;
}
}
if (bCommandEchod == false)
{
printf("Error in synchronizing the MPSSE\n");
FT_Close(ftHandle);
return 1; // Exit with error
}

dwNumBytesToSend = 0; // Reset output buffer pointer
// Check the receive buffer - it should be empty
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in
// the FT2232H receive buffer
if (dwNumBytesToRead != 0)
{
printf("Error - MPSSE receive buffer should be empty\n", ftStatus);
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}

//MPSSE Setup
// -----------------------------------------------------------
// Configure the MPSSE settings for JTAG
// Multple commands can be sent to the MPSSE with one FT_Write
// -----------------------------------------------------------
dwNumBytesToSend = 0; // Start with a fresh index
// Set up the Hi-Speed specific commands for the FTx232H
byOutputBuffer[dwNumBytesToSend++] = 0x8A;
// Use 60MHz master clock (disable divide by 5)
byOutputBuffer[dwNumBytesToSend++] = 0x97;
// Turn off adaptive clocking (may be needed for ARM)
byOutputBuffer[dwNumBytesToSend++] = 0x8D;
// Disable three-phase clocking
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the HS-specific commands
dwNumBytesToSend = 0; // Reset output buffer pointer
// Set TCK frequency
// TCK = 60MHz /((1 + [(1 +0xValueH*256) OR 0xValueL])*2)
byOutputBuffer[dwNumBytesToSend++] = '\x86';
// Command to set clock divisor
byOutputBuffer[dwNumBytesToSend++] = dwClockDivisor & 0xFF;
// Set 0xValueL of clock divisor
byOutputBuffer[dwNumBytesToSend++] = (dwClockDivisor >> 8) & 0xFF;
// Set 0xValueH of clock divisor
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the clock divisor commands
dwNumBytesToSend = 0; // Reset output buffer pointer
// Set initial states of the MPSSE interface
// - low byte, both pin directions and output values
// Pin name Signal Direction Config Initial State Config
// ADBUS0 TCK/SK output 1 high 1
// ADBUS1 TDI/DO output 1 low 0
// ADBUS2 TDO/DI input 0 0
// ADBUS3 TMS/CS output 1 high 1
// ADBUS4 GPIOL0 output 1 low 0
// ADBUS5 GPIOL1 output 1 low 0
// ADBUS6 GPIOL2 output 1 high 1
// ADBUS7 GPIOL3 output 1 high 1
byOutputBuffer[dwNumBytesToSend++] = 0x80;
// Configure data bits low-byte of MPSSE port
byOutputBuffer[dwNumBytesToSend++] = 0xC9;
// Initial state config above
byOutputBuffer[dwNumBytesToSend++] = 0xFB;
// Direction config above
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the low GPIO config commands
dwNumBytesToSend = 0; // Reset output buffer pointer
// Note that since the data in subsequent sections will be clocked on the rising edge, the
// inital clock state of high is selected. Clocks will be generated as high-low-high.
// For example, in this case, data changes on the rising edge to give it enough time
// to have it available at the device, which will accept data *into* the target device
// on the falling edge.
// Set initial states of the MPSSE interface
// - high byte, both pin directions and output values
// Pin name Signal Direction Config Initial State Config
// ACBUS0 GPIOH0 input 0 0
// ACBUS1 GPIOH1 input 0 0
// ACBUS2 GPIOH2 input 0 0
// ACBUS3 GPIOH3 input 0 0
// ACBUS4 GPIOH4 input 0 0
// ACBUS5 GPIOH5 input 0 0
// ACBUS6 GPIOH6 input 0 0
// ACBUS7 GPIOH7 input 0 0
byOutputBuffer[dwNumBytesToSend++] = 0x82;
// Configure data bits low-byte of MPSSE port
byOutputBuffer[dwNumBytesToSend++] = 0x00;
// Initial state config above
byOutputBuffer[dwNumBytesToSend++] = 0x00;
// Direction config above
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the high GPIO config commands
dwNumBytesToSend = 0; // Reset output buffer pointer
for(dwCount = 0; dwCount < 8; dwCount++)
{ // Clear out the input and output buffers
byInputBuffer[dwCount] = 0x00;
byOutputBuffer[dwCount] = 0x00;
}
// Data Transmit, no receive
dwNumBytesToSend = 0;
byOutputBuffer[dwNumBytesToSend++] = 0x84;
// Enable loopback
ftStatus = FT_Write(ftHandle, byOutputBuffer, \
dwNumBytesToSend, &dwNumBytesSent);
//sleep(2);
dwNumBytesToSend = 0;
byOutputBuffer[dwNumBytesToSend++] = 0x10;
// Output on rising clock, no input
// MSB first, clock a number of bytes out
byOutputBuffer[dwNumBytesToSend++] = 0x01; // Length L
byOutputBuffer[dwNumBytesToSend++] = 0x00; // Length H
// Length = 0x0001 + 1
byOutputBuffer[dwNumBytesToSend++] = 0xA5;
byOutputBuffer[dwNumBytesToSend++] = 0x0F;
// Data = 0xA50F
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the command
dwNumBytesToSend = 0; // Reset output buffer pointer
Sleep(2); // Wait for data to be transmitted and status
// to be returned by the device driver
// - see latency timer above
// Check the receive buffer - it should be empty
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in
// the FT2232H receive buffer
// It should be zero since there was
// no data clocked *in*
FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
if (dwNumBytesToRead != 0)
{
printf("Error - MPSSE receive buffer should be empty\n", ftStatus);
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
printf("Press <Enter> to continue\n");
getchar(); // wait for a carriage return
// Now repeat the transmission with the send and receive op-code in place of transmit-only
// Data Transmit, with receive
byOutputBuffer[dwNumBytesToSend++] = 0x34;
// Output on rising clock, input on falling clock
// MSB first, clock a number of bytes out
byOutputBuffer[dwNumBytesToSend++] = 0x01; // Length L
byOutputBuffer[dwNumBytesToSend++] = 0x00; // Length H
// Length = 0x0001 + 1
byOutputBuffer[dwNumBytesToSend++] = 0xA5;
byOutputBuffer[dwNumBytesToSend++] = 0x0F;
// Data = 0xA50F
ftStatus = FT_Write(ftHandle, byOutputBuffer, dwNumBytesToSend, &dwNumBytesSent);
// Send off the command
dwNumBytesToSend = 0; // Reset output buffer pointer
Sleep(2); // Wait for data to be transmitted and status
// to be returned by the device driver
// - see latency timer above
// Check the receive buffer - it should contain the looped-back data
ftStatus = FT_GetQueueStatus(ftHandle, &dwNumBytesToRead);
// Get the number of bytes in
// the FT2232H receive buffer
// It should be zero since there was
// no data clocked *in*
FT_Read(ftHandle, &byInputBuffer, dwNumBytesToRead, &dwNumBytesRead);
// The input buffer should contain the same number of bytes as those output
printf("\n size:%d",dwNumBytesToRead);
if (dwNumBytesToRead != 2)
{
printf("Error - MPSSE receive buffer should have the looped-back data\n");
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
printf("The correct number of bytes have been received\n");
// Check to be sure it's the same.
for(dwCount = 0; dwCount <= dwNumBytesRead - 1; dwCount++)
{
if (byInputBuffer[dwCount] != byOutputBuffer[dwCount + 3])
// Output data begins at location 3,
// after the opcode and length
{
printf("Error - Data received does not match data output\n");
FT_SetBitMode(ftHandle, 0x0, 0x00);
// Reset the port to disable MPSSE
FT_Close(ftHandle); // Close the USB port
return 1; // Exit with error
}
}
printf("The input data matches the output data\n");
printf("Press <Enter> to continue\n");
getchar(); // wait for a carriage return
// Clear the buffers
for(dwCount = 0; dwCount < 8; dwCount++)
{
byInputBuffer[dwCount] = 0x00;
byOutputBuffer[dwCount] = 0x00;
}
FT_Close(ftHandle);
return 0;
}

BSP 2019.1 BSP MiniZed

iaguilar — Mon, 11 Apr 2022 21:46:15 GMT

I am getting a critical warring regarding wireless_mgr. The file is not in the build. Where can I find that file?

error when running avnet make_minized_sbc_base.sh script

NealRayYoung — Thu, 07 Apr 2022 23:23:25 GMT

I'm having trouble getting the minized_sbc_base petalinux project to build.

Here are the steps I performed:

I cloned the three repos:

$ cd ~

$ mkdir -p git/avnet

$ cd git/avnet

$ git clone https://github.com/avnet/bdf.git

$ git clone https://github.com/avnet/hdl.git

$ git clone https://github.com/avnet/petalinux.git

And checked out the branches (bdf is ok at master):

$ cd hdl

$ git checkout 2021.2

$ cd ../petalinux

$ git checkout 2021.2

$ cd scripts

$ ./make_minized_sbc_base.sh

It creates and builds the vivado project just fine. Then is copies the .bit and .xsa as expected.

Here is the output of the script:

Importing hardware definition minized_sbc_base.xsa from HDL project folder ...

Importing hardware bitstream minized_sbc_base_wrapper.bit from HDL project folder...

[INFO] Sourcing buildtools
INFO: Getting hardware description...
INFO: Renaming minized_sbc_base.xsa to system.xsa
[INFO] Generating Kconfig for project
[INFO] Silentconfig project
[INFO] Extracting yocto SDK to components/yocto. This may take time!
[INFO] Sourcing build environment
[INFO] Generating kconfig for Rootfs
[INFO] Silentconfig rootfs
[INFO] Generating plnxtool conf
[INFO] Adding user layers
[INFO] Generating workspace directory

Patching PetaLinux project config ...

Tag 2021p2_minized_sbc_20210426_105325 not found. Cloning 2021.2 branch instead.

***WARNING: This may result in build mismatch!***

Stop (<ctrl>-c) in the next 5 seconds if this is not OK.

Pause here for 5 seconds
Clone meta-avnet layer and checkout 2021.2 branch

Cloning into 'project-spec/meta-avnet'...
remote: Enumerating objects: 2704, done.
remote: Counting objects: 100% (1266/1266), done.
remote: Compressing objects: 100% (685/685), done.
remote: Total 2704 (delta 721), reused 947 (delta 504), pack-reused 1438
Receiving objects: 100% (2704/2704), 7.76 MiB | 5.85 MiB/s, done.
Resolving deltas: 100% (1326/1326), done.

Setting cache (sstate and download) path (/home/dev/test/petalinux/projects/cache) ...

[INFO] Sourcing buildtools
[INFO] Silentconfig project
[INFO] Sourcing build environment
[INFO] Generating kconfig for Rootfs
[INFO] Silentconfig rootfs
[INFO] Generating plnxtool conf
[INFO] Adding user layers
[INFO] Generating workspace directory
[INFO] Successfully configured project

Modifying project config for INITRD boot support...

[INFO] Sourcing buildtools
[INFO] Silentconfig project
[INFO] Sourcing build environment
[INFO] Generating kconfig for Rootfs
[INFO] Silentconfig rootfs
[INFO] Generating plnxtool conf
[INFO] Generating workspace directory
[INFO] Successfully configured project

Building project...

[INFO] Sourcing buildtools
[INFO] Building avnet-image-full
[INFO] Sourcing build environment
[INFO] Generating workspace directory
INFO: bitbake avnet-image-full
NOTE: Started PRServer with DBfile: /home/dev/test/petalinux/projects/minized_sbc_base_2021_2/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 39873, PID: 2629570
Loading cache: 100% | | ETA: --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100% |##########################################################################| Time: 0:03:32
Parsing of 3513 .bb files complete (0 cached, 3513 parsed). 5170 targets, 278 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Fetching uninative binary shim file:///home/dev/test/petalinux/projects/minized_sbc_base_2021_2/components/yocto/downloads/uninative/5ec5a9276046e7eceeac749a18b175667384e1f445cd4526300a41404d985a5b/x86_64-nativesdk-libc.tar.xz;sha256sum=5ec5a9276046e7eceeac749a18b175667384e1f445cd4526300a41404d985a5b (will check PREMIRRORS first)
Initialising tasks: 100% |######################################################################################################| Time: 0:00:09
Checking sstate mirror object availability: 100% |###############################################################################################################################| Time: 0:00:47
Sstate summary: Wanted 2138 Found 1662 Missed 476 Current 0 (77% match, 0% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 6336 tasks of which 2845 didn't need to be rerun and all succeeded.
INFO: Failed to copy built images to tftp dir: /tftpboot
[INFO] Successfully built avnet-image-full
[INFO] Sourcing buildtools
INFO: Getting system flash information...
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/zynq_fsbl.elf"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/project-spec/hw-description/minized_sbc_base.bit"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/u-boot.elf"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/system.dtb"
INFO: Generating zynq binary package BOOT.BIN...

****** Xilinx Bootgen v2021.2
**** Build date : Sep 30 2021-06:08:18
** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

[INFO] : Bootimage generated successfully

INFO: Binary is ready.
WARNING: Unable to access the TFTPBOOT folder /tftpboot!!!
WARNING: Skip file copy to TFTPBOOT folder!!!
[INFO] Sourcing buildtools
INFO: Getting system flash information...
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/zynq_fsbl.elf"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/system.bit"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/u-boot.elf"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/system.dtb"
INFO: Generating zynq binary package BOOT.BIN...

****** Xilinx Bootgen v2021.2
**** Build date : Sep 30 2021-06:08:18
** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

[INFO] : Bootimage generated successfully

INFO: Binary is ready.
WARNING: Unable to access the TFTPBOOT folder /tftpboot!!!
WARNING: Skip file copy to TFTPBOOT folder!!!

Modifying project config for INITRD boot support...

[INFO] Sourcing buildtools
[INFO] Silentconfig project
[INFO] Sourcing build environment
[INFO] Generating kconfig for Rootfs
[INFO] Silentconfig rootfs
[INFO] Generating plnxtool conf
[INFO] Generating workspace directory
[INFO] Successfully configured project

Building project...

[INFO] Sourcing buildtools
[INFO] Building avnet-image-full
[INFO] Sourcing build environment
[INFO] Generating workspace directory
INFO: bitbake avnet-image-full
NOTE: Started PRServer with DBfile: /home/dev/test/petalinux/projects/minized_sbc_base_2021_2/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 34731, PID: 144671
Loading cache: 100% | | ETA: --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100% |##########################################################################################################################################################| Time: 0:01:56
Parsing of 3513 .bb files complete (0 cached, 3513 parsed). 5170 targets, 278 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% |#######################################################################################################################################################| Time: 0:00:18
Sstate summary: Wanted 298 Found 251 Missed 47 Current 1825 (84% match, 97% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 6293 tasks of which 5596 didn't need to be rerun and all succeeded.
INFO: Failed to copy built images to tftp dir: /tftpboot
[INFO] Successfully built avnet-image-full
[INFO] Sourcing buildtools
INFO: Getting system flash information...
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/zynq_fsbl.elf"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/project-spec/hw-description/minized_sbc_base.bit"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/u-boot.elf"
INFO: File in BOOT BIN: "/home/dev/test/petalinux/projects/minized_sbc_base_2021_2/images/linux/system.dtb"
INFO: Generating zynq binary package BOOT.BIN...

****** Xilinx Bootgen v2021.2
**** Build date : Sep 30 2021-06:08:18
** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

[INFO] : Bootimage generated successfully

****** Xilinx Bootgen v2021.2
**** Build date : Sep 30 2021-06:08:18
** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

[INFO] : Bootimage generated successfully

INFO: Binary is ready.
WARNING: Unable to access the TFTPBOOT folder /tftpboot!!!
WARNING: Skip file copy to TFTPBOOT folder!!!

Modifying project config for EXT4 boot support...

[INFO] Sourcing buildtools
[INFO] Silentconfig project
[INFO] Sourcing build environment
[INFO] Generating kconfig for Rootfs
[INFO] Silentconfig rootfs
[INFO] Generating plnxtool conf
[INFO] Generating workspace directory
[INFO] Successfully configured project

Building project...

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
ERROR: Failed to build avnet-image-full. Check the /home/dev/test/petalinux/projects/minized_sbc_base_2021_2/build/build.log file for more details...
[INFO] Sourcing buildtools
[INFO] Building avnet-image-full
[INFO] Sourcing build environment
[INFO] Generating workspace directory
INFO: bitbake avnet-image-full
NOTE: Started PRServer with DBfile: /home/dev/test/petalinux/projects/minized_sbc_base_2021_2/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 34819, PID: 216273
Loading cache: 100% |############################################################################################################################################################| Time: 0:00:01
Loaded 5165 entries from dependency cache.
Parsing recipes: 100% |##########################################################################################################################################################| Time: 0:00:01
Parsing of 3513 .bb files complete (3508 cached, 5 parsed). 5170 targets, 278 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'u-boot' (but /home/dev/test/petalinux/projects/minized_sbc_base_2021_2/components/yocto/layers/meta-xilinx/meta-xilinx-bsp/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb DEPENDS on or otherwise requires it)
u-boot was skipped: PREFERRED_PROVIDER_virtual/bootloader set to u-boot-xlnx, not u-boot
ERROR: Required build target 'avnet-image-full' has no buildable providers.
Missing or unbuildable dependency chain was: ['avnet-image-full', 'virtual/boot-bin', 'u-boot']

________________________________________

Since I'm using the stuff directly from the avnet git repo I'm not sure why I'm getting errors and could use a little help in figuring out why I have a "Missing or unbuildable dependency chain was: ['avnet-image-full', 'virtual/boot-bin', 'u-boot']".

Any help would be appreciated.

Thanks.

how can i use and see module on rootfs menuconfig of meta-avnet layer??

ldw — Fri, 25 Mar 2022 09:57:24 GMT

Hello!

i use minized zynq board by minized_sbc_base_2020_2.bsp .. so i build 'petaliux-build -c avnet-image-minimal' .

i hope to use led-brightness module at 'project-spec/meta-avnet/recipes-modules/led-brightness that was already supported on bsp.

but, i command by petalinux-config -c rootfs and enter menu config 'modules -> no modules'

So, is there some command to use not 'meta-user' layer but 'meta-avnet' layer???

when i command petalinux-create -t modules --name test-driver --enable, this module generated at meta-user .. not meta-avnet.

please, let me know .. how can i use meta-avnet layer? why i can't see any ready-maded modules..?

thank you.

How can i use 'meta-avnet' modules on minized_2020.2_bsp ?

ldw — Fri, 25 Mar 2022 01:42:23 GMT

Hello

i use minized zynq board by minized_sbc_base_2020_2.bsp .. so i build 'petaliux-build -c avnet-image-full' .

i hope to use led-brightness module at 'project-spec/meta-avnet/recipes-modules/led-brightness that was already supported ...

but, i command by petalinux-config -c rootfs and enter modules menu -> no modules

So, is there some command to use not 'meta-user' layer but 'meta-avnet' layer???

when i command petalinux-create -t modules --name test-driver --enable, this module generated at meta-user .. not meta-avnet.

please, let me know .. how can i use meta-avnet layer that was supported and made already by minized_sbc_base_2020_2.bsp.

MiniZed Sainsmart relay connection

tanderson — Fri, 11 Mar 2022 12:55:33 GMT

I am driving a Sainsmart 4 Relay Module from MiniZed.

Because it needs 5 volts, I connected JD-VCC to 5v on Arduino Shield of MiniZed.

VCC is connected to 3.3v VCC of MiniZed.

Ground is connected to ground.

IN4 of Sainsmart is connected to an output of MiniZed.

The relay allows a connected module to have its VCC connected/disconnected on K4 of Sainsmart.

All seems to be working well, but I am wondering if 5v of relay could draw too much power. I did not see any specs for 5v on the MiniZed HW users guide.

An alternative would be using an external 5v power supply (breadboard power supply), but so far, the setup appears to work.

I plan on doing some testing of the setup, and I would not want to jeopardize my MiniZed.

Regards,

Todd Anderson

Error at exporting Minized BSP 2020.2 hardware xpr

Sungwoo — Tue, 08 Mar 2022 07:35:43 GMT

When exporting 2020.2 xpr at Vivado, following error comes up.

ERROR: [Common 17-53] User Exception: Specified ip cache dir /home/training/Projects/bsp_build_tests/test_tag/minized_sbc_base/hdl/projects/minized_sbc_base_2020_2/minized_sbc_base.cache/ip does not exist. Unable to copy into Shell.

To replicate, here is steps based on Ubuntu 20.04

~/Downloads$ tar -xf minized_sbc_base_2020_2.tar.gz

$ source ~/petalinux/settings.sh

$ petalinux-create -t project -s ~/Downloads/minized_sbc_base_2020_2.bsp

At Vivado 2020.2, open project at /hardware/minized_sbc_base_2020_2/minized_sbc_base.xpr

Then File/Export/Export Platform, select Next, select Hardware, select include bitstream, select Next, Next, Finish. 
Then above error pops up.



I want to modify the design and export to xsa but the error is blocking. Any advice ?

Macros missing from xparameters.h when using AXI Timer

LTxAlves — Wed, 19 Jan 2022 20:11:25 GMT

Hi!

I needed to use to PWM from the AXI Timer IP. I designed a simple block diagram, exported the hardware to work on it on SDK. Looking at the example given for the PWM using the Timer IP, SDK pointed out some errors with the code. I fixed some by modifying the BSP settings and changing them back. However, I noticed some MACRO definitions were missing in the xparameters.h file, which in turn SDK points out as errors and I have no idea if I can just copy those from another xparameters.h file or what to change in my code/bock design so those definitions appear on my current file.

The block design:

https://imgur.com/a/9qGeMHu

The code:

/******************************************************************************
*
* Copyright (C) 2018 Xilinx, Inc.  All rights reserved.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
* XILINX  BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
* WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
* OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
* SOFTWARE.
*
* Except as contained in this notice, the name of the Xilinx shall not be used
* in advertising or otherwise to promote the sale, use or other dealings in
* this Software without prior written authorization from Xilinx.
*
******************************************************************************/
/*****************************************************************************/
/**
* @file  xtmrctr_pwm_example.c
*
* This file contains a design example using the timer counter driver
* and hardware device using interrupt mode. The example demonstrates
* the use of PWM feature of axi timers. PWM is configured to operate at specific
* duty cycle and after every N cycles the duty cycle is incremented until a
* specific duty cycle is achieved. No software validation of duty cycle is
* undergone in the example.
*
* This example assumes that the interrupt controller is also present as a part
* of the system.
*
*
*
*
* <pre>
* MODIFICATION HISTORY:
*
* Ver   Who  Date	 Changes
* ----- ---- -------- -----------------------------------------------
* 1.00b cjp  03/28/18 First release
*</pre>
******************************************************************************/

/***************************** Include Files *********************************/
#include "xtmrctr.h"
#include "xparameters.h"
#include "xil_exception.h"

#ifdef XPAR_INTC_0_DEVICE_ID
#include "xintc.h"
#include <stdio.h>
#else
#include "xscugic.h"
#include "xil_printf.h"
#endif

/************************** Constant Definitions *****************************/
/*
 * The following constants map to the XPAR parameters created in the
 * xparameters.h file. They are only defined here such that a user can easily
 * change all the needed parameters in one place.
 */
#define TMRCTR_DEVICE_ID        XPAR_TMRCTR_0_DEVICE_ID

#ifdef __MICROBLAZE__
#define TMRCTR_INTERRUPT_ID     XPAR_INTC_0_TMRCTR_0_VEC_ID
#else
#define TMRCTR_INTERRUPT_ID     XPAR_FABRIC_TMRCTR_0_VEC_ID
#endif

#ifdef XPAR_INTC_0_DEVICE_ID
#define INTC_DEVICE_ID          XPAR_INTC_0_DEVICE_ID
#define INTC                    XIntc
#define INTC_HANDLER            XIntc_InterruptHandler
#else
#define INTC_DEVICE_ID          XPAR_SCUGIC_SINGLE_DEVICE_ID
#define INTC                    XScuGic
#define INTC_HANDLER            XScuGic_InterruptHandler
#endif /* XPAR_INTC_0_DEVICE_ID */

#define PWM_PERIOD              500000000    /* PWM period in (500 ms) */
#define TMRCTR_0                0            /* Timer 0 ID */
#define TMRCTR_1                1            /* Timer 1 ID */
#define CYCLE_PER_DUTYCYCLE     10           /* Clock cycles per duty cycle */
#define MAX_DUTYCYCLE           100          /* Max duty cycle */
#define DUTYCYCLE_DIVISOR       4            /* Duty cycle Divisor */
#define WAIT_COUNT              PWM_PERIOD   /* Interrupt wait counter */

/**************************** Type Definitions *******************************/

/***************** Macros (Inline Functions) Definitions *********************/

/************************** Function Prototypes ******************************/
int TmrCtrPwmExample(INTC *IntcInstancePtr, XTmrCtr *InstancePtr, u16 DeviceId,
								u16 IntrId);
static void TimerCounterHandler(void *CallBackRef, u8 TmrCtrNumber);
static int TmrCtrSetupIntrSystem(INTC *IntcInstancePtr, XTmrCtr *InstancePtr,
						u16 DeviceId, u16 IntrId);
static void TmrCtrDisableIntr(INTC *IntcInstancePtr, u16 IntrId);

/************************** Variable Definitions *****************************/
INTC InterruptController;  /* The instance of the Interrupt Controller */
XTmrCtr TimerCounterInst;  /* The instance of the Timer Counter */

/*
 * The following variables are shared between non-interrupt processing and
 * interrupt processing such that they must be global.
 */
static int   PeriodTimerHit = FALSE;
static int   HighTimerHit = FALSE;

/*****************************************************************************/
/**
* This function is the main function of the Tmrctr PWM example.
*
* @param	None.
*
* @return	XST_SUCCESS to indicate success, else XST_FAILURE to indicate a
*		Failure.
*
* @note		None.
*
******************************************************************************/
int main(void)
{
	int Status;

	/* Run the Timer Counter PWM example */
	Status = TmrCtrPwmExample(&InterruptController, &TimerCounterInst,
				  TMRCTR_DEVICE_ID, TMRCTR_INTERRUPT_ID);
	if (Status != XST_SUCCESS) {
		xil_printf("Tmrctr PWM Example Failed\r\n");
		return XST_FAILURE;
	}

	xil_printf("Successfully ran Tmrctr PWM Example\r\n");
	return XST_SUCCESS;
}

/*****************************************************************************/
/**
* This function demonstrates the use of tmrctr PWM APIs.
*
* @param	IntcInstancePtr is a pointer to the Interrupt Controller
*		driver Instance
* @param	TmrCtrInstancePtr is a pointer to the XTmrCtr driver Instance
* @param	DeviceId is the XPAR_<TmrCtr_instance>_DEVICE_ID value from
*		xparameters.h
* @param	IntrId is XPAR_<INTC_instance>_<TmrCtr_instance>_INTERRUPT_INTR
*		value from xparameters.h
*
* @return	XST_SUCCESS if the Test is successful, otherwise XST_FAILURE
*
* @note		none.
*
*****************************************************************************/
int TmrCtrPwmExample(INTC *IntcInstancePtr, XTmrCtr *TmrCtrInstancePtr,
						u16 DeviceId, u16 IntrId)
{
	u8  DutyCycle;
	u8  NoOfCycles;
	u8  Div;
	u32 Period;
	u32 HighTime;
	u64 WaitCount;
	int Status;

	/*
	 * Initialize the timer counter so that it's ready to use,
	 * specify the device ID that is generated in xparameters.h
	 */
	Status = XTmrCtr_Initialize(TmrCtrInstancePtr, DeviceId);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	/*
	 * Perform a self-test to ensure that the hardware was built
	 * correctly. Timer0 is used for self test
	 */
	Status = XTmrCtr_SelfTest(TmrCtrInstancePtr, TMRCTR_0);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	/*
	 * Connect the timer counter to the interrupt subsystem such that
	 * interrupts can occur
	 */
	Status = TmrCtrSetupIntrSystem(IntcInstancePtr, TmrCtrInstancePtr,
							DeviceId, IntrId);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	/*
	 * Setup the handler for the timer counter that will be called from the
	 * interrupt context when the timer expires
	 */
	XTmrCtr_SetHandler(TmrCtrInstancePtr, TimerCounterHandler,
							TmrCtrInstancePtr);

	/* Enable the interrupt of the timer counter */
	XTmrCtr_SetOptions(TmrCtrInstancePtr, TMRCTR_0, XTC_INT_MODE_OPTION);
	XTmrCtr_SetOptions(TmrCtrInstancePtr, TMRCTR_1, XTC_INT_MODE_OPTION);

	/*
	 * We start with the fixed divisor and after every CYCLE_PER_DUTYCYCLE
	 * decrement the divisor by 1, as a result Duty cycle increases
	 * proportionally. This is done until duty cycle is reached upto
	 * MAX_DUTYCYCLE
	 */
	Div = DUTYCYCLE_DIVISOR;

	/* Configure PWM */
	do {
		/* Fail check for 0 divisor */
		if (!Div) {
			Status = XST_FAILURE;
			goto err;
		}

		/* Disable PWM for reconfiguration */
		XTmrCtr_PwmDisable(TmrCtrInstancePtr);

		/* Configure PWM */
		Period = PWM_PERIOD;
		HighTime = PWM_PERIOD / Div--;
		DutyCycle = XTmrCtr_PwmConfigure(TmrCtrInstancePtr, Period,
								HighTime);
		if (Status != XST_SUCCESS) {
			Status = XST_FAILURE;
			goto err;
		}

		xil_printf("PWM Configured for Duty Cycle = %d\r\n", DutyCycle);

		/* Enable PWM */
		XTmrCtr_PwmEnable(TmrCtrInstancePtr);

		NoOfCycles = 0;
		WaitCount = WAIT_COUNT;
		while (NoOfCycles < CYCLE_PER_DUTYCYCLE) {
			if (PeriodTimerHit == TRUE && HighTimerHit == TRUE) {
				PeriodTimerHit = FALSE;
				HighTimerHit = FALSE;
				WaitCount = WAIT_COUNT;
				NoOfCycles++;
			}

			/* Interrupt did not occur as expected */
			if (!(--WaitCount)) {
				return XST_FAILURE;
			}
		}
	} while (DutyCycle < MAX_DUTYCYCLE);

	Status = XST_SUCCESS;
err:
	/* Disable PWM */
	XTmrCtr_PwmDisable(TmrCtrInstancePtr);

	/* Disable interrupts */
	TmrCtrDisableIntr(IntcInstancePtr, DeviceId);

	return Status;
}

/*****************************************************************************/
/**
* This function is the handler which performs processing for the timer counter.
* It is called from an interrupt context.
*
* @param	CallBackRef is a pointer to the callback function
* @param	TmrCtrNumber is the number of the timer to which this
*		handler is associated with.
*
* @return	None.
*
* @note		None.
*
******************************************************************************/
static void TimerCounterHandler(void *CallBackRef, u8 TmrCtrNumber)
{
	/* Mark if period timer expired */
	if (TmrCtrNumber == TMRCTR_0) {
		PeriodTimerHit = TRUE;
	}

	/* Mark if high time timer expired */
	if (TmrCtrNumber == TMRCTR_1) {
		HighTimerHit = TRUE;
	}
}

/*****************************************************************************/
/**
* This function setups the interrupt system such that interrupts can occur
* for the timer counter. This function is application specific since the actual
* system may or may not have an interrupt controller.  The timer counter could
* be directly connected to a processor without an interrupt controller.  The
* user should modify this function to fit the application.
*
* @param	IntcInstancePtr is a pointer to the Interrupt Controller
*		driver Instance.
* @param	TmrCtrInstancePtr is a pointer to the XTmrCtr driver Instance.
* @param	DeviceId is the XPAR_<TmrCtr_instance>_DEVICE_ID value from
*		xparameters.h.
* @param	IntrId is XPAR_<INTC_instance>_<TmrCtr_instance>_VEC_ID
*		value from xparameters.h.
*
* @return	XST_SUCCESS if the Test is successful, otherwise XST_FAILURE.
*
* @note		none.
*
******************************************************************************/
static int TmrCtrSetupIntrSystem(INTC *IntcInstancePtr,
			XTmrCtr *TmrCtrInstancePtr, u16 DeviceId, u16 IntrId)
{
	 int Status;

#ifdef XPAR_INTC_0_DEVICE_ID
	/*
	 * Initialize the interrupt controller driver so that
	 * it's ready to use, specify the device ID that is generated in
	 * xparameters.h
	 */
	Status = XIntc_Initialize(IntcInstancePtr, INTC_DEVICE_ID);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	/*
	 * Connect a device driver handler that will be called when an interrupt
	 * for the device occurs, the device driver handler performs the
	 * specific interrupt processing for the device
	 */
	Status = XIntc_Connect(IntcInstancePtr, IntrId,
				(XInterruptHandler)XTmrCtr_InterruptHandler,
				(void *)TmrCtrInstancePtr);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	/*
	 * Start the interrupt controller such that interrupts are enabled for
	 * all devices that cause interrupts, specific real mode so that
	 * the timer counter can cause interrupts through the interrupt
	 * controller
	 */
	Status = XIntc_Start(IntcInstancePtr, XIN_REAL_MODE);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	/* Enable the interrupt for the timer counter */
	XIntc_Enable(IntcInstancePtr, IntrId);
#else
	XScuGic_Config *IntcConfig;

	/*
	 * Initialize the interrupt controller driver so that it is ready to
	 * use
	 */
	IntcConfig = XScuGic_LookupConfig(INTC_DEVICE_ID);
	if (NULL == IntcConfig) {
		return XST_FAILURE;
	}

	Status = XScuGic_CfgInitialize(IntcInstancePtr, IntcConfig,
					IntcConfig->CpuBaseAddress);
	if (Status != XST_SUCCESS) {
		return XST_FAILURE;
	}

	XScuGic_SetPriorityTriggerType(IntcInstancePtr, IntrId,
					0xA0, 0x3);

	/*
	 * Connect the interrupt handler that will be called when an
	 * interrupt occurs for the device.
	 */
	Status = XScuGic_Connect(IntcInstancePtr, IntrId,
				 (Xil_ExceptionHandler)XTmrCtr_InterruptHandler,
				 TmrCtrInstancePtr);
	if (Status != XST_SUCCESS) {
		return Status;
	}

	/* Enable the interrupt for the Timer device */
	XScuGic_Enable(IntcInstancePtr, IntrId);
#endif /* XPAR_INTC_0_DEVICE_ID */

	/* Initialize the exception table */
	Xil_ExceptionInit();

	/* Register the interrupt controller handler with the exception table */
	Xil_ExceptionRegisterHandler(XIL_EXCEPTION_ID_INT,
					(Xil_ExceptionHandler)
					INTC_HANDLER,
					IntcInstancePtr);

	/* Enable non-critical exceptions */
	Xil_ExceptionEnable();

	return XST_SUCCESS;
}

/******************************************************************************/
/**
*
* This function disconnects the interrupts for the Timer.
*
* @param	IntcInstancePtr is a reference to the Interrupt Controller
*		driver Instance.
* @param	IntrId is XPAR_<INTC_instance>_<Timer_instance>_VEC_ID
*		value from xparameters.h.
*
* @return	None.
*
* @note		None.
*
******************************************************************************/
void TmrCtrDisableIntr(INTC *IntcInstancePtr, u16 IntrId)
{
	/* Disconnect the interrupt for the timer counter */
#ifdef XPAR_INTC_0_DEVICE_ID
	XIntc_Disconnect(IntcInstancePtr, IntrId);
#else
	XScuGic_Disconnect(IntcInstancePtr, IntrId);
#endif
}

Some of the Macros which aren't defined: XPAR_INTC_0_DEVICE_ID, XPAR_INTC_0_TMRCTR_0_VEC_ID, XPAR_FABRIC_TMRCTR_0_VEC_ID and causing errors

suitable ethernet phy chip for ps side of XC7Z020/XC7Z010

hasila — Fri, 07 Jan 2022 04:05:47 GMT

Hi all,

I am trying to make my own low cost XC7Z020/XC7Z010 based board. I am referring the microzed schematic and picozed schematic... the thing is with the phy chip attached to the ps. the both boards are using 88E1512-A0-NNP2I000 which is very expensive(~35 usd). I have attached the schematic with this post. so I want to change this phy chip and go for a cheaper option. but my concern is....are there any reason why this has been selected even for this kind of development board... is it okay to go for a cheaper option like RTL8211E-VL which is used in the zybo board... I would be most grateful if someone can give me a clear idea about this or what are the criteria need to be consider apart from voltage levels of the zynq chip and RMII compatibility.

kind regardscommunity.element14.com/.../4237.mz-sch.PDF

Reprogramming a minized from a USB drive

GaryA — Mon, 03 Jan 2022 23:06:51 GMT

Hi,

I inadvertently deleted the files in the /run/media/mmcbkl1d1 folder and hit the reset button.

Now all I get is the Zynq> prompt - uboot.

I read "Restoring MiniZed to the Factory State" but it assumes that the board is running PetaLinux which my board is not.

How do I get image.ub, smallboot.bin, and wpa_supplicant.conf back onto the eMMC from a USB drive or some other possible way?

Thank you in advance for all your help.

Regards,
Gary

reprogramming a minized from a USB drive using the uboot Zynq> prompt

GaryA — Mon, 03 Jan 2022 23:01:10 GMT

Hi,

I inadvertently removed the files from /run/media/mmcblk1d1 which contains the image.ub and smallboot.bin.

How do I get those files back into the eMMC from a USB drive?

I have read the "Restoring MiniZed to the Factory State" and it does not describe anything near what I require - it assumes that the device is up and running PetaLinux, which it is not.

Thanks for any and all help with this

NOTE: this problem was solved by invoking the following command from the Zynq> prompt

Zynq>run boot_qspi.

Once that command was run then the entire filesystem was available and I could copy the files back into the designated folder. YES!!!

I wish that information was in the "Restoring MiniZed to the Factory State" document.

Quickstart of IBM Bluemix is not working with petalinux of Minized

jvilardy — Tue, 02 Nov 2021 22:02:03 GMT

For the course: Integrating Sensors on MiniZed with PetaLinux 2019.1, how to setup the web page quickstart IoT of IBM?

When I enter the link https://quickstart.internetofthings.ibmcloud.com/ , this web page is offline.

Register Definitions

kas.lewis — Mon, 18 Oct 2021 03:54:38 GMT

Hello All,

I'm trying to get back to learning FPGAs and how to program them. The issue I'm having is understanding were to find the information to interact with the FPGA side. I wanted to create a basic program where I have an AND or some other basic input/output created in the FPGA fabric and that would then be used by the MCU side. \

I've worked through this https://www.youtube.com/watch?v=Mb-cStd4Tqs video and can get it to run, but I can't figure out how the MCU interacts with the UART created in the FPGA fabric. Any help with this would be greatly appreciated.

Kas

How do I enable the USB Type A port on MiniZed single-core Zynq 7Z007S development board?

yiu.yuen — Tue, 21 Sep 2021 20:41:44 GMT

Hello,

I'm USB Type A port on a MiniZed single-core Zynq 7Z007S development board, I can't access it neither from the Petalinux application prompt nor from an uboot prompt.

I need the the USB Type A port being accessible/enabled for the purpose of transferring a Vxworks OS from our PC to the FPGA board.

Is there a way I can transfer a file into the MiniZed FPGA board other than buying a .

Thanks

Workshop files contain virus or malware?

dc73 — Tue, 21 Sep 2021 01:20:46 GMT

I began the Avnet speedway workshop "MiniZed Developing Zynq Hardware With Xilinx Vivado 2019.1". When I attempt to download the student files, I get the error from Norton 360 that the files contain malware or virus. Can anyone confirm?