PSoC™ 5, 3 & 1 Forum Discussions

USB bootloader works the first time, but on subsequent tries I get this error message: The application is currently marked as active and cannot be modified.

Hi,

I can program a hex file with a MiniProg3 and its GUI application as attached picture shows.

Then I followed the sample code in "C:\Program Files (x86)\Cypress\Programmer\Examples\Programming\PSoC3_5\SWD\C_Sharp", if I run this sample code directly without any changes, the prompt tells me:

"Failed! PSoC device is not acquired! Check connection of the chip to the programmer"

So I change the code with the settings on the GUI application, Below is the code of setting part in ProgramAll() function:

Mainly I have many issues on:

1. The prompt tells me "Failed! Device is not in ISSP mode"

2. CheckHexAndDeviceCompatibility() function could not pass.

3. EraseAll() function is unable to run.

4. Sometime I change the "Power" mode to "Power Cycle", sometimes I change the function from xxx() to PsoC3_xxx() if I found there is one, but it still could not work. Anyone know what's wrong there? Thanks!

Code:

if (pp == null) return -1;

string filePath = "E:/Projects/X2/CRTS-XRAY-XPS-Bootloader-v3.2.hex";

int hr;

//Port Initialization

//Setup Power - "5.0V" and internal

hr = pp.SetPowerVoltage("0.5", out m_sLastError);

if (!SUCCEEDED(hr)) return hr;

hr = pp.PowerOn(out m_sLastError);

if (!SUCCEEDED(hr)) return hr;

//Set protocol, connector and frequency

hr = pp.SetProtocol(enumInterfaces.SWD, out m_sLastError); //SWD-protocol

if (!SUCCEEDED(hr)) return hr;

hr = pp.SetProtocolConnector(0, out m_sLastError); //5-pin connector

if (!SUCCEEDED(hr)) return hr;

hr = pp.PSoC3_SetProtocolClock(enumFrequencies.FREQ_01_6, out m_sLastError); //3.0 MHz clock on SWD bus

// Set Hex File

int hexImageSize;

hr = pp.HEX_ReadFile(filePath, out hexImageSize, out m_sLastError);

if (!SUCCEEDED(hr)) return hr;

//Set Acquire Mode

pp.SetAcquireMode("Power", out m_sLastError);

//The "Programming Flow" proper

//Acquire Device

//hr = pp.DAP_Acquire(out m_sLastError);

hr = pp.DAP_Acquire(out m_sLastError);

if (!SUCCEEDED(hr)) return hr;

//Check Hex File and Device compatibility

//bool fCompatibility;

//hr = CheckHexAndDeviceCompatibility(out fCompatibility);

//if (!SUCCEEDED(hr)) return hr;

//if (!fCompatibility)

//{

// m_sLastError = "The Hex file does not match the acquired device, please connect the appropriate device";

// return -1;

//}

//Erase All

hr = pp.EraseAll(out m_sLastError);

if (!SUCCEEDED(hr)) return hr;

Dear All:

I am working in a design having a SAR ADC and AMUX. Check the picture attached for the schematic.

ADC is single ended, internal VREF 1.024, Bypassed, range 0-2.048V.

I have three small questions regarding this subsystem:

(1) To calculate ADC offset I have connected the last channel of the AMUX (COL_9) to VSSA (externally, on the PCB) and use the following code

AMux_FastSelect(9);

CyDelayUs(10);

ADC_SAR_StartConvert();

ADC_SAR_IsEndConversion(ADC_SAR_WAIT_FOR_RESULT);

adcReading = ADC_SAR_GetResult16();

ADC_SAR_SetOffset(adcReading);

Do you think is this correct?

(2) Should I do anything similar to calculate the ADC_SetScaledGain()? In the ADC datasheet, it says:

"It should only be used to further calibrate the ADC with a known input or if the ADC is using an external reference."

In case yes, What do suggest me?

(3) On the AMUX datasheet,  AMUX_FastSelect command seems to take 4 us to set the new channel (Table 1, pag8) for a 48Mhz Clock, so, as I am using a 24Mhz clock, I have added a CyDelayUS(10) on the code above. Is this correct? More or less time?

Thanks in advance,

Joaquin.

Hi, I'm a bit new to USB device design and have a fairly straight forward question about connection state. 

My application is a keyboard style piece of hardware that has custom buttons, USBFS with three HID end points for keys, mouse and volume control. It's always powered and always connected to an Embedded X86, running Windows 10 or similar. The OS will reboot many times during the users day, because Windows is like that, and each time, my device will stop working, requiring a full power cycle to bring us back.

I need to detect the USB disconnection by host... right now I'm using USBFS_1_bGetConfiguration, and clearly it is returning a != 0 value even after the OS has shut down. 

Should I be using isConfigurationChanged()? This would let me see the OS come up, then I'd reInit the USBFS, use USBFS_1_bGetConfiguration to confirm a connection and load each end point? I'm working on this now with no success yet.

Thanks, Brent. 

I had initially posted requesting for info on MultiApp bootloader, but the post wasn't successful. 

Is there any documentation on how to use MultiApp bootloader which can be of use..

「①対角が15mm以上の推奨外の大きさのボタン」「②センサ配線が推奨外の長さ」である場合の懸念点を教えてください。

寄生容量が大きくなり、SNRが「5」以上の感度が取れない等でしょうか？