Forum : 8051
| Post Information | Post |
|---|---|
|
January 25, 2016 - 5:12pm
|
Hi I am using Ride 7 to update a geriatric upsd (8051) project. It wont run/debug unless STM's PSDSoft Express is loaded on the PC (rather than the output files from ot) and as that wont run on anything more modern than Windows XP I have had to do a temp install of Ride on an old XP. Whilst building I get a number of "r7_clang.exe is not a valid Win32 applixcation" messages, but the program does generate new hex and aof files. A simple attempt to start debugging generates a simple 'programming Failure message. Opening the uPSD debugger options - I can connect to the RLINK and read its serial number and firmware version. - Connect to Target reads the PSD and MCU ID codes - so I'm talking to the processor. - Erase otion works but the program option doesnt, but it does leave the chip then failing the blank test. When attmpting to re-program I either get "programming Failure" or "No response from the DTC("Data Transfer Component")" The last weeror is reference in a question in the ARM forum bu the link in the answer is invalid. So I now have a customer unit which did work, but they wanted an extra feature, and is now completely useless. And help appreciated Dr John |
I have tried using PSD_PGM.exe to program the unit from the osf file.
That successfully reads the RLINK and upsd chip ID, and erases the chip and does a blank check.
when attempting to program it fails with
"ERROR 102: Programming failure.
This is a temporary error. Try again later could work."
not the most helpful message
I have tried a different model RLink and got the same result.
I have a very limited stock of these obsolete chips so would at least like to understand the error before committing to changing a chip that was working before it got erased.
Dr John
now chenged the chip and still got the same problem so there is some issue in your software supporting uPSD's
Tried programming by telling the debug that it had more than one device so it used/generated a jci file. Came up with an error that it could not find ride\bin\uPSD_MCU_IdCodes.txt. this again suggests you have removed or corrupted the uPSD ability. I did find a copy and inserted it but still got programming error. tried only loading the flash and reliably get the DTC error.
We have now managed to program the uPSD card that continually failed using your RLINK and associated software.
We did it using the project.obj file and an ISP link connected to a Dataman programmer.
Again this strongly suggests that you have deliberately or carelessly removed the load/debug ability for uPSD devices from you software, which is next to useless when our customers still have 1000's of units in the field and need the option to be able to update them
The lack of any response from your support is very disapointing. I might only work 1 or 2 days per week, I had expected your support team to be working at least 5!
VERY UNAMUSED
Sorry for the inconvenience but the answer of the forum question is not immediate. If you need a fastest response you should report the issue in "support".
The answer will be given in time depends the type of licenses and if you are under valid support contract. Furthermore, we will answer if the product is supported by our tools (hardware and/or software).
In this case, uPSD are supported for the compilation like all 8051 micro controllers but the programming with Rlink is not supported anymore.
Best regards,
Can you please share your setup details? I want know about the upsd and DTC, what are their specifications?
Also what are the specifications for your 8051?
Steffi
I have used the uPSD for two types of project.
1) - A card that over the years we have built several thousand of, and are currently building another 250. I have just redesigned this to use an STM 32F401 as the stock of chips we got on a last time buy is all but exhausted. to keep it going we have bought both uPSD 3334 and uPSD 3354 (same code in both but needed a change to the PSDSoft settings).
2) - Some low volume test equipment. They problem I had was an item of equipment being tested has been upgraded, so although the tester was built when the uPSD was current, it needs to be updated. Redesigning and replacing the PCB was not an economic option.
The DTC (Data Transfer Component) problem is because the uPSD has been obsolete for 8-10 years and Riasonance have removed the support for it from their latest code.
There is a secondary problem in that the uPSD contains both an 8051 core and a programmable logic block. The setup for the locic block is done using an STM program called PSDSoft Express which will not run on anythink more modern that XP. (and Ride 7 checks that you have the program installed, rather than that you have the files it produced).
If you run the latest Ride 7 on an XP machine, it will not recognice/program the uPSD and will report an error (one of which may be the DTC error).
If you download the oldest available version of RKit51 from the web site AND the version of Ride 7 published the same day you can compile and program the uPSD using an RLINK and you can run it in the simulator, however you cannot run the program in debug mode on the target hardware.
I have now installed Ride 6 and the RKit from a CD that we got 10 or so years ago, and that still works. Since Microsoft have withdrawn support for XP we will probably have to virtualise the PC in order to maintain our various approvals.
Hope this helps