Hello,

Thank you for your question.

Currently there is no stand alone Spinner Widget available in ESD, there is a 'Pop-Up Spinner' available in the as a ESD Utility however.

I will see if the development team can incorporate a Spinner Widget in an upcoming revision of ESD.

I would also be possible to manually edit your output source code to call the CMD_SPINNER EVE API call.

Best Regards,
BRT Community

Hi,

There are a couple of things that may help with regards to your questions although there may also be other ways using EVE's GPU and widget features to achieve it without swapping bitmaps as this can risk tearing etc.     

For the display list itself, EVE has double buffering and so if you create your content using graphic primitives and widgets then it will be double buffered. It also avoids the need to manually create and edit bitmaps unless the application needs this in particular (for example a line can be drawn by specifying the start and end point and EVE will work out how to draw the line). You can also optimise it to avoid completely re-sending the list - for example, you can use the append command to append a list of static items which you have created and then add some dynamic numbers or text for readouts. What was your overall requirement for the application?

For your question about images and changing during the scan-out,

EVE has bitmap formats such as RGB332 and ARGB2 (if you need alpha) which use 1 byte per pixel and so could fit two images in RAM_G.

The BT81x has a command CMD_SYNC which allows you to wait for the end of the scan out and so can help avoid tearing. You can use this to help when editing the data on the fly of a bitmap for example or updating a macro value as shown here.

//To update REG_MACRO_0 at the end of scan out, to avoid tearing:
cmd_sync();
cmd_memwrite(REG_MACRO_0, 4);
cmd(value);

Best Regards, BRT Community

Hello,
 
There is existing code GPIO wakeup code available with the toolchain which you can use for reference.
 
This is specifically taken from D2XX Example 1 (see AN_360 FT900 Example Applications).
The code can be found at the following location as part of the IDE:
 
C:\Users\Username\Documents\Bridgetek\FT9xx\Version\Examples\D2XX Example 1
 
#ifdef GPIO_REMOTE_WAKEUP
SetRemoteWakeup = 0;
if (RemoteWakeupEnable)
{
tfp_printf("d2xx_loopback_test1: Configuring GPIO pin to wakeup \r\n");
#if 1
/* Set up the pin */
gpio_dir(GPIO_PIN, pad_dir_input);
gpio_pull(GPIO_PIN, pad_pull_pullup);
 
 /* Attach an interrupt */
gpio_interrupt_enable(GPIO_PIN, gpio_int_edge_falling);
interrupt_attach(interrupt_gpio, (uint8_t)interrupt_gpio, ISR_gpio);
tfp_printf("d2xx_loopback_test1: GPIO pin setup for interrupt\r\n");
#endif
}
 
#endif
 
D2XXTEST__Sleep = 1;
D2XXTEST__Wakeup = 0;
 
/* Power down Mode */
SYS->PMCFG_L |= MASK_SYS_PMCFG_PM_PWRDN_MODE;
SYS->PMCFG_L |= MASK_SYS_PMCFG_PM_PWRDN;
asm volatile ("nop");
asm volatile ("nop");
asm volatile ("nop");
asm volatile ("nop");
asm volatile ("nop");
 
 //wait for wakeup
 while(!D2XXTEST__Wakeup);
 
interrupt_disable_globally();
 
#ifdef GPIO_REMOTE_WAKEUP
gpio_interrupt_disable(GPIO_PIN);
interrupt_detach(interrupt_gpio);
gpio_is_interrupted(GPIO_PIN);
 
#endif
 
SYS->PMCFG_L &= ~MASK_SYS_PMCFG_PM_PWRDN_MODE;
SYS->PMCFG_L &= ~MASK_SYS_PMCFG_PM_PWRDN;

The contents in RAM should not be lost, as this is a standby mode and not POWER ON RESET.

The datalogger feature uses the on-chip flash in the FT9XX for storage.
More information can be found in AN 365 FT9xx API Programmers Manual section 2.34 Datalogger Feature.
Example datalogger code can also be found in the Toolchain examples.

Best Regards,
BRT Community

Hello,

Thank you for question.

Could you let me know the exact display settings you are using for the panel?
Specifically LCD_HORIZONTAL and LCD_VERTICAL, if you can provide the panels datasheet that would be helpful as well.

Best Regards,
BRT Community

Hello,

I checked this and also couldn't see the source code.

I will ask for this to be added into the APIs.

Something like the following sequence in USBH_finalise() would be required to deactivate the USB Host:

{
// Remove all devices/interfaces/endpoints from root hub.
usbh_hub_port_remove(NULL, 1);
usbh_hw_disable_int();
interrupt_detach(interrupt_usb_host);

CRITICAL_SECTION_BEGIN
               usbh_intr_xfer = 0;
               usbh_intr_port = 0;
CRITICAL_SECTION_END

// Clear Status Register
usbh_hw_clrsts();
usbh_hw_stop();
usbh_hw_reset();
sys_disable(sys_device_usb_host);
}

Please test this out and provide any feedback.
You can modify the source APIs to add this.
See BRT TN 002 Modifying FT9xx API Functions for details on how to do this.
Simply copy the source .c into your project and it will override the library version.

To activate the USB host port again, you would then perform USBH_initialise().

Best Regards,
BRT Community

Hello,

In this case I would suggest having in a single thread in your system that deals with updating the EVE display list
Whilst your other threads can update and pass any applicable variable changes into the EVE thread, which will redraw the screen periodically.

Best Regards,
BRT community

Hello,

Thank you for your question.

I suspect the issue lies with the display list you are writing to EVE, for example your button routine includes a DL_START and SWAP/DISPLAY commands, but you mention that you are also setting the background to red. In general a Co-processor list should be structured as follows, with only one set DL_START and DISPLAY/SWAP commands:

[Await REG_CMD_READ == REG_CMD_WRITE and read value of these registers]
CMD_DL_START // Tells co-pro to begin writing DL at RAM_DL+0
CLEAR_COLOR_RGB // Co-processor writes this instruction to the DL
CLEAR(1,1,1) // Co-processor writes this instruction to the DL
Color_RGB(0,0,255)
Point_Size(20)
Begin(Points)
Vertex2F(0,0)
End()
DISPLAY // Co-processor writes this instruction to the DL
CMD_SWAP // Co-processor writes REG_DL_SWAP
[update REG_CMD_WRITE to point to end of new commands]
[Await REG_CMD_READ == REG_CMD_WRITE]

Could you provide the whole co-processor list that you are writing to the BT81X? (I assume you are writing other commands to EVE outwith the bt81x_draw_button routine, please correct me if I am wrong)

Best Regards,
BRT Community