I am trying to glitch this new target board PSoC 62 but not able to, whatever changes made in the simpleserial.c , no effective changes are seen when trying to run introduction to clock glitching file. i had to flash the target all that process is happening, i got the psoc62 hal layer file from a github source that particular file has a simpleserail.c file with some exceptions they havent used the commands used for version 2 , only the code lines related to version 1 is used, kindly help me out here what changes are to be made inorder to carry out glitching.
simpleserial.c is unrelated to glitching - itâs just the serial protocol we use. Iâm not sure what clock settings we use for the PSOC, but you might have to change the clock source for the CPUs (I think hal/psoc62/generated_source/psoc6sw-1.1/components/psoc6pdl/drivers/source/cy_sysclk.c has all the clock change functions).
Hi @Alex_Dewar , one more question, I am trying to make serial communication with the help of this PSoC 62 Target board to call an API and get the value of that APi for example
simpleserial_addcmd(âpâ, 5, password);
where password is the API I want call and get the result, this password API has a value which i want to receive. And I am not able to make that serial communication. Any idea what changes are to be made in order to get the result. and make the serial communication??
You should use target.simpleserial_write('p', bytearray([N1, N2, N3, N4, N5]) in Python
where N1-5 are the 5 bytes of the password. Make sure youâre using the SimpleSerial class in Python,
and not the SimpleSerial2 class. The former should be selected if you run through with SS_VER=âSS_VER_1_1â in a notebook.
Have you had any successful serial communication with this target? If not, it could be that the baud rate isnât actually coming out to 38400bps. Try printing some stuff just after init_uart() in main(), then looking for it in Python. You could automate this as follows (may require some adjusting, as Iâve used some similar code in the past, but donât remember it exactly off the top of my head)
Hi @Alex_Dewar , I tried to do the following changes you mentioned but no changes happened.
this is the link to which I created the .hex file and flashed onto the target board using Segger J Link. The main_cm4.c file, this has the functions to carry out the serial communication, problem here is there is blinky function which should make LEDs in the hardware to blink but it isnât happening so I am getting a doubt if the flashing occurred correctly or not. If this works I think the remaining will work automatically. Can you let me know if this is working for you?? There are some changes made to main_cm0 file and main_cm4.c file am not able to upload an attachment.
so can you let me know which file did you use to generate .hex file??please share it with me.
I tried to do it as you said but no result or changes. Not able to communicate serially with the PSOC 62 Target. Anything else you suggest?? Can you please check out the code in that link and let me know if there is anything wrong. In main_cm4.c file.
Can you let me the procedure you carry out to do serial communication with PSoC 62 Target board. Like how did you flash the firmware onto the target, and so on. Which files did you use to do that. Would be really helpful.
%%bash -s â$PLATFORMâ â$SS_VERâ
cd âŚ/âŚ/âŚ/hardware/victims/firmware/simpleserial-glitch
make PLATFORM=$1 CRYPTO_TARGET=NONE SS_VER=$2
it says Couldnât find program: âbashâ . Any fix for this, tried adding the bin file location to environment variables but didnât work. Help me out.