Configuration of cube miner
Publish: 2021-05-07 17:21:19
1. The interface protocol adopted by CP2000 is pcie3x4, nvme protocol and m.2 interface. After confirming that notebook and desktop computers supporting such interface protocol can be used, please refer to.
2. The initialization clock is not configured with clock surface spi0 or SPI1
3. Administrator rights to run a look.
4. Unknown_Error
5. Click the drop-down menu of each peripheral on the left side of the pinout menu, and then configure it in configuration
6. Specific configuration process:
1. Open stm32cubemx and select the corresponding chip. The chip in this paper is stm32f207vct6. After selection, it is shown in the following figure:
2. Configure RCC clock, ETH, PA8 and enable LwIP
as the hardware of our development board is RMII mode, eth-rmii is selected. If you have a development board in MII mode, please refer to the configuration method of MII. This is only for RMII
RCC selects an external clock source and checks mco1. The software will automatically configure PA8 to mco1 mode. This pin is very important for RMII mode and is used to provide 50MHz clock for PHY chip
enable LwIP
3. The configuration of the clock tree must ensure that the mco1 output is 50MHz. If the frequency is not correct, the PHY chip will not work
because the chip is 207vct6, in order to make the mco1 output 50MHz, some adjustments of PLL frequency doubling parameters are made, as follows: (comrades can flexibly configure according to their own chip, but they need to ensure that the mco1 output is 50MHz)
4. Related parameter settings of eth, LwIP and RCC
at this point, the more important thing is in the front, but there is still one thing to pay attention to, that is, the output speed of PA8 pin, which failed several times because this pin did not pay attention to
the subsequent parameter settings can be set according to the comrades' own needs. Here are my settings for reference
the ETH parameter remains the default, but interrupt is checked once
LwIP parameter settings are as follows: (because I am configuring UDP server here, and I choose static IP allocation)
5. Generate the project and make the final function modification
Add UDP server initialization, port binding and other related functions to the generated project
I will directly add the UDP server file in the previous official routine, as follows:
then add the. C file to the user program, and add the. H header file of UDP to the main function; As follows: (the specific content of the UDP file is given later)
6. Several functions need to be added to the main function. Here, we will not explain the function and implementation principle, but only add them
attached: UDP_ Echoserver related file content (this file is an official sample program, right belongs to the official, reprinted here)
UDP_ The content of echoserver. C is as follows:
/ * includes -------- - - - - - - - - - - - - - - - - /
? Include & quot; main.h"< br />#include " lwip/pbuf.h"< br />#include " lwip/udp.h"< br />#include " lwip/tcp.h"< br />#include < string.h>< br />#include < stdio.h>< br />
/* Private typedef -----------------------------------------------------------*/
/* Private define ------------------------------------------------------------*/
#define UDP_ SERVER_ PORT 7 /* define the UDP local connection port */
#define UDP_ CLIENT_ PORT 7 /* define the UDP remote connection port */
/* Private macro -------------------------------------------------------------*/
/* Private variables ---------------------------------------------------------*/
/* Private function prototypes -----------------------------------------------*/
void udp_ echoserver_ receive_ callback(void *arg, struct udp_ pcb *upcb, struct pbuf *p, const ip_ addr_ t *addr, u16_ t port);< br />
/* Private functions ---------------------------------------------------------*/
/**
* @brief Initialize the server application.
* @param None
* @retval None
*/
void udp_ echoserver_ init(void)
{
struct udp_ pcb *upcb;< br /> err_ t err;< br />
/* Create a new UDP control block */
upcb = udp_ new();< br />
if (upcb)
{
/* Bind the upcb to the UDP_ PORT port */
/* Using IP_ ADDR_ ANY allow the upcb to be used by any local interface */
err = udp_ bind(upcb, IP_ ADDR_ ANY, UDP_ SERVER_ PORT);< br />
if(err == ERR_ OK)
{
/* Set a receive callback for the upcb */
udp_ recv(upcb, udp_ echoserver_ receive_ callback, NULL);< br /> }
}
}
/**
* @brief This function is called when an UDP datagrm has been received on the port UDP_ PORT.
* @param arg user supplied argument (udp_ pcb.recv_ arg)
* @param pcb the udp_ pcb which received data
* @param p the packet buffer that was received
* @param addr the remote IP address from which the packet was received
* @param port the remote port from which the packet was received
* @retval None
*/
void udp_ echoserver_ receive_ callback(void *arg, struct udp_ pcb *upcb, struct pbuf *p, const ip_ addr_ t *addr, u16_ t port)
{
/* Connect to the remote client */
udp_ connect(upcb, addr, UDP_ CLIENT_ PORT);< br />
/* Tell the client that we have accepted it */
udp_ send(upcb, p);< br />
/* free the UDP connection, so we can accept new clients */
udp_ disconnect(upcb);< br />
/* Free the p buffer */
pbuf_ free(p);< br />
}
udp_ The content of echoserver. H is as follows:
? Ifndef__ ECHO_ H__< br />#define __ ECHO_ H__< br />
void udp_ echoserver_ init(void);< br />
#endif /* __ MINIMAL_ ECHO_ H * /
7. So far, all the work has been completed, the project has been compiled and downloaded to the development board. Due to UDP_ The port number bound in echoserver is 7. Here we test the function of the network through the test tool,
1. Open stm32cubemx and select the corresponding chip. The chip in this paper is stm32f207vct6. After selection, it is shown in the following figure:
2. Configure RCC clock, ETH, PA8 and enable LwIP
as the hardware of our development board is RMII mode, eth-rmii is selected. If you have a development board in MII mode, please refer to the configuration method of MII. This is only for RMII
RCC selects an external clock source and checks mco1. The software will automatically configure PA8 to mco1 mode. This pin is very important for RMII mode and is used to provide 50MHz clock for PHY chip
enable LwIP
3. The configuration of the clock tree must ensure that the mco1 output is 50MHz. If the frequency is not correct, the PHY chip will not work
because the chip is 207vct6, in order to make the mco1 output 50MHz, some adjustments of PLL frequency doubling parameters are made, as follows: (comrades can flexibly configure according to their own chip, but they need to ensure that the mco1 output is 50MHz)
4. Related parameter settings of eth, LwIP and RCC
at this point, the more important thing is in the front, but there is still one thing to pay attention to, that is, the output speed of PA8 pin, which failed several times because this pin did not pay attention to
the subsequent parameter settings can be set according to the comrades' own needs. Here are my settings for reference
the ETH parameter remains the default, but interrupt is checked once
LwIP parameter settings are as follows: (because I am configuring UDP server here, and I choose static IP allocation)
5. Generate the project and make the final function modification
Add UDP server initialization, port binding and other related functions to the generated project
I will directly add the UDP server file in the previous official routine, as follows:
then add the. C file to the user program, and add the. H header file of UDP to the main function; As follows: (the specific content of the UDP file is given later)
6. Several functions need to be added to the main function. Here, we will not explain the function and implementation principle, but only add them
attached: UDP_ Echoserver related file content (this file is an official sample program, right belongs to the official, reprinted here)
UDP_ The content of echoserver. C is as follows:
/ * includes -------- - - - - - - - - - - - - - - - - /
? Include & quot; main.h"< br />#include " lwip/pbuf.h"< br />#include " lwip/udp.h"< br />#include " lwip/tcp.h"< br />#include < string.h>< br />#include < stdio.h>< br />
/* Private typedef -----------------------------------------------------------*/
/* Private define ------------------------------------------------------------*/
#define UDP_ SERVER_ PORT 7 /* define the UDP local connection port */
#define UDP_ CLIENT_ PORT 7 /* define the UDP remote connection port */
/* Private macro -------------------------------------------------------------*/
/* Private variables ---------------------------------------------------------*/
/* Private function prototypes -----------------------------------------------*/
void udp_ echoserver_ receive_ callback(void *arg, struct udp_ pcb *upcb, struct pbuf *p, const ip_ addr_ t *addr, u16_ t port);< br />
/* Private functions ---------------------------------------------------------*/
/**
* @brief Initialize the server application.
* @param None
* @retval None
*/
void udp_ echoserver_ init(void)
{
struct udp_ pcb *upcb;< br /> err_ t err;< br />
/* Create a new UDP control block */
upcb = udp_ new();< br />
if (upcb)
{
/* Bind the upcb to the UDP_ PORT port */
/* Using IP_ ADDR_ ANY allow the upcb to be used by any local interface */
err = udp_ bind(upcb, IP_ ADDR_ ANY, UDP_ SERVER_ PORT);< br />
if(err == ERR_ OK)
{
/* Set a receive callback for the upcb */
udp_ recv(upcb, udp_ echoserver_ receive_ callback, NULL);< br /> }
}
}
/**
* @brief This function is called when an UDP datagrm has been received on the port UDP_ PORT.
* @param arg user supplied argument (udp_ pcb.recv_ arg)
* @param pcb the udp_ pcb which received data
* @param p the packet buffer that was received
* @param addr the remote IP address from which the packet was received
* @param port the remote port from which the packet was received
* @retval None
*/
void udp_ echoserver_ receive_ callback(void *arg, struct udp_ pcb *upcb, struct pbuf *p, const ip_ addr_ t *addr, u16_ t port)
{
/* Connect to the remote client */
udp_ connect(upcb, addr, UDP_ CLIENT_ PORT);< br />
/* Tell the client that we have accepted it */
udp_ send(upcb, p);< br />
/* free the UDP connection, so we can accept new clients */
udp_ disconnect(upcb);< br />
/* Free the p buffer */
pbuf_ free(p);< br />
}
udp_ The content of echoserver. H is as follows:
? Ifndef__ ECHO_ H__< br />#define __ ECHO_ H__< br />
void udp_ echoserver_ init(void);< br />
#endif /* __ MINIMAL_ ECHO_ H * /
7. So far, all the work has been completed, the project has been compiled and downloaded to the development board. Due to UDP_ The port number bound in echoserver is 7. Here we test the function of the network through the test tool,
7. 1. New project
hit stm32cubemx software, click new project to select corresponding MCU (stm32f103zet6)
select project to enter the interface diagram of project
2. Configure peripheral
RCC setting to select HSE crystal / ceramic resonator
GPIO port function to select PF6, PF7, PF8, pf9led1-led4_ Output mode (yellow pin, the function GPIO has been used as its function, ignoring the green pin indicates that the pin has been used)
3. Clock configuration
the clock configuration adopts graphic configuration, which is intuitive and simple. Each peripheral clock entry STM32 high clock 72m hclk input 72 software, that is, self configuration (RCC select external high-speed clock)
4. Function peripheral configuration
configuration box I see several areas should be function settings
multimedia (medium) System: DMA, GPIO, NVIC, RCC, watchdog
middleware: FreeRTOS, FatFs, LwIP USB
Engineering DMA is not used to configure NVIC (nested vector interrupt controller) to configure interrupt priority, RCC is used to configure
GPIO pin level: low level
GPIO mode: push-pull
maximum output speed: low speed
User label: LED1
change user The pin configuration diagram of the label shows the pin label
4. Power consumption calculation
calculation of power consumption according to the configuration of peripherals
5. Engineering report
hit stm32cubemx software, click new project to select corresponding MCU (stm32f103zet6)
select project to enter the interface diagram of project
2. Configure peripheral
RCC setting to select HSE crystal / ceramic resonator
GPIO port function to select PF6, PF7, PF8, pf9led1-led4_ Output mode (yellow pin, the function GPIO has been used as its function, ignoring the green pin indicates that the pin has been used)
3. Clock configuration
the clock configuration adopts graphic configuration, which is intuitive and simple. Each peripheral clock entry STM32 high clock 72m hclk input 72 software, that is, self configuration (RCC select external high-speed clock)
4. Function peripheral configuration
configuration box I see several areas should be function settings
multimedia (medium) System: DMA, GPIO, NVIC, RCC, watchdog
middleware: FreeRTOS, FatFs, LwIP USB
Engineering DMA is not used to configure NVIC (nested vector interrupt controller) to configure interrupt priority, RCC is used to configure
GPIO pin level: low level
GPIO mode: push-pull
maximum output speed: low speed
User label: LED1
change user The pin configuration diagram of the label shows the pin label
4. Power consumption calculation
calculation of power consumption according to the configuration of peripherals
5. Engineering report
8. You can configure which version of the library to use
introction, download and installation of stm32cubemx:
http://blog.csdn.net/ybhuangfugui/article/details/52225736
stm32cubemx usage and function introction:
http://blog.csdn.net/ybhuangfugui/article/details/52264403
introction, download and installation of stm32cubemx:
http://blog.csdn.net/ybhuangfugui/article/details/52225736
stm32cubemx usage and function introction:
http://blog.csdn.net/ybhuangfugui/article/details/52264403
9. Aiken's sound card is not good. The so-called Aiken in the United States is just a Guangdong manufacturer who has registered a brand in the United States. Any joint venture is fake. I strongly don't recommend Aiken. If you want to get started with recording, you can choose the u46xl of ESI company. There is no problem loading the plug-in with the host, and the driver is very stable. For entertainment, you can choose innovation. The background of these brands can never be compared with that of "American Aiken". Because Aiken doesn't have his own technology. All cottages.
Hot content