Hello,
Q1> Are the green bars unchanged in [Fig1] and [Fig2] ?
The green bar is always full.
Regards.
Jame,Shin
Hello Charles,
Thank you for your reply.
I analyzed it with what you answered.
The example source code seems to be a problem.
When the ui32Fullness value becomes a constant, a red bar is drawn unconditionally.
And the green bar is overwritten again at a high speed, which is not visible with eyes.
How can I display data in a FIFO with a color bar?
// Called by the main function.
DrawBufferMeter(&g_sContext, 40, 22);
DrawBufferMeter(&g_sContext, 40, 42);
// Has there been any (transmit or receive) traffic since we last checked?
1 byte sent to UART Tx to USB Rx buffer (1 * 100) / 256 = 0.390625 , result 0
100 byte sent to UART Tx to USB Rx buffer (100*100)/ 256 = 39.0625 , result 39
ui32Fullness = ((USBBufferDataAvailable(&g_sRxBuffer) * 100) / UART_BUFFER_SIZE);
UpdateBufferMeter(&g_sContext, ui32Fullness, 40, 22);
ui32Fullness = ((USBBufferDataAvailable(&g_sTxBuffer) * 100) / UART_BUFFER_SIZE);
UpdateBufferMeter(&g_sContext, ui32Fullness, 40, 42);
// Fill the full section with red (if there is anything to draw)
UpdateBufferMeter(tContext *psContext, uint32_t ui32FullPercent, int32_t i32X, int32_t i32Y)
{
// Determine where the break point between full (red) and empty (green) sections occurs.
i32XBreak = (i32X + 1) + (ui32FullPercent * (BUFFER_METER_WIDTH - 2)) / 100;
case1> // ( 40+1) + ( 0 * 54) / 100 = 41 + 0 = 41
case2> // (40+1) + (39 * 54)/100 = 41 + 21.06 = 62
if(ui32FullPercent)
{
GrContextForegroundSet(psContext, ClrRed);
GrRectFill(psContext, &sRect);
}
// Fill the empty section with green
sRect.i16XMin = i32XBreak;
sRect.i16XMax = i32X + BUFFER_METER_WIDTH - 2;
if(sRect.i16XMax > sRect.i16XMin)
{
GrRectFill(psContext, &sRect
GrContextForegroundSet(psContext, ClrGreen););
}
// Revert to white for text drawing which may occur later.
GrContextForegroundSet(psContext, ClrWhite);
}
regards,
Jame,Shin
Hello Charles,
Thank you for your reply
In [Fig. 5], the red bar is hard to see when a lot of data is sent once.
[Fig. 6] shows a very small red bar variation when sending a lot of data.
I'm a bit hard to check.
Does that mean I can see the tx bar you told me changing rapidly ?
There is no see obvious change.
Have a happy weekend. ^ . ^
regards,
Jame,Shin
Hi Jame,
Please go to the uart.h file for the MACRO definition.
//***************************************************************************** // // Values that can be passed to UARTFIFOLevelSet as the ui32TxLevel parameter // and returned by UARTFIFOLevelGet in the pui32TxLevel. // //***************************************************************************** #define UART_FIFO_TX1_8 0x00000000 // Transmit interrupt at 1/8 Full #define UART_FIFO_TX2_8 0x00000001 // Transmit interrupt at 1/4 Full #define UART_FIFO_TX4_8 0x00000002 // Transmit interrupt at 1/2 Full #define UART_FIFO_TX6_8 0x00000003 // Transmit interrupt at 3/4 Full #define UART_FIFO_TX7_8 0x00000004 // Transmit interrupt at 7/8 Full //***************************************************************************** // // Values that can be passed to UARTFIFOLevelSet as the ui32RxLevel parameter // and returned by UARTFIFOLevelGet in the pui32RxLevel. // //***************************************************************************** #define UART_FIFO_RX1_8 0x00000000 // Receive interrupt at 1/8 Full #define UART_FIFO_RX2_8 0x00000008 // Receive interrupt at 1/4 Full #define UART_FIFO_RX4_8 0x00000010 // Receive interrupt at 1/2 Full #define UART_FIFO_RX6_8 0x00000018 // Receive interrupt at 3/4 Full #define UART_FIFO_RX7_8 0x00000020 // Receive interrupt at 7/8 Full
Whose pumpkin is handsome. ?
Hello.,
To everyone
It gives a pleasant laugh.
regards,
Jame, Shin
Hello Charles,
I don't know the source code interface in the Usb dev serial API.
Q1> How do you send the data in g_sTxBuffer to PC Rx Host USB1 (Bulk IN) using which source code?
Q2> How do I get to g_sRxbuffer using which source code from PC Tx Host USB1 (Bulk OUT)?
regards,
Jame,Shin
Hello , My Star & friend Cb1
I want to grow pumpkins by finding fertile land in the 'barren and pumpkin-free' area.
True to the basics, looking for ideas in simple places.!!
I will send vitamins E for anti aging medicines.
May I ask you a question.
Q1> When data is written to TxFIFO, will it be automatically sent to UART0 Tx pin immediately?
Or is it sent to UART0 Tx based on the interrupt level 50% setting in FIFO memory?
Have a good weekend.
regards,
Jame,Shin
Tag : Pumpkin cultivation on the next Halloween day.
Hello Cb1,
Cb1 Said > What is your definition of 'immediately?' (that's important - is it not?)
A> In the usb_dev_serial API, UART_FIFO_TX4_8 is enabled with half of the FIFO (8 bytes out of 16 bytes) or 50% interrupt configuration
Cb1 Said > Without enabling the FIFO - staff notes (near) immediate output from UARTn_TX. (this observed via O-Scope)
A> i.e. Sending 1 byte character from USB1 transmission serial terminal immediately receives 1 byte character from USB0 receiving serial terminal.
Q1> In the words of Cb1 and staff, if the FIFO is enabled, does it wait for 8 bytes in the FIFO and then print it to the next USB0( via ICD) receiving terminal window?
( self-reflection , My thoughts and actions are lazy, Don’t have O-Scope now)
regards,
Jame,Shin
Greetings to this forum's 'Artistic Director.' And while your creativity (likely) 'pain some' - you've added LIFE to an otherwise 'barren plain.'
Even though it is just past 08:00 Sunday - and only 3 staffers have 'come in' - we all (suddenly) have become hungry! (that 'thanks' (somehow) to forum's Artistic Director!)
Not having a Scope places you at a, 'Real Disadvantage' - especially when you are deploying Serial Interfaces. (i.e. SPI, I2C, CAN - most notably)
That said - is not one 'Creative & Resourceful enough to present 'Filet Mignon' to this (otherwise) 'Cut/Paste Plain' - able to 'IMAGINE' a 'Scope Replacement/Substitute'?'
Now the Scope presents two key advantages:
Now - to answer your particular questions - are not 'ONLY' the toa 'Time of Arrival' (and even) 'IF the signal arrives' - your REAL ISSUES?
Young Staff here believes, 'That is so' - thus can a Signal's 'Arrival/Presence' be (somehow) detected - yet minus a Scope?
Staff - having 'hacked' your 'Artistic File' (at least in 'spirit') - present:
as a beyond, 'Adequate Scope Substitute' when 'Signal Presence, Generation (and or Pulsation)' proves of interest and/or value.
While 'timing' info appears unavailable - it too can be 'gleaned' via (imaginative):
TAG: When 'NO Scope' proves 'NO EXCUSE!' (now that's a 'proper Tag!')
Jame,
Jame shin said:Q1> In the words of Cb1 and staff, if the FIFO is enabled, does it wait for 8 bytes in the FIFO and then print it to the next USB0( via ICD) receiving terminal window?
Regardless in FIFO mode or not, as soon as you write to the FIFO, the transmission will start. There is a 16 bytes deep TX FIFO. The threshold to generate the TX interrupt is programmable. Let's suppose you program the TX interrupt FIFO trigger level to 1/2. This means that the interrupt is only generated after there are 8 bytes or less in the FIFO. The processor could have written 16 bytes to the TX FIFO in a burst. After the first byte is written to the TX FIFO, the transmission starts. You should see the START bit on the UART TX pin immediate if you use the scope to capture. After 8 bytes are transmitted out, there is only 8 bytes left in the FIFO. This is the time when the TX FIFO interrupt is generated to notify the processor write more data to the TX FIFO.
