cancel
Showing results for 
Search instead for 
Did you mean: 

SPC582B-DIS with the VNF1248 Evaluation board GUI

Francois_M
Associate II

Dear ST Community,
I recently bought the SPC582B-DIS board in order to test the EV-VNF1248F board. 
I installed the VNF1248 Evaluation board GUI and the UDE STK 2021 by following VNF user guide.
I downloaded the Chorus1M_VNF1248_discovery.elf in order to test the board, I flashed it with this elf file (flash success) but communication is not possible in the GUI with the good COM port  and good serial configuration (error "Cannot found Demo Board! Check USB cable"  in USB FTDI, and no Rx trame in Serial Port)
I tried with another computer, same results. I looked in the forum, I have the good PLS driver (Driver USB PLS\JtagUsbDriver), and I installed the stsw-link009, but still not working.
I also found another elf file on st community website --> Chorus1M_M09SpiDriver.elf, and with this .elf, I'm able to communicate, I get Rx trame and uC is active, but I get the error "firmware is not fitting with HW type", which seems logical.

If I'm not wrong, I (and another post on the same subject) suppose that the Chorus1M_VNF1248_discovery.elf is not working on the SPC582-DIS, but only with the EV-SPC582B which seems to be the old board, and which is out of stock on every distributor.
Would it be possible to generate a .elf which can be compatible with SPC582-DIS to control the VNF1248F? Or to find a solution to my problem ?
@zambrano.luigi@Erwan YVIN@Max VIZZINI, I see that you helped other community member on the subject, could be great if you or another ST member could help me :) 

Thank you a lot.
François 

9 REPLIES 9
Roberto CAPUTO
ST Employee

Hi François,

the correct firmware to use with the EV-VNF1248F board is included in the STSW-EV-VNF1248F package (GUI+firmware), which you can download from the device’s dedicated page at https://www.st.com/en/automotive-analog-and-power/vnf1248f.html, under the Tools & Software section.

 

Best regards,

Roberto

 

Dear @Roberto CAPUTO,
First of all, thank you for your answer.
I downloaded this firmware, but it isn't working with the SPC582-DIS board.
In the User manual of the STSW-EV-VNF1248F, they speak about the EV-SPC582B board to use with the EV-VNF1248F, and not SPC582-DIS (EV-SPC582B seems to have been replaced by SPC582-DIS)
On my side, It seems that STSW-EV-VNF1248F firmware is not compatible with SPC582-DIS. (Chorus1M_M09SpiDriver.elf seems to be compatible with this board, my computer is able to communicate with SPC582-DIS with this .elf).
Have you test that the STSW-EV-VNF1248F package is compatible with the SPC582-DIS on STM side ?
If not, is it possible to update the STSW-EV-VNF1248F package to make it compatible with SPC582-DIS ? (maybe it already exist somewhere ?)
Thank you for your help :) 

PS : Obviously, I'm not alone with this problem (https://community.st.com/t5/automotive-mcus/spc582b-dis-and-vnf1048f-1248f-firmwares/m-p/874739#M7107).

Hi François,

The EV-VNF1248F solution was developed and tested using the EV-SPC582B. As reported in the documentation, the correct hardware combination is EV-SPC582B + EV-VNF1248F. Let me check if the SPC582B-DIS can also be used.

Best regards,
Roberto

 

 

Francois_M
Associate II

Hello @Roberto CAPUTO ,
Did you have a chance to look at SPC582B-DIS + EV-VNF1248F combination ? 
Thank you by advance.
Best regards,
François 

Hi François,

Time's running, and nothing in sight!
Did you get any (may be more personnal) information regarding this post as STM employees haven't replied yet. Will they do... ?

Regards,
Michel

Francois_M
Associate II

Hello Michel,
I didn't get any answer from Roberto, but I'm not losing hope :) 
If I get any private answer or if I found a solution, I will keep you in touch ! 

Regards,
François 

Merci François !

thaidv
Associate

Hello,

I am experiencing the same issue. Has anyone found a solution yet? I have contacted support but have not received any response.

Hi Taidv,
I guess you won't get one, but we all hope you will!
Many developers have already asked several questions about these devices and their associated dev kits without getting answers from ST employees - which is the opposite of what you can attend on a forum.
Either ST does not allow them, or ST doesn't want to make profit on the devices it releases!?
I was fed up waiting for advices or clues which could have been unlocking our development but never came so I gave up with those chips and chose another and more conventional solution.
Cross your fingers.
Michel