New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device detection fails. Boot fails as well. #3
Comments
Thanks for the very detailed issue, that helps a lot ! First things first, here is a list of things I consider good from what you said:
Things I'm unsure about:
Things I'm pretty sure don't work:
That would explain exactly the traces I see and also the detection issue you have. DMA transfers are too fast to be cleanly implement on the STM32, so I use fixed delays. It worked on all my machines (and it worked for other people too), but it seems to be hit or miss. Could you try experimenting with the pulseDrqSend function ? The aim is to find the correct number of lines (between line 230 and 236 in the last version) to have the correct DRQ pulse timing. Some had more success by removing 3 or 4 lines, but you may have to add 3 or 4 lines. The best way to test is to try booting the ST: if you have more than one command on the trace, it means that reading from the SD card is working to some extent. If you need to test your image, I recommend you test on the Hatari emulator because my code follows its implementation so the behavior should be the same. |
I did some checks on an up to date Roger Clark environment. It seems that the optimization level has an impact. Can you try with Tools/Optimize: Fastest (-O3) ? |
Hi! I switched the optimization level to: Fastet (O3). Results are at least interesting. At first - nothing changed. I did some testing and after around 15 minutes of meddling - it booted! During a day I managed to get it working only once :( I think I'll try shortening wires a little (now 7cm). I have also borrowed another blue pill from a friend. |
I have another observation from today! Just by accident I powered the ACSI2STM from laptops USB (instead of charger). During tests:
In following days I'll try to experiment with pulseDrqSend as you suggest. |
That's nice progress, thanks for the feedback ! |
Hi, I looked carefully at the bottom of the blue pill, and there are already to capacitors between 5V and GND - on mine boars labelled C5 and C7. Unfortunately, there is no label on them, parameters are unknown. According to some sources on web those might already be 100n and 10u :/ However I have a major breakthrough :)
Demo "We were at" is causing problems. It loads and runs until certain point. It crashes before image screen with girl and her hair waving. FDD version loads some additional data at that moment. What's interesting is that Hatari emulator fails as well, but due to some reports - Ultrasatan does not. I'll try to contact Leonard/Oxygene for that. |
Hi! I heard that someone at atari-forum is trying to exact-cycle Drq pulses using machine code's NOP instructions. What do you think? |
Hi, If you still have issues, I recommend that you upgrade to the 2.0 beta I just uploaded. Beware that there are minor pinout differences. |
I am trying to build acsi2stm and I am having hard time.
Symptoms:
Source: http://atari.8bitchip.info/DiskImgPP1.html
Source: http://joo.kie.sk/?page_id=332
Some details:
https://a.allegroimg.com/s720/118a5c/e51e5c7a499b809e3ae4c8f7aa82/Modul-STM32F103C8T6-Board-STM32-ARM
as well as from Roger Clark (https://github.com/rogerclarkmelbourne/Arduino_STM32)
I am starting to believe that I have a fake chip. Maybe there are slightly different timings on GPIO and device goes out of sync?
Maybe do you have any ideas what to do next?
Maybe try to get different blue pill?
The text was updated successfully, but these errors were encountered: